VPN Clients can't access other resources

I just setup RRAS to allow PPTP VPN connections and the clients connect fine
and can ping and DNS resolve the RRAS server but no other server or resource
in the network. Do I need to add a static route? All the clients are
receiving a 169. IP address too.

Thanks,

Luke

There is no way it will work if the clients are receiving APIPA addresses.
They are not routable.

It looks like your RRAS server can't get addresses from DHCP. Have you
tried using a static pool of addresses?

"Luke Davis" <Luke (E-Mail Removed)> wrote in message
news:64C6B1A7-FAD9-4F24-BCBA-(E-Mail Removed)...
>I just setup RRAS to allow PPTP VPN connections and the clients connect
>fine
> and can ping and DNS resolve the RRAS server but no other server or
> resource
> in the network. Do I need to add a static route? All the clients are
> receiving a 169. IP address too.
>
> Thanks,
>
> Luke

That's what I thought, but I set RRAS' DHCP to give out IP's in the same
subnet as the local network, and that still did not work. Any other Ideas?

"Bill Grant" wrote:

> There is no way it will work if the clients are receiving APIPA addresses.
> They are not routable.
>
> It looks like your RRAS server can't get addresses from DHCP. Have you
> tried using a static pool of addresses?
>
> "Luke Davis" <Luke (E-Mail Removed)> wrote in message
> news:64C6B1A7-FAD9-4F24-BCBA-(E-Mail Removed)...
> >I just setup RRAS to allow PPTP VPN connections and the clients connect
> >fine
> > and can ping and DNS resolve the RRAS server but no other server or
> > resource
> > in the network. Do I need to add a static route? All the clients are
> > receiving a 169. IP address too.
> >
> > Thanks,
> >
> > Luke
>
>

That is not how it works. The DHCP option just means that the server
leases the addresses from DHCP and uses them as an address pool. If the
server can't do this for any reason you get APIPA addresses being used.

Configure a static pool of addresses in the same IP subnet as your LAN
machines. Use addresses from the high end on the scope like x.y.z.201 to
x.y.z.220 . You can reserve these in the DHCP scope if you are worried that
they might be issued to a LAN device

"Luke Davis" <(E-Mail Removed)> wrote in message
newsE0B0F65-D6C1-43FA-BC45-(E-Mail Removed)...
> That's what I thought, but I set RRAS' DHCP to give out IP's in the same
> subnet as the local network, and that still did not work. Any other
> Ideas?
>
> "Bill Grant" wrote:
>
>> There is no way it will work if the clients are receiving APIPA
>> addresses.
>> They are not routable.
>>
>> It looks like your RRAS server can't get addresses from DHCP. Have
>> you
>> tried using a static pool of addresses?
>>
>> "Luke Davis" <Luke (E-Mail Removed)> wrote in message
>> news:64C6B1A7-FAD9-4F24-BCBA-(E-Mail Removed)...
>> >I just setup RRAS to allow PPTP VPN connections and the clients connect
>> >fine
>> > and can ping and DNS resolve the RRAS server but no other server or
>> > resource
>> > in the network. Do I need to add a static route? All the clients
>> > are
>> > receiving a 169. IP address too.
>> >
>> > Thanks,
>> >
>> > Luke
>>
>>

I can't believe I made that mistake. I've been searching for answers online
now how to fix this DNS problem, I can ping the IP addresses of internal
servers now but I can't resolve their name. Any ideas?

"Bill Grant" wrote:

> That is not how it works. The DHCP option just means that the server
> leases the addresses from DHCP and uses them as an address pool. If the
> server can't do this for any reason you get APIPA addresses being used.
>
> Configure a static pool of addresses in the same IP subnet as your LAN
> machines. Use addresses from the high end on the scope like x.y.z.201 to
> x.y.z.220 . You can reserve these in the DHCP scope if you are worried that
> they might be issued to a LAN device
>
> "Luke Davis" <(E-Mail Removed)> wrote in message
> newsE0B0F65-D6C1-43FA-BC45-(E-Mail Removed)...
> > That's what I thought, but I set RRAS' DHCP to give out IP's in the same
> > subnet as the local network, and that still did not work. Any other
> > Ideas?
> >
> > "Bill Grant" wrote:
> >
> >> There is no way it will work if the clients are receiving APIPA
> >> addresses.
> >> They are not routable.
> >>
> >> It looks like your RRAS server can't get addresses from DHCP. Have
> >> you
> >> tried using a static pool of addresses?
> >>
> >> "Luke Davis" <Luke (E-Mail Removed)> wrote in message
> >> news:64C6B1A7-FAD9-4F24-BCBA-(E-Mail Removed)...
> >> >I just setup RRAS to allow PPTP VPN connections and the clients connect
> >> >fine
> >> > and can ping and DNS resolve the RRAS server but no other server or
> >> > resource
> >> > in the network. Do I need to add a static route? All the clients
> >> > are
> >> > receiving a 169. IP address too.
> >> >
> >> > Thanks,
> >> >
> >> > Luke
> >>
> >>
>
>

Just make sure that the client has the correct DNS address (ie the one on
the LAN you connect to). If it isn't getting it automatically, configure it
manually in the client's connection properties. If you can resolve a name
using theFQDN but not by just using a single name, manually code the domain
suffix into the client as well.

"Luke Davis" <(E-Mail Removed)> wrote in message
newsF7E29BA-B7C9-4151-84AE-(E-Mail Removed)...
>I can't believe I made that mistake. I've been searching for answers
>online
> now how to fix this DNS problem, I can ping the IP addresses of internal
> servers now but I can't resolve their name. Any ideas?
>
> "Bill Grant" wrote:
>
>> That is not how it works. The DHCP option just means that the server
>> leases the addresses from DHCP and uses them as an address pool. If the
>> server can't do this for any reason you get APIPA addresses being used.
>>
>> Configure a static pool of addresses in the same IP subnet as your
>> LAN
>> machines. Use addresses from the high end on the scope like x.y.z.201 to
>> x.y.z.220 . You can reserve these in the DHCP scope if you are worried
>> that
>> they might be issued to a LAN device
>>
>> "Luke Davis" <(E-Mail Removed)> wrote in message
>> newsE0B0F65-D6C1-43FA-BC45-(E-Mail Removed)...
>> > That's what I thought, but I set RRAS' DHCP to give out IP's in the
>> > same
>> > subnet as the local network, and that still did not work. Any other
>> > Ideas?
>> >
>> > "Bill Grant" wrote:
>> >
>> >> There is no way it will work if the clients are receiving APIPA
>> >> addresses.
>> >> They are not routable.
>> >>
>> >> It looks like your RRAS server can't get addresses from DHCP. Have
>> >> you
>> >> tried using a static pool of addresses?
>> >>
>> >> "Luke Davis" <Luke (E-Mail Removed)> wrote in message
>> >> news:64C6B1A7-FAD9-4F24-BCBA-(E-Mail Removed)...
>> >> >I just setup RRAS to allow PPTP VPN connections and the clients
>> >> >connect
>> >> >fine
>> >> > and can ping and DNS resolve the RRAS server but no other server or
>> >> > resource
>> >> > in the network. Do I need to add a static route? All the clients
>> >> > are
>> >> > receiving a 169. IP address too.
>> >> >
>> >> > Thanks,
>> >> >
>> >> > Luke
>> >>
>> >>
>>
>>