How to Fix ‘The Network Path Was Not Found’ (0x80070035) in Windows 11

When attempting to access a shared network folder, network attached storage (NAS) device, or another computer on the local area network using File Explorer in Windows 11 (e.g. entering \\SERVERNAME or \\192.168.1.50 into the address bar), encountering the error dialogue “The network path was not found. Error code: 0x80070035” prevents connection to the remote share. This error code indicates that the Windows SMB client (Server Message Block) cannot establish a TCP socket handshake with the destination host on port 445 or 139. The breakdown typically stems from disabled Network Discovery in Windows 11, disabled NetBIOS over TCP/IP, third-party firewall rules blocking SMB packets, unconfigured TCP/IP services (such as TCP/IP NetBIOS Helper), or name resolution failures. Resolving this issue involves enabling local sharing protocols, verifying NetBIOS settings, and opening network firewall exceptions.

Why Windows 11 Throws Error 0x80070035

When you request a UNC path like \\DESKTOP-PC\Shared, Windows initiates local hostname resolution via DNS, Link-Local Multicast Name Resolution (LLMNR), and NetBIOS over TCP/IP (NetBT). If the target computer’s IP address cannot be resolved to its NetBIOS computer name, or if the destination machine’s Windows Defender Firewall drops SMB traffic on TCP port 445, Windows terminates the connection attempt and reports error 0x80070035. Because Windows 11 defaults to Private/Public network isolation profiles that disable peer-to-peer discovery out of the box, local file sharing requires explicit configuration.

Common technical triggers include:

• Network Profile Set to Public: Windows 11 categorising the local Wi-Fi or Ethernet connection as a “Public network,” which automatically disables Network Discovery and blocks all incoming/outgoing file sharing ports. For drive reconnection stalls, see our guide on fixing Could Not Reconnect All Network Drives in Windows 11.
• Disabled NetBIOS Over TCP/IP: Network adapters configured to disable NetBIOS, preventing computer name lookups across local subnets. For file execution stalls, see our guide on fixing Windows Cannot Access Specified Device, Path, or File.
• Stopped TCP/IP NetBIOS Helper Service: The background Windows service responsible for name resolution across workgroups being disabled. For Outlook logon issues, check our guide on fixing Outlook Cannot Log On in Windows 11.
• Windows Defender Firewall Port Blockage: Third-party antivirus or Windows Firewall dropping SMB traffic on ports 137, 138, 139, and 445.

Network Protocol / Port	Operational Role	Required Healthy State
TCP Port 445 (SMB)	Direct-hosted SMB file sharing traffic	Allowed through Windows Firewall
NetBIOS over TCP/IP (NetBT)	Legacy workgroup computer name resolution	Enabled on IPv4 network adapter properties
TCP/IP NetBIOS Helper (lmhosts)	Provides NetBIOS service support	Service status: Running (Automatic)
Network Profile Type	Firewall rule grouping (Public vs Private)	Must be set to Private network

Method 1: Change Network Profile from Public to Private

Windows 11 blocks local peer discovery on Public networks. Changing the active profile to Private enables safe local network sharing.

1. Press Win + I to open the Settings app.
2. Select Network & internet in the left sidebar.
3. Click on your active connection (either Wi-Fi or Ethernet).
4. Under Network profile type, change the selection from Public network (Recommended) to Private network.
5. Next, return to Network & internet and click Advanced network settings > Advanced sharing settings.
6. Under the Private networks header, ensure both Network discovery and File and printer sharing are switched On.

Method 2: Enable NetBIOS Over TCP/IP on the Network Adapter

NetBIOS over TCP/IP allows Windows to discover network shares using local computer hostnames rather than static IP addresses.

1. Press Win + R, type ncpa.cpl, and press Enter to open Network Connections.
2. Right-click your active network adapter (Wi-Fi or Ethernet) and select Properties.
3. In the list under This connection uses the following items:, double-click Internet Protocol Version 4 (TCP/IPv4).
4. Click the Advanced… button in the lower-right corner.
5. Navigate to the WINS tab at the top.
6. In the NetBIOS setting section at the bottom, select the radio button labelled Enable NetBIOS over TCP/IP.
7. Click OK on all open dialogues to apply the setting.

Method 3: Start and Set TCP/IP NetBIOS Helper Service to Automatic

The NetBIOS Helper service enables local NetBIOS name resolution over TCP/IP networks.

1. Press Win + R, type services.msc, and press Enter.
2. Scroll through the services list to locate TCP/IP NetBIOS Helper.
3. Right-click the service and select Properties.
4. Change the Startup type from Manual to Automatic.
5. If the Service status shows Stopped, click the Start button.
6. Click Apply and OK.
7. Repeat this check for the Function Discovery Resource Publication and Function Discovery Provider Host services to ensure complete peer discovery.

Method 4: Connect via Direct IP Address Rather Than Computer Name

If local hostname resolution continues to fail, navigating directly to the remote device’s local IP address bypasses NetBIOS name lookup entirely.

1. Determine the local IPv4 address of the target machine or NAS (e.g. 192.168.1.150).
2. Press Win + R to open the Run dialogue.
3. Type the UNC path using the raw IP address:
   \\192.168.1.150
4. Press Enter. If the shared folder opens immediately, your problem is strictly related to DNS/NetBIOS name resolution rather than SMB connectivity.
5. Tip: To make this permanent, map the network share using the IP address rather than the computer name.

Method 5: Verify SMB Firewall Exceptions in Windows Defender

Ensure Windows Defender Firewall is permitting File and Printer Sharing packets through active network profiles.

1. Press Win + S, type Windows Defender Firewall, and open it.
2. In the left sidebar, click Allow an app or feature through Windows Defender Firewall.
3. Click the button at the top labelled Change settings (with administrator shield).
4. Scroll down to locate File and Printer Sharing.
5. Ensure the checkbox next to File and Printer Sharing is ticked, and crucially ensure the checkbox under the Private column is ticked.
6. Click OK. Restart your computer and access the network share.