for proper routing, the network you are dialing in from must be on a
different subnet then the
one you are dialing into. Below are some examples
Ex of Improper config, and what you probibly have:
Local Desktop 192.168.1.38
255.255.255.0
192.168.1.1 (VPN overrides when connected and points
to 192.168.1.254)
Remote Server 192.168.1.2
255.255.255.0
192.168.1.254
^-- this will not work because the routing tables can not properly determine
if the traffic is local,
or remote(through the VPN tunnel)
Ex of Proper Config:
Local Desktop 192.168.5.38
255.255.255.0
192.168.5.1
Remote Server 192.168.1.2
255.255.255.0
192.168.1.254
^-- With this config, your desktop(client) machine will be able to determine
which network to pass
traffic to, while still using your local connection for internet access.
Ex of working, but improper config (for most cases, this will be needed in
certian cases)
With this you will connect remotly, but internet access will be very slow.
(ie. VPN session
is using default gateway on remote network, tcp properties -> advanced)
Local Desktop 192.168.5.38
255.255.255.0
192.168.1.254 (note, this will still say 192.168.5.1
in your LAN settings, the
VPN session settings will override this when connected)
Remote Server 192.168.1.2
255.255.255.0
192.168.1.254