Home

W10 Pro - Problems with multiple server IPs and mapped network drive

%3CLINGO-SUB%20id%3D%22lingo-sub-801152%22%20slang%3D%22en-US%22%3EW10%20Pro%20-%20Problems%20with%20multiple%20server%20IPs%20and%20mapped%20network%20drive%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-801152%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20a%20file%20server%20fileserver1%20with%20two%20IPs%2C%20a%20LAN%20IP%20192.168.100.100%20and%20a%20VPN%20IP%20192.168.200.200.%20The%20Windows%2010%20Pro%20client%20uses%20the%20DNS%20name%20fileserver1.company.corp%20to%20get%20the%20correct%20IP%20depending%20on%20its%20own%20network%20(LAN%20or%20VPN).%20DNS%20name%20resolution%20works%20without%20problems.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20client%20has%20a%20persistent%20network%20drive%20K%3A%20%5C%5Cfileserver1.company.corp.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUnfortunately%20the%20Windows%2010%20Pro%20client%20always%20seems%20to%20use%20the%20cached%20server%20IP%20(192.168.100.100%20or%20192.168.200.200)%20to%20reconnect%20the%20network%20drive%20on%20startup.%20Some%20users%20want%20to%20wakeup%20the%20Windows%20PC%20from%20powersave%20mode.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20the%20client%20uses%20the%20cached%20IP%20from%20the%20other%20location%20(LAN%20vs.%20VPN)%2C%20access%20to%20this%20drive%20fails.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHow%20can%20I%20update%20the%20network%20drive%20IP%3F%3CBR%20%2F%3E%3CBR%20%2F%3ECurrently%20I%20use%20two%20workarounds.%3C%2FP%3E%3COL%3E%3CLI%3EOn%20most%20PCs%20it%20is%20enough%20to%20delete%20network%20drives%20(net%20use%20K%3A%20%2Fdelete)%20and%20then%20connect%20the%20network%20drive%20again%20with%20the%20DNS%20name%20(net%20use%20K%3A%20%5C%5Cfileserver1.company.corp%20%2Fpersistent%3Ayes)%3C%2FLI%3E%3CLI%3ESome%20PCs%20need%20a%20reboot%20between%20deletion%20of%20network%20drive%20and%20connection%3C%2FLI%3E%3C%2FOL%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-801152%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3Enetwork%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Enetwork%20drive%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Evpn%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-807885%22%20slang%3D%22en-US%22%3ERe%3A%20W10%20Pro%20-%20Problems%20with%20multiple%20server%20IPs%20and%20mapped%20network%20drive%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-807885%22%20slang%3D%22en-US%22%3EWhat%20type%20of%20DHCP%20is%20available%20in%20your%20network%3F%20software%20or%20hardware%3F%3CBR%20%2F%3EWhat%20is%20the%20file%20server%20exactly%3F%20is%20it%20a%20Windows%20Server%20or%20NAS%3F%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E
Highlighted
bjoernv
Occasional Visitor

I have a file server fileserver1 with two IPs, a LAN IP 192.168.100.100 and a VPN IP 192.168.200.200. The Windows 10 Pro client uses the DNS name fileserver1.company.corp to get the correct IP depending on its own network (LAN or VPN). DNS name resolution works without problems.

 

The client has a persistent network drive K: \\fileserver1.company.corp.

 

Unfortunately the Windows 10 Pro client always seems to use the cached server IP (192.168.100.100 or 192.168.200.200) to reconnect the network drive on startup. Some users want to wakeup the Windows PC from powersave mode.

 

If the client uses the cached IP from the other location (LAN vs. VPN), access to this drive fails.

 

How can I update the network drive IP?

Currently I use two workarounds.

  1. On most PCs it is enough to delete network drives (net use K: /delete) and then connect the network drive again with the DNS name (net use K: \\fileserver1.company.corp /persistent:yes)
  2. Some PCs need a reboot between deletion of network drive and connection
1 Reply
Highlighted
What type of DHCP is available in your network? software or hardware?
What is the file server exactly? is it a Windows Server or NAS?