If the VPN is using the same subnet range as your local LAN, then the easiest fix would probably be to either change the VPN subnet or the LAN subnet (I use
192.168.1.0/24, for example).
If you only need to use say one or two devices on the remote network, you can just set up static routes for those devices and remove the VPN's subnet route:
If the VPN supports it (I'm not familiar with Window's built-in VPN), configure the VPN to not create a route for the VPN subnet, and instead create individual routes for each device you want to access. You can specify these by having the VPN create a route for the exact IP and a subnet of 255.255.255.255.
- Open an elevated (administrator) command prompt
route print and make a note of the interface list at the top. The first number for each interface is the interface number, you want the interface number for your VPN interface. We'll call it
VPN-IF for the sake of this guide.
- Remove the subnet route to the VPN:
route delete 192.168.1.0 MASK 255.255.255.0 IF VPN-IF You should lose all connectivity with devices on VPN at this point, but it should still be connected.
- Add routes for each device on the VPN that you want to access:
route -p add <DEVICEIP> MASK 255.255.255.255 IF VPN-IF where
<DEVICEIP> is the IP of the device you want to access.
You will need to repeat step #3 after each time you connect to the VPN, though the routes in step #4 will persist across reboots. Note, any IPs that you add a static route for in step #4 will not be accessible on the local network.