EXPERT RESPONSE
You problem is fairly easy to resolve if you have administrative access to the remote VPN server you are connecting to or are able to communicate with its administrator so he can resolve it for you.
In almost every VPN server, there's an option in the client configuration section usually named "Split Tunneling Policy," where you're able to either tunnel everything on the client's side to go through the VPN or specify a preconfigured network list.
The preconfigured network list is built by the administrator and contains all the networks behind the VPN server that the remote client should be able to connect to. These networks are then added in the client's routing table as soon he connects to the VPN. If no such list exist, then the solution is to push everything (0.0.0.0) through the VPN tunnel, which is what seems to be happening in your case.
You'll also be able to view this if you type "route print" on your command prompt before and after connecting to the VPN server.
In closing, let me point out that this problem is at the VPN server side, not your router or PC. When a VPN client connects to a VPN server, all configured parameters are pushed to the client, whether he likes it or not!
Cheers.
|
