ERROR_BAD_NETPATH (0X00000035): Network Path Not Found Fix

Quick Answer

Check the share name for typos, ensure the host is reachable via ping, and enable SMB 1.0/CIFS File Sharing Support (if the remote device needs it—like old NAS or printer). Most of the time, it's a simple mistake in the path or a firewall rule blocking port 445.

Why This Happens

I know this error is infuriating. You type a UNC path like \server\share and Windows stares back at you with 0X00000035. The network path was not found. But here's the thing: this error is almost never about the physical network cable being unplugged. It's about Windows failing to resolve the name or connect to the specific share. I've seen it most often in three scenarios:

• You're trying to access a shared folder on a device that has SMB1 disabled (Windows 10/11 default turns it off).
• The firewall on the remote machine or a network firewall is blocking TCP port 445 (SMB).
• You mistyped the path—it happens to everyone, even me after 6 years on the help desk.

Here's the full fix flow.

Fix Steps

1. Verify the path. Type the UNC path exactly. No trailing spaces. Use \server\share—note the double backslashes. A single backslash and you'll get this error every time. Check if the share name is case-sensitive? Usually not, but some Linux-based NAS devices are.
2. Ping the host. Open Command Prompt and run ping server. If it fails, the hostname isn't resolving. Use the IP address instead: \\192.168.1.100\share. If ping works but the error persists, the issue is at the SMB layer.
3. Check the SMB protocol. Modern Windows (10/11, Server 2019+) disables SMB1. If the target is a Windows 7 machine, a network drive, or an older NAS, you might need SMB1. Enable it via Control Panel > Programs and Features > Turn Windows features on or off > SMB 1.0/CIFS File Sharing Support. Restart after enabling. This is the fix for most people hitting this error with older devices.
4. Check Windows Firewall. On the machine hosting the share, ensure the rule "File and Printer Sharing" is enabled for the correct profile (Private, Domain, or Public). A quick test: disable the firewall temporarily (on the host) and see if the error clears. If it does, create a custom inbound rule for TCP port 445.
5. Enable NetBIOS over TCP/IP. This helps if you're using hostnames. In Network Connections, right-click your adapter > Properties > Internet Protocol Version 4 (TCP/IPv4) > Properties > Advanced > WINS tab > Enable NetBIOS over TCP/IP.

If None of That Works

Try these alternative fixes:

• Use the IP address and the admin share. Type \\192.168.1.100\C$ (replace IP with the host's IP). If that works, the issue is with the specific share, not the network.
• Restart the Server service. On the remote machine, run net stop server && net start server in an admin prompt.
• Check DNS. If ping fails but you know the machine is online, flush DNS: ipconfig /flushdns and try again. Also check the hosts file at C:\Windows\System32\drivers\etc\hosts for any stale entries.
• Map the drive with different credentials. Run net use * \\server\share /user:username from command line—it'll prompt for password. Sometimes the cached credentials are wrong.

Prevention Tip

Once you've fixed it, avoid future pain by documenting the share's exact path in a note. If it's a device you control, set a static IP for the host—then use the IP in the UNC path. That way DNS issues won't trip you up again. And if you're the admin, leave SMB1 disabled unless absolutely needed—it's a security risk. The real fix is usually just enabling SMB1 or fixing the path. But I've seen this error so many times I can spot it from across the room.