RRAS in Windows 2003

[Stephen Gillett]

I have a Windows 2003 server with R&RAS enabled. The
machine has two nics one is public and has a public
default gateway, the other is homed on the internal
network and has a 192 address with no default gateway.

I am able to connect and autheticate and register my
computer on the network no problem from a dialup to
earthlink. The problem is I can not see any of the 192
hosts on the internal segment. I do recall in Win2000
that I needed to add some static routes on the server
that will apply to clients and things would work fine
however I am having problems finding that Q article for
the problem If anyone can provide that info would be
appreciated. I tried all the standard static routes that
that made sense to me with no luck. I also can not get to
the internet terminaled in from 192 network as well. Keep
in mind from outside the network things PPTP initially
fine.

Thanks!

 

[Bill Grant]

You should not need any routes on the client to see the LAN machines. By
default, the client sets up a default route through the tunnel, so all
traffic goes to the RRAS server. It is then forwarded on to the LAN machines
(if they are in the same IP subnet) or routed to the LAN segment by the RRAS
server (if they are in different IP subnets).

Do you have your name resolution set up correctly? Does the remote
client use the correct DNS suffix on the connection? Can you do an nslookup
for a LAN client from the remote?

Getting Internet access depends on a few things. How do your LAN clients
access the Internet? If they use NAT on this same server, you need to add
the "internal" interface as a private interface in NAT. (In 2003 you can do
this from the RRAS console. In W2k you needed to use a netsh command).

If the LAN clients access the Internet through another gateway, it is
probably just a matter of checking that the routing works to get traffic
back to the remote client. Note that in both cases, the client needs to get
the correct DNS server address.