Error 0x800704cf: Network Location Can’t Be Reached

Error 0x800704cf means Windows cannot reach a network location (a shared folder, NAS, or another PC) because of a network discovery, permission, or connectivity problem. The fix usually involves checking your network profile, enabling SMB support, or resetting the network connection. Below is a detailed breakdown of why this error appears and how to resolve it step by step.

What Causes Error 0x800704cf?

This error is most common on Windows 10 and Windows 11 when you try to open a mapped drive or a UNC path like \\SERVER\Share. The underlying causes fall into a few categories:

• Network discovery is off – Windows can’t see other devices on the network.
• Incorrect network profile – The connection is set to Public instead of Private, which blocks file sharing.
• SMB protocol disabled or outdated – The Server Message Block version used by the remote device isn’t supported.
• Firewall or security software – Blocks the ports used for file sharing (445, 139, 138, 137).
• DNS or IP address issue – The computer name can’t be resolved to an IP address.
• Credentials issue – The user account doesn’t have permission to access the share.

Quick Fixes to Try First

Before diving into advanced settings, try these simple steps:

1. Restart both the computer and the device hosting the share (NAS, router, other PC).
2. Check that the remote device is powered on and connected to the same network.
3. Try accessing the share by IP address instead of name: \\192.168.1.10\share.
4. Run the Windows Network Troubleshooter: Settings > System > Troubleshoot > Other troubleshooters > Network Adapter.
5. Disable and re-enable the network adapter in Control Panel > Network and Sharing Center > Change adapter settings.

Step-by-Step: Set Network Profile to Private

Windows treats public networks as untrusted and blocks file sharing by default. To change the profile:

1. Open Settings > Network & Internet > Wi-Fi (or Ethernet).
2. Click on the connected network.
3. Under Network profile type, select Private.
4. If you’re on Ethernet, you may need to go to Ethernet > click the connected network and change the profile there.

After switching, try accessing the network location again. If it still fails, proceed to the next step.

Enable Network Discovery and File Sharing

Network discovery must be turned on for Windows to find other devices. Here’s how:

1. Open Control Panel > Network and Sharing Center > Advanced sharing settings.
2. For the Private profile, turn on Network discovery and File and printer sharing.
3. For the All Networks profile, turn on Public folder sharing (optional) and ensure Password protected sharing is set as appropriate.
4. Click Save changes.

Check SMB Protocol Support

Windows 10 and 11 have SMB 1.0 disabled by default for security reasons. If the remote device (like an older NAS) only supports SMB 1.0, you’ll get this error. To enable SMB 1.0 (use with caution):

1. Open Control Panel > Programs > Turn Windows features on or off.
2. Scroll to SMB 1.0/CIFS File Sharing Support and check it.
3. Click OK and restart.

However, SMB 1.0 is insecure and should only be enabled temporarily. A better solution is to update the firmware on the NAS or device to support SMB 2.0 or higher. To check which SMB versions are enabled on your Windows machine, open PowerShell as administrator and run:

Get-SmbServerConfiguration | Select EnableSMB1Protocol, EnableSMB2Protocol

Reset Network and Firewall Settings

Sometimes the network stack gets corrupted. Resetting it can clear the error:

1. Open Command Prompt as administrator.
2. Run the following commands one by one:
   • netsh int ip reset
   • netsh winsock reset
   • ipconfig /flushdns
3. Restart the computer.

If you suspect the Windows firewall is blocking SMB, you can temporarily disable it (only for testing) and try again. If it works, you need to add an inbound rule for ports 445 and 139. Go to Windows Defender Firewall > Advanced settings > Inbound Rules > New Rule, select Port, and allow TCP ports 445, 139, 138, and 137. Also enable the predefined rules for File and Printer Sharing.

Verify Credentials and Permissions

If the network location requires a username and password, make sure you’re using the correct credentials. On the remote machine, check that the folder is shared with the user account you’re trying to use. To test, try accessing the share using an administrator account on the remote device. Also, check if the remote device has a guest account enabled – sometimes that helps if password-protected sharing is off.

Frequently Asked Questions

Why does error 0x800704cf happen only when accessing a NAS?

NAS devices often use SMB or NFS protocols. If the NAS firmware is outdated or configured to use SMB 1.0, Windows 10/11 will block the connection. Check the NAS settings for SMB version and enable SMB 2.0 or higher. Also, ensure the NAS is on the same subnet and has a static IP.

Can I fix error 0x800704cf by changing the computer name?

Sometimes DNS resolution fails due to a stale cache. Flushing DNS (ipconfig /flushdns) and restarting the computer can help. Changing the computer name is not usually necessary, but if the name has special characters, renaming it to a simple alphanumeric name might resolve the issue.

Is error 0x800704cf the same as “network path not found”?

No, they are different. “Network path not found” (error 0x80070035) indicates the path is unreachable, whereas 0x800704cf specifically points to a network location that Windows can’t reach due to a configuration issue. However, the troubleshooting steps overlap.

Does this error appear when trying to access a shared printer?

Yes, it can. Shared printers are network locations too. The same fixes apply: enable network discovery, set the profile to private, and ensure SMB is enabled. Also, check that the print sharing service (Spooler) is running on the host.

Will upgrading to Windows 11 fix this error?

Not necessarily. The error is usually caused by network configuration, not the OS version. However, Windows 11 has updated network drivers and SMB settings, which might resolve some underlying issues. If you’re on Windows 10 and have tried everything, upgrading could help, but it’s not a guaranteed fix.

How do I map a network drive to avoid this error?

Mapping a drive doesn’t prevent the error, but it can make accessing the share easier. Right-click on This PC > Map network drive, choose a drive letter, and enter the path. Make sure to check “Connect using different credentials” if needed. If the error persists, the underlying network issue must be fixed first.

Related

• iPhone 14 Pro Camera: Step-by-Step Guide
• Remove OneDrive from Windows 10: A Step-by-Step Guide
• Fix iPhone Apps After Location Access Is Restricted