It should be noted that if you connect to a network using a Virtual Private Network (VPN) connection, that network may appear to your machine as a different network than when you are directly connected to the network. For example, if you have your machine in your office and connected to your work network, that network might appear as something like WorkNet. But if you are at home and VPN into your work network, the work network might appear to your machine under a different name, such as WorkVPN. In this case, NDC considers them as two different networks, and you need to create entries in NDC for your mapped drives under both network names. An example of this is shown below, where the same server (\\192.168.0.32\Public\Temp) is assigned to the same drive letter (Q:) under the direct connection network name (HIEX-Guest) and the VPN connection to that same network (Network).




Another issue to be aware of when using a VPN is whether the VPN connection is using split tunneling. If it is using split tunneling, and the server you want to map to is on another subnet or VLAN, the split tunnel VPN connection may misdirect the call to the server to the wrong gateway, in which case, the server won't be reachable. The solution is to not allow the VPN connection to use split tunneling. If you are using Windows built in VPN capability, the default is to not use split tunneling.