sodcalculator

10 Tech How-To

Fix Error 0x80070035 Network Path Not Found in Windows

Guide 10-57606 · Updated · Step by step

Error 0x80070035 (“The network path was not found”) appears when Windows cannot reach a shared folder or printer on another computer. This guide walks through the most common causes—network discovery off, incorrect credentials, firewall blocks, and SMB protocol mismatches—and gives you clear steps to resolve it on Windows 10 and 11.

What You’ll Need

  • Administrator access on both the computer you’re using and the one hosting the shared folder.
  • The IP address or hostname of the target computer (find it with ipconfig on that machine).
  • Knowledge of the share name (e.g., \\PC-Name\SharedFolder).

Step-by-Step

  1. Confirm the target computer is on and reachable. Open Command Prompt and run ping <IP-address>. If ping fails, check that both computers are on the same network and that the target’s firewall allows ICMP (or temporarily disable the firewall for testing).
  2. Enable Network Discovery and File and Printer Sharing. On both computers, go to Control Panel > Network and Sharing Center > Advanced sharing settings. Under Private, turn on Network discovery and File and printer sharing. Save changes.
  3. Verify the share exists. On the host computer, right-click the folder you want to share, select Properties > Sharing > Share, and note the network path it shows (e.g., \\DESKTOP-ABC\Shared). Ensure the share name has no typos.
  4. Try connecting via IP instead of hostname. Press Win+R, type \\<IP-address> (e.g., \\192.168.1.10), and press Enter. If this works, the issue is DNS/NetBIOS resolution—skip to step 7.
  5. Check SMB protocol settings. On the host, open Control Panel > Programs > Turn Windows features on or off. Ensure SMB 1.0/CIFS File Sharing Support is checked (if the other computer is older) or that SMB 2/3 is enabled (default on modern Windows). Reboot if you change this.
  6. Adjust firewall settings. On the host, open Windows Defender Firewall > Allow an app or feature through the firewall. Ensure File and Printer Sharing is checked for both Private and Public networks. If you have a third-party firewall, allow inbound TCP 445 and UDP 137-138.
  7. Use the correct credentials. When prompted, enter the username and password of an account on the host computer. If the host uses a Microsoft account, use that email and password. Try prefixing with the computer name: \\HOSTNAME\username.
  8. Enable SMB signing or disable it temporarily. On the host, run gpedit.msc (Pro/Enterprise) and navigate to Computer Configuration > Windows Settings > Security Settings  Local Policies > Security Options. Set Microsoft network server: Digitally sign communications (always) to Disabled and try again. Re-enable later for security.
  9. Reset the network stack. On the client, open Command Prompt as administrator and run: netsh int ip reset, netsh winsock reset, then reboot.
  10. Map the drive with different options. In File Explorer, right-click This PC > Map network drive. Choose a drive letter, enter the path, and check Connect using different credentials. If you get the error, try using the IP and adding /user: in the credential prompt.

Common Mistakes

  • Typing the share path incorrectly. Windows paths use backslashes, not forward slashes. Double-check for spaces or missing characters.
  • Forgetting to enable network discovery on the host. Without it, the host doesn’t advertise shares, and the client can’t see them.
  • Using a public network profile. Windows treats public networks as untrusted and blocks file sharing by default. Switch both computers to a Private network profile in Settings > Network & Internet.
  • Credential mismatch. Using a PIN or local account password when the host expects a Microsoft account password (or vice versa).
  • Disabling SMB completely. Some security guides recommend disabling SMB, but if you need file sharing, leave SMB 2/3 enabled.

Tips

  • Use static IP addresses for computers that share files regularly to avoid DNS changes.
  • Create a dedicated share account with a strong password to avoid using your main admin account.
  • If you’re on a domain, check with your IT admin—Group Policy may block SMB or require specific settings.
  • Keep Windows updated; many SMB fixes are included in cumulative updates.
  • For quick testing, temporarily disable the firewall on the host, but re-enable it immediately after.

Troubleshooting

If the error persists after following all steps:

  • Check the host’s firewall logs. Look for blocked inbound connections on port 445. If blocked, add an inbound rule for TCP 445.
  • Try accessing from another device. If another computer can connect, the issue is specific to your client. Reinstall the network adapter driver or run sfc /scannow.
  • Verify the host’s IP hasn’t changed. Use ipconfig on the host and try the new IP.
  • Check if the host has a VPN or virtual adapter. Sometimes Windows binds SMB to the wrong network interface. Disable VPN temporarily.
  • Look at Event Viewer. On the client, go to Windows Logs > System and filter for source MRxSmb or Bowser to see detailed error codes.
  • If all else fails, enable SMB 1.0 on both computers. While not recommended for security, some older devices (like network-attached storage) require it. Enable it via Windows Features, reboot, and test.

Frequently Asked Questions

Why does error 0x80070035 happen even when I can ping the computer?

Ping uses ICMP, while file sharing uses SMB over TCP port 445. A firewall can block port 445 while allowing ping. Check that File and Printer Sharing is allowed through the firewall.

Can I fix this error by changing network profile from Public to Private?

Yes, often. Windows blocks file sharing on public networks by default. Go to Settings > Network & Internet > Properties and set the network profile to Private.

What does SMB stand for and why does it matter?

SMB (Server Message Block) is the protocol Windows uses for file and printer sharing. If SMB is disabled or misconfigured, Windows can’t establish the network path, causing error 0x80070035.

Is it safe to enable SMB 1.0 to fix this error?

SMB 1.0 is outdated and has serious security vulnerabilities. Only enable it temporarily if you’re connecting to legacy devices, and disable it as soon as possible. Prefer using SMB 2/3.

I get the error when trying to connect to a network drive that worked before. What changed?

Likely causes: the host’s IP changed, Windows update altered SMB settings, or the firewall rules were modified. Re-check the share path and try connecting via IP.

Does this error occur on Windows 11 as well?

Yes, error 0x80070035 appears on Windows 11 too. The same fixes apply, but note that Windows 11 may have stricter default firewall settings.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →