Error 0x80070035 Network Path Not Found Fix

Error 0x80070035, “The network path was not found,” appears when Windows cannot reach a shared folder or drive on another computer over the network. This guide explains the most common causes and walks you through the fixes that usually resolve it, from enabling network discovery to resetting your network settings.

What This Error Means

When you try to open a network share (for example, typing \\COMPUTERNAME\SharedFolder in File Explorer), Windows sends a request to locate that computer and the specific shared resource. Error 0x80070035 means the request failed before any connection was made. The computer name could not be resolved, the target machine is offline, or something on the path (like a firewall or a misconfigured network profile) is blocking the request.

This error is different from an access-denied error (0x80070005) or a credentials error. Those mean the computer was found but you lack permission. Here, the path itself is unreachable.

Why This Happens: Common Causes

Several distinct issues can produce the same error message. Knowing which one you have saves time.

• Network discovery is off – Windows can’t see other devices, and other devices can’t see it.
• File and printer sharing is disabled – Even if discovery is on, sharing must also be enabled.
• Incorrect network profile – The network is set to “Public” instead of “Private,” which blocks file sharing by default.
• Firewall rules – Third-party antivirus or Windows Defender Firewall may be blocking SMB (port 445) traffic.
• DNS or NetBIOS name resolution failure – The computer name you typed can’t be translated to an IP address.
• SMB protocol version mismatch – Older Windows versions use SMB1, while newer ones may have it disabled.
• IPv6 vs IPv4 issues – Sometimes the network uses IPv6 but the name resolution only works over IPv4.

Quick Fixes to Try First

Start with these simple steps. They resolve a large percentage of cases.

1. Check the computer name and path. Open Command Prompt and type ping COMPUTERNAME. If it replies, name resolution works. If not, try the IP address instead: \\192.168.1.10\share.
2. Make sure the target computer is on and awake. Check if it’s in sleep mode or has its network adapter disabled.
3. Restart both computers. A simple reboot clears many temporary network glitches.
4. Try accessing via IP address. If that works, the problem is name resolution, not the network path itself.

Enable Network Discovery and File Sharing

Windows turns off network discovery by default for public networks. To turn it on:

1. Open Control Panel > Network and Sharing Center > Advanced sharing settings.
2. Under your current network profile (Private or Guest/Public), select Turn on network discovery and Turn on file and printer sharing.
3. Save changes.

If you’re on a domain network, some settings may be managed by Group Policy and will be grayed out. In that case, contact your network administrator.

Set the Network Profile to Private

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

1. Go to Settings > Network & Internet > Status.
2. Click Properties under your active connection.
3. Under Network profile, select Private.

This is safe on home or office networks you trust. On public Wi-Fi (coffee shops, airports), keep it set to Public.

Check Firewall and Antivirus Settings

Windows Defender Firewall usually allows file sharing on private networks. But third-party security software often blocks SMB traffic. To test:

1. Temporarily disable your third-party firewall or antivirus.
2. Try accessing the network share again.
3. If it works, re-enable the software and add an exception for file sharing (port 445, or the specific app).

If you use Windows Defender Firewall, ensure the rules for “File and Printer Sharing” are enabled for Private networks:

1. Open Windows Defender Firewall > Allow an app or feature through Windows Defender Firewall.
2. Scroll to File and Printer Sharing and check both Private and Public boxes if you need access on both.

Reset Network Settings

If nothing else works, resetting the network stack often clears corrupted settings. This is a more aggressive step, so note your Wi-Fi passwords first.

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

You can also go to Settings > Network & Internet > Status > Network reset and follow the prompts. This reinstalls network adapters and resets all settings to defaults.

Enable SMB 1.0 (If Needed for Older Devices)

If you’re connecting to an old Windows 7 or XP machine, or a network-attached storage (NAS) device from the early 2000s, it may require SMB1. Windows 10 and 11 disable SMB1 by default for security. To enable it (only if necessary):

1. Open Control Panel > Programs > Turn Windows features on or off.
2. Check SMB 1.0/CIFS File Sharing Support.
3. Restart the computer.

Warning: SMB1 is outdated and insecure. Only enable it temporarily to transfer files, then disable it again. Modern devices don’t need it.

Use the IP Address Instead of the Computer Name

If name resolution is the problem, bypass it entirely. Find the target computer’s IP address (run ipconfig on that machine) and type \\192.168.1.50\share in File Explorer. If that works, the issue is DNS or NetBIOS. To fix name resolution permanently:

• Add an entry to the hosts file (C:\Windows\System32\drivers\etc\hosts) mapping the IP to the computer name.
• Or ensure both computers are on the same workgroup and have different computer names.

Frequently Asked Questions

Why does this error happen even when both computers are on the same Wi-Fi?

Same Wi-Fi doesn’t guarantee the network profile is set to Private. If either machine is on a Public profile, file sharing is blocked. Also, some routers have “AP isolation” enabled, which prevents devices from talking to each other. Check your router settings.

Can I fix this error by disabling Windows Defender Firewall?

Yes, but it’s not recommended. Disabling the firewall leaves your computer exposed. Instead, add an exception for File and Printer Sharing, or temporarily disable it to test if the firewall is the cause. Re-enable it immediately after testing.

What does “network path not found” mean when using a mapped drive?

It means the mapped drive letter points to a share that is currently unreachable. The same causes apply. You can try disconnecting and re-mapping the drive with the correct path.

Does this error occur on Mac or Linux when connecting to Windows?

Yes, but the error message may differ. The underlying causes are similar: SMB protocol version, firewall, or name resolution. On Mac, you might see “There was a problem connecting to the server.” On Linux, you might get “mount error(2): No such file or directory.”

Is there a way to prevent this error from happening again?

Yes. Keep network profiles set to Private on trusted networks, ensure network discovery and file sharing are enabled, keep Windows updated, and avoid using SMB1 unless absolutely necessary. Also, use static IP addresses for computers that host shared folders, so the IP doesn’t change.

Related

• Dual SIM & eSIM on iPhone XR and XS: Setup Guide
• Disable Chrome Targeted Ads: Step-by-Step Guide
• Your PC Ran Into a Problem Error: Fixes That Work