Discussion Locked

VPN connection closes LAN activity

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Here is the situation, users connected to a LAN use their VPN connection to connect to another LAN. When they do, they loose connectivity to the original LAN. I'm sure it has something to do with Open Shortest Path First, but can't seem to get it toquit. Very annoying. Oh only happens on the 2K professional workstations, not NT4.

5 replies

by rabbit_runner

I am not certain, but we have experienced this similar problem. What we learned was that the 'route table' was adjusted when you open the VPN connection. The computer, then does not know how to communicate to the locak LAN.

At one location, we have a computer on the network, DSL internet connection. The computer boots fine, and can browse the network. But this system is needed to connect to a remote location via VPN. As soon as the VPN tunnel is established, we are able to communicate with the remote network, able to browse the internet, but NOT able to browse the local network. We have not addressed this problem, because the user, simply re-boots the system and it works fine. At least until the VPN connection is used again.

The problem is that the route table has been modified. If one can determine which entries have been modified, then make the necessary adjustements, you should be able to fix this.

Hope this helps

by verada

I understand now. I tried clearing the "Use Default Gateway on remote network" tab and it seemed to clear it up, for one situation. However in the case of one user on DSL it did not. I'm chalking it up to Microsoft, and telling the user to re-boot.

by stillatit

Step 1. Go into the vpn dial-up properties on the user's machine. Under tcp/ip settings (click the button), at the bottom, there is a check box for "Use default gateway on remote network" or some such. Clear the box.

This step prevents the situation you are describing, but connectivity over the vpn may or not be correct depending on how you are set up. If the network(s) on the far side of the vpn are NOT accessable, apply step 2, below.

Step 2. Create a batch file which contains one ROUTEstatement for each network on the far side of the vpn. The form of the command is:
ROUTE ADD MASK
where the network address is the address range you want to reach (typically ending in .0), mask number is the subnet mask of the network, and gateway address is the address of the vpn server on the far side of the vpn, using its INTERNAL (over the vpn) address.

Set up a desktop icon to run the batch file, and have the user double-click the iconafter bringing up the tunnel.

Good luck.

by verada

I used the clear default gatway option and it seemed to work for one of the users. However several of our users connect through DSL VPN connections, these users seem to not be helped. I will try the Route Add angle. Thanks for the help

This discussion is closed to new replies.