client default gateway

[Jeremy]

When I connect to my RAS server, then perform a route
print on the RAS server the default gateway to my local
subnets is the IP address given to RAS client. While the
client is connected the server cannot browse the network
and the client cannot ping internally (except for internal
subnet of RAS server) and cannot get to the internet. Any
suggestions here is great.

 

[Bill Grant]

There are several different situations and problems here.

1. The default gateway setting is correct. The default gateway of your
remote client is the point-to-point connection to the RRAS server. The IP
address for this connection is the "received" IP. See MS KB 254231.

2. Client cannot get to the Internet. Is the server doing NAT for the LAN
clients? Remote clients do not also get to NAT by default. You need to make
the internal interface (to which the remote client connects) an input to
NAT. In Server 2003 you can do this from the GUI. In W2k RRAS you need to
use this netsh command from a command prompt.

netsh routing ip nat add interface internal private

3. Network browsing. Is the server the first/only DC on the network? Making
a RRAS connection makes the server multihomed, which upsets browsing and may
also affect name resolution. See MS KB 292822.