When attempting to map a network drive, the following error appears. This error is common when the share was mapped on an old computer, and you are attempting to map the share on a new computer.
Determine if there is a DNS issue
- Launch PowerShell.
- Type ping \\example\share to determine the IP address of the share.
- Attempt to map the network drive using the IP address of the share (example: \\1.2.3.4\share)
If you are able to map the network drive when using the IP address, but the error appears when using the DNS name, this verifys there is a DNS issue.
Flush your local DNS cache
Use the ipconfig /flushdns command to flush your DNS cache.
PS C:> ipconfig /flushdns
Windows IP Configuration
Successfully flushed the DNS Resolver Cache.
Determine the IP address of the Authoritative DNS Server
Use the nslookup command to determine the IP address of the Authoritative DNS Server. In this example, the Authoritative DNS server is 161.228.143.112, and the Authoritative DNS Server is able to resolve example.com to 161.228.39.13.
PS C:> nslookup example.com
Server: usapl1-abcdefg.pbi.global.pvt
Address: 161.228.143.112
Non-authoritative answer:
Name: www.example.com
Address: 161.228.39.13
Aliases: example.com
Ensure the NIC is configured to use the Authoritative DNS Server as the Primary DNS Server
PS C:> ipconfig /all
. . .
DNS Servers . . . . . . 161.228.143.112
Did you find this article helpful?
If so, consider buying me a coffee over at 