Start > ncpa.cpl > Right click your VPN Connector > Properties > Internet Protocol Version 4 > Properties.Īdvanced > Untick ‘Automatic Metric’ > Set the Interface Metric to 10 > OK > OK >OK.Mapping a Network Drive or Folder in Windows 10 is easy, mapping a drive means that getting permanent access to a drive or folder which is currently residing on another computer, File server, and network storage devices in a different location. Well until Microsoft fixes this in Windows 10, (it’s fine on Windows 8 and earlier), you have to manipulate the metrics yourself, like so

AND THE LOWEST ONE WINS, so your DNS queries are going out of your local internet connection NOT down the VPN tunnel! How Do I Fix this? Why is this happening? Well even with Force Tunnel enabled, you can still use your local LAN (Connect to your VPN, and ping your home gateway, or printer or wireless access point if you don’t believe me!) This connection takes precedence over your remote VPN connection, to prove it run a netstat -rn command.įrom the above you can see my Ethernet Adaptor has a metric of 6, and my VPN connector, (in this case called Connection Template) has metric of 23. But disabling IPv6 is hardly a fix is it?Īlso If you want internet access for your remote clients, (Commonly referred to as ‘Split Tunnel’), then even with IPv6 disabled, the problem comes back! Google this problem and you’re simply told to ‘Disable IPv6 on your network card, and this works, (if you want to keep your remote users Force-Tunnelled).

Now I connected fine, and I could ping IP addresses on my corporate network, but I could not ping my servers by their domain name, in fact Windows was trying to resolve my domain name to a public IP?

Connect to vpn network drive windows 10