RRAS & DHCP Question.

G

Guest

Guest
Archived from groups: microsoft.public.win2000.advanced_server (More info?)

Good day to all. A quick question regarding the above:

1) RRAS setup on server,
2) DHCP and DNS all good (reserved 10 addresses from DHCP for clients),
3) All works well and as expected with the following exception;

When a client VPNs in, they get an address from the reserved Pool - Good
thing. The server (call it BOB) has a static address of 192.168.0.200. When
the client logs in, BOB gets an additional address from the reserved pool.
So far so good. The problem is that LAN clients connect to internal
resources (File, Print, Linux, Web etc). Periodically a LAN client tries to
access a resource at BOB\sharename. BOB is registered in DNS at the 200
address. When a VPN client connects to BOB, some users (Win2k * XP pro) try
to access BOB (@ 200), but seem to be sent to BOB (@ VPN DHCP address, say
100).

It's annoying, but not a show stopper.

Any Ideas as to how to fix this up/

TX,

RG
 

lee

Distinguished
Mar 30, 2004
635
0
18,980
Archived from groups: microsoft.public.win2000.advanced_server (More info?)

Bob should have two nics...the external one used for vpn connections should
NOT register in DNS. The internal one registers and is the only place bob
is found.
Lee

"Richard Gutery" <rgutery@mentorits.com> wrote in message
news:uzoxTQ1yEHA.908@TK2MSFTNGP11.phx.gbl...
> Good day to all. A quick question regarding the above:
>
> 1) RRAS setup on server,
> 2) DHCP and DNS all good (reserved 10 addresses from DHCP for clients),
> 3) All works well and as expected with the following exception;
>
> When a client VPNs in, they get an address from the reserved Pool - Good
> thing. The server (call it BOB) has a static address of 192.168.0.200.
When
> the client logs in, BOB gets an additional address from the reserved pool.
> So far so good. The problem is that LAN clients connect to internal
> resources (File, Print, Linux, Web etc). Periodically a LAN client tries
to
> access a resource at BOB\sharename. BOB is registered in DNS at the 200
> address. When a VPN client connects to BOB, some users (Win2k * XP pro)
try
> to access BOB (@ 200), but seem to be sent to BOB (@ VPN DHCP address, say
> 100).
>
> It's annoying, but not a show stopper.
>
> Any Ideas as to how to fix this up/
>
> TX,
>
> RG
>
>
 
G

Guest

Guest
Archived from groups: microsoft.public.win2000.advanced_server (More info?)

Thanks Lee, never thought of that one. Did so and now all is well.

Cheers.

RG
"Lee" <leweb2000@hotmail.com> wrote in message
news:enCOroGzEHA.260@TK2MSFTNGP11.phx.gbl...
> Bob should have two nics...the external one used for vpn connections
> should
> NOT register in DNS. The internal one registers and is the only place bob
> is found.
> Lee
>
> "Richard Gutery" <rgutery@mentorits.com> wrote in message
> news:uzoxTQ1yEHA.908@TK2MSFTNGP11.phx.gbl...
>> Good day to all. A quick question regarding the above:
>>
>> 1) RRAS setup on server,
>> 2) DHCP and DNS all good (reserved 10 addresses from DHCP for clients),
>> 3) All works well and as expected with the following exception;
>>
>> When a client VPNs in, they get an address from the reserved Pool - Good
>> thing. The server (call it BOB) has a static address of 192.168.0.200.
> When
>> the client logs in, BOB gets an additional address from the reserved
>> pool.
>> So far so good. The problem is that LAN clients connect to internal
>> resources (File, Print, Linux, Web etc). Periodically a LAN client tries
> to
>> access a resource at BOB\sharename. BOB is registered in DNS at the 200
>> address. When a VPN client connects to BOB, some users (Win2k * XP pro)
> try
>> to access BOB (@ 200), but seem to be sent to BOB (@ VPN DHCP address,
>> say
>> 100).
>>
>> It's annoying, but not a show stopper.
>>
>> Any Ideas as to how to fix this up/
>>
>> TX,
>>
>> RG
>>
>>
>
>