Posts Tagged ‘remote vpn’
Issue: When connected to Remote Access VPN, internet cannot be reached because of IP routing conflicts
Solution: Enable Split Tunneling for the VPN connection, and add routing for the IP addresses on the device
On a Windows 10, When Remote VPN is connected, internet disconnects. Let’s say, 192.168.20.123 is an IP address on the VPN. In the screenshot below, when internet is connected, google.com pings, however 192.168.20.123 doesn’t ping. Expected behavior because we are not connected to VPN yet.
When Remote VPN connectivity is established, the internet goes off, and the VPN machine starts pinging.
So, that’s the issue.
Disconnect the VPN.
Open Windows Powershell, and type in the command to enable Split Tunneling for the VPN connection.
If VPN connectivity is attempted now, after the Split Tunneling change, notice the internet works, however VPN machine cannot be reached.
Add a persistent route for the destination.
We need four things to add a permanent route:
- The destination IP address [Eg: 192.168.20.123]
- Subnet mask [Eg: 255.255.255.255]
- Destination gateway [Eg: 192.168.20.1]
- VPN network interface id (route print command, and identify the Interface ID of the VPN connection)
[Eg: In the example below, the Interface Number for the VPN connection is 69]
Open a command prompt with Elevated Privileges, and type in the below command to add a permanent route to the destination IP address. For more IP addresses, repeat the command by changing the destination IP address.
Now, internet connectivity works as expected. If there is a request for 192.168.20.123 IP address which is on the VPN, then the route would go through the VPN interface.