Fix Error 0x800704cf in Windows 10

Error 0x800704cf typically appears when Windows 10 cannot connect to a network share, a mapped drive, or another computer on your local network. It often reads “The network location cannot be reached” and is caused by incorrect network settings, a stale DNS cache, or a firewall blocking the connection. This guide walks you through the most effective fixes, from quick resets to deeper configuration changes.

What You’ll Need

• Administrator access to your Windows 10 PC
• The exact name or IP address of the computer or server you’re trying to reach
• If you’re on a domain network, your domain credentials

Step-by-Step

1. Check your network connection. Click the network icon in the system tray and ensure you’re connected to the correct network (Wi‑Fi or Ethernet). If you’re on Wi‑Fi, try moving closer to the router or restarting the router.
2. Restart your PC and the device you’re connecting to. Turn off both the computer showing the error and the target computer or NAS, wait 30 seconds, then power them back on. This clears many temporary glitches.
3. Flush the DNS cache. Press Win+R, type cmd, right‑click “Command Prompt” and select “Run as administrator”. Then run:

   ipconfig /flushdns

   Also run ipconfig /registerdns and ipconfig /renew in the same window.

4. Reset the TCP/IP stack. In the same administrator Command Prompt, run:

   netsh int ip reset
   netsh winsock reset

   Restart your PC after these commands.

5. Verify the target computer name or IP. On the target machine, open Command Prompt and type ipconfig to see its IPv4 address. Then on your PC, try connecting directly to that IP: press Win+R, type \192.168.1.100 (replace with the actual IP) and press Enter. If that works, the problem is with name resolution.
6. Check the network profile type. Go to Settings → Network & Internet → Status, click “Properties” under your active connection, and set the network profile to Private (not Public). Public networks block file sharing by default.
7. Enable Network Discovery and File Sharing. Open Control Panel → Network and Sharing Center → Advanced sharing settings. Under “Private”, turn on “Network discovery” and “File and printer sharing”. Save changes.
8. Check Windows Firewall. In the same advanced sharing settings, ensure “File and Printer Sharing” is allowed through the firewall. To verify, go to Control Panel → Windows Defender Firewall → Allow an app or feature through Windows Defender Firewall and confirm the checkbox is ticked for Private networks.
9. Disable IPv6 temporarily. Open Control Panel → Network and Sharing Center → Change adapter settings. Right‑click your connection, choose “Properties”, uncheck “Internet Protocol Version 6 (TCP/IPv6)”, and click OK. If the error disappears, you may need to update your network driver.
10. Update network drivers. Press Win+X and select “Device Manager”. Expand “Network adapters”, right‑click your adapter, and choose “Update driver”. Select “Search automatically for drivers”.
11. Check the SMB 1.0/CIFS setting (if connecting to old devices). Some older NAS or Windows 7 machines require SMB 1.0. In Windows 10, go to Control Panel → Programs → Turn Windows features on or off, expand “SMB 1.0/CIFS File Sharing”, and check “SMB 1.0/CIFS Client”. Reboot. (Only enable if necessary, as SMB 1.0 is insecure.)
12. Map the network drive using the IP address. If you normally use a computer name, try mapping the drive with the IP instead: right‑click “This PC” → “Map network drive”, enter \192.168.1.100\share.

Common Mistakes

• Using the wrong network profile. Leaving the network as “Public” blocks file sharing. Always set your home/office network to “Private”.
• Forgetting to restart after changes. Many fixes (like netsh resets) only take effect after a reboot.
• Typing the computer name incorrectly. Windows names are case‑insensitive but must be spelled exactly. Use the IP address to rule this out.
• Disabling the firewall entirely. Turning off Windows Firewall to fix the error is risky and often doesn’t work. Instead, allow the specific feature through the firewall.

Tips

• Use a static IP for the target computer if it keeps changing. This avoids future connection failures.
• Keep your network drivers updated regularly, especially after a major Windows update.
• If you’re connecting to a work network, check with your IT admin whether VPN or direct access is required.
• Test the connection with the ping command: ping 192.168.1.100. If you get replies, the network path is fine.

Troubleshooting

If the error persists after trying all steps above, consider the following:

• Check the target device’s sharing settings. On the computer you’re trying to reach, make sure the folder is actually shared and that the user account has permission. Right‑click the folder → “Give access to” → “Specific people” and add your username.
• Try a different user account. Sometimes the error is due to cached credentials. In the “Map network drive” window, uncheck “Reconnect at sign‑in” and enter credentials manually.
• Disable network adapter power saving. In Device Manager, right‑click your network adapter → “Properties” → “Power Management” tab, and uncheck “Allow the computer to turn off this device to save power”.
• Run the Windows Network Troubleshooter. Go to Settings → Update & Security → Troubleshoot → Additional troubleshooters → Network Adapter and run it. Also run “Shared Folders” troubleshooter if available.
• Check for third‑party antivirus interference. Some security suites block file sharing. Temporarily disable the firewall component (not the whole product) and test. Re‑enable it afterwards.
• Reset the network settings completely. Go to Settings → Network & Internet → Status, click “Network reset”, and restart. This reinstalls network adapters and sets everything to default.

Frequently Asked Questions

What does error 0x800704cf mean?

It means Windows cannot reach the network location you’re trying to access. The cause is usually a network configuration issue, not a hardware failure.

Can this error occur on Windows 11?

Yes, the same error can appear on Windows 11, and the fixes are nearly identical. The steps above work for both versions.

Why does the error appear only when using a computer name but not an IP?

That points to a DNS or NetBIOS name resolution problem. Flushing DNS and ensuring the network profile is set to Private often fixes it.

Is it safe to enable SMB 1.0?

SMB 1.0 is outdated and has security vulnerabilities. Only enable it if you absolutely need to connect to legacy devices, and disable it after use.

Will resetting the network delete my Wi‑Fi passwords?

Yes, a network reset removes all saved network profiles, including Wi‑Fi passwords. You’ll need to reconnect and re‑enter them.

Do I need to be an administrator to fix this error?

Most fixes require administrator privileges, especially those involving Command Prompt and Device Manager. If you’re not an admin, contact your system administrator.

Related

• Block Metro Apps From Using Your Webcam in Windows
• Fix Microsoft Weather App Issues Windows 10
• How to Tell if Your iPhone Has Water Damage