RAS'd in : why traffic routed though VPN's network

[John A Grandy]

Why is it that when RAS'd into a VPN that much of your network traffic is
routed through the internal routers of the VPN's network ?

I'm not talking about the case where you are Remote Desktop'd into a machine
that is a member of the VPN's network.

I'm talking about the case of having a VPN connection open, and making the
following two types of requests directly from your machine:

1. Making simple browser requests from your box to public websites:
google.com , whatever. If you look at the tracert, you see that the VPN's
network router (and then it's inet provider) is forwarding the packets.
This slows down speed of web access relative to if the traffic was routed
through you local inet connection.

2. When Outlook needs to contact its assigned Exchange Server it tries to
locate it on the VPN's network ! Incredibly annoying. You can see Outlook
popping up message boxes above the systray saying that it's unable to find
its Exchange Server.

Can Windows Server 2000 be configured so that it knows to first go to the
local network and the local router for requested urls, including local
network resources ?

 

[Kurt]

Because the default VPN client setup is to use the default gateway on the
remote network. This is for good reason, many corporate networks are routed
and if you had your local gateway as the default you wouldn't be able to get
to any routed subnets via the VPN. You can uncheck the "use default gateway
on remote network" box and your local default gateway will be used instead.

....kurt