3 replies
by stillatit
What has probably happened is that the definition of the VPN connection, the box for "Use default gateway on server" (or some such) is checked. This can be found if you click the button for TCP/IP properties in the VPN definition.
With the box checked, when the VPN comes up, it overrides your default gateway with the VPN's. This masks the rest of the internet.
Uncheck the box. If the VPN server is running RIP, everything should still work, but you should be able to see the internet. If you have problems seeing the network on the other side of the VPN with the box not checked, create a set of ROUTE commands which specificlly point to the VPN for each network or subnet on the far side of the VPN. Put these commands in a batch file, andrun the batch from an icon.
Example:
If my vpn server has address 10.0.0.1, and the network on the far side is 10.1.2.0, the route command is:
ROUTE 10.1.2.0 MASK 255.255.255.0 10.0.0.1 METRIC 1
Using the -p switch on the route command is not a workable solution because when the vpn is down the route is invalid.
Good luck.
by adlee
by adlee
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending