Skip to content

Est. 2011ยทMicrosoft Partner ID 7033487ยทDelivery under 3 minยทSupport 7 days a week

Your vault is empty.

Free Fix 0x80070035

Error 0x80070035: the network path was not found when opening a share

10 min read Updated October 5, 2026 Networking, Sharing & Printing

Fix it now

0x80070035 is Win32 53, ERROR_BAD_NETPATH, “The network path was not found”. The client could not find the machine, so it never got as far as checking a credential. Share permissions, NTFS rights and account problems are all the wrong place to start: either the name did not resolve, or nothing answered on TCP 445.

Run these on the failing client, in PowerShell, in order

Test-NetConnection fileserver -Port 445
Resolve-DnsName fileserver
Get-NetConnectionProfile
Get-Service LanmanWorkstation
  1. Try the address instead of the name: type \\192.168.1.10\share into Explorer, substituting the real address. If that opens, the fault is name resolution and nothing else.
  2. Read the Test-NetConnection result. TcpTestSucceeded : False means nothing is answering on 445, so stop adjusting client settings and look at the host and the firewall.
  3. On the machine hosting the share, run Get-NetConnectionProfile and confirm the network category is Private. File sharing is blocked on a Public profile by design.
  4. Retry with net use \\fileserver\share. It reports a more specific message than Explorer does; Microsoft names “System error 53 has occurred. The network path was not found” as the command-line form of this failure.
  5. On the host, confirm network discovery and file and printer sharing are on for the profile in use, from Control Panel, Network and Internet, Network and Sharing Center, Advanced sharing settings.

Do not re-enable SMB1 for this. 0x80070035 is a path failure, not a protocol one, and a device that only speaks SMB1 fails with a different code.

If the share opens by name you are done. If not, the next section separates the three things that happen before a password is ever checked.

Why it happens

Opening a share is three separate operations that people think of as one. The name is turned into an address. A connection is made to that address on TCP 445. Only then do the two machines negotiate a protocol version and start talking about who you are. 0x80070035 is raised in the first two steps, which is why changing share permissions never fixes it and why the account you are using is almost certainly innocent.

On a domain network the first step is DNS and behaves predictably. On a workgroup or home network it falls back to local discovery, several parts of which are switched off when the network profile is Public. A profile that flips to Public – which happens routinely after a new adapter appears, a dock is connected, or a network is reconnected – takes file sharing with it on both the client and the host, and nobody changed a setting.

The companion codes describe the same journey failing at slightly different points, and Microsoft’s published wording for each is more useful than the paraphrases in circulation. 0x80070033 is Win32 51, ERROR_REM_NOT_LIST: “Windows cannot find the network path. Verify that the network path is correct and the destination computer is not busy or turned off.” 0x800704B3 is Win32 1203, ERROR_NO_NET_OR_BAD_PATH: “The network path was either typed incorrectly, does not exist, or the network provider is not currently available” – note that a typo is the first thing Microsoft lists, not the last. 0x8007003A is Win32 58, ERROR_BAD_NET_RESP: “The specified server cannot perform the requested operation”, which means the server did answer.

The name does not resolve

You have this one if The share opens by address and fails by name, every time, from every application.

  1. On a domain network, check the host has a current DNS record and the client uses domain DNS servers.
  2. Clear stale entries with ipconfig /flushdns before retesting.
  3. On a workgroup network, use the address in a mapped drive, or a hosts file entry if the address is fixed.
  4. Reserve the host an address in DHCP if it keeps moving.

Nothing is answering on the file sharing port

You have this one if Test-NetConnection -Port 445 returns false, and the address does not work either.

  1. Confirm the host is powered on and awake. Sleeping machines are the commonest cause on small networks and the easiest to overlook.
  2. Check the firewall on the host allows file and printer sharing for the profile the network is currently using, not for the profile you assume it is on.
  3. Where a third-party security product manages the firewall, check its rules rather than the Windows ones.
  4. Between subnets or across a VPN, confirm nothing in the path blocks TCP 445.

The network profile is Public on one of the machines

You have this one if Sharing worked and then stopped for no obvious reason, often after a reboot, a new adapter or a reconnection.

  1. Run Get-NetConnectionProfile on both machines and read the NetworkCategory.
  2. On a network you trust, set it to Private: Set-NetConnectionProfile -InterfaceAlias Ethernet -NetworkCategory Private.
  3. Confirm network discovery and file and printer sharing are on for the private profile in Advanced sharing settings.
  4. On a domain-joined machine, expect the profile to be DomainAuthenticated, and investigate why it is not if it shows as Public.

The client’s own sharing components are missing or disabled

You have this one if 0x800704B3, or the client fails against every share on the network while other clients are fine.

  1. Open the adapter properties and confirm Client for Microsoft Networks is present and ticked.
  2. Confirm the Workstation service is running and set to start automatically: Get-Service LanmanWorkstation.
  3. Check the SMB client has not been removed from the machine as part of a hardening exercise.
  4. Reset the network stack only as a last step, and reboot afterwards, since these bindings are read at startup.

The host is not sharing anything

You have this one if The host answers on 445 but no share can be opened, and the share list is empty.

  1. On the host, confirm the Server service is running and that at least one share exists.
  2. Recreate the share and check its name. A name ending in a dollar sign is deliberately hidden from browsing but still reachable if you type it.
  3. Check the host has not been hardened to refuse inbound file sharing altogether.

Full reference

The four codes with their published wording

Code Win32 Published meaning
0x80070035 53 The network path was not found
0x80070033 51 Windows cannot find the network path. Verify that the network path is correct and the destination computer is not busy or turned off
0x800704B3 1203 The network path was either typed incorrectly, does not exist, or the network provider is not currently available
0x8007003A 58 The specified server cannot perform the requested operation

The distinction that saves time is between 0x8007003A and the other three. The first three all mean nothing useful came back. 0x8007003A means the server answered and declined, which moves the investigation to the host and off the network.

Splitting name resolution from reachability

Test result What it tells you
The address works, the name does not Name resolution only. The host and the share are fine
Neither works, and the port test fails The host is unreachable, or file sharing is blocked at it
The port test succeeds but Explorer still fails Negotiation or the share itself, not the network path
It works from one machine and not another Compare the two clients’ network profiles, then their firewall rules
It works until the machine sleeps or reconnects The profile is changing, or the host is asleep

Commands worth having in order

Command What it answers
Test-NetConnection <host> -Port 445 Is anything listening for file sharing at that address
Resolve-DnsName <host> What does the name resolve to, and from which server
ipconfig /flushdns Clears cached answers so the next test is real
Get-NetConnectionProfile Which profile the adapter is on, which decides the firewall rules in force
Get-Service LanmanWorkstation Is the SMB client service running at all
net use \\host\share A more specific message than Explorer gives, including “System error 53 has occurred”

The workgroup case, which behaves differently

Without a domain there is no authoritative name service, so a share that opened yesterday can be unreachable today because the discovery mechanism the client was relying on is not running, or because the host’s address changed. On a small network the reliable arrangement is a reserved DHCP address for anything that shares files, and mapped drives that use either that address or a hosts file entry. That is not a workaround so much as an acknowledgement that name resolution on a workgroup network is best-effort.

  • Reserve an address for every machine that shares anything.
  • Keep both machines on the Private profile, and check after every dock, VPN or adapter change.
  • Prefer a mapped drive to browsing, because browsing depends on discovery and a mapped drive does not.
  • If a device sleeps, either stop it sleeping or accept that the share is unavailable while it does.

Resetting the network stack is a genuine last resort, not a routine step. It clears the machine’s TCP/IP configuration and the layered components installed above it, so static addresses, proxy settings and anything a VPN or security client registered there are lost and have to be put back. Record the current configuration first, and reboot afterwards.

Every code this article covers

Code What it points at Source
0x80070035 Win32 53, ERROR_BAD_NETPATH: the network path was not found. The command line reports it as “System error 53 has occurred” Microsoft Learn
0x80070033 Win32 51, ERROR_REM_NOT_LIST: Windows cannot find the network path. Verify that the path is correct and the destination computer is not busy or turned off Microsoft Learn
0x800704B3 Win32 1203, ERROR_NO_NET_OR_BAD_PATH: the network path was either typed incorrectly, does not exist, or the network provider is not currently available Microsoft Learn
0x8007003A Win32 58, ERROR_BAD_NET_RESP: the specified server cannot perform the requested operation Microsoft Learn

Confirm the fix worked

  1. Open the share by name, not only by address.
  2. Confirm Test-NetConnection <host> -Port 445 returns TcpTestSucceeded True from the client.
  3. Reboot both machines and confirm the share still opens without intervention.
  4. Check a mapped drive reconnects at logon rather than showing a red cross.
  5. Confirm Get-NetConnectionProfile still reports the expected category after a reconnect or a dock.

Questions people ask about this

Do I need to buy anything to fix this?

No, and nothing here costs money. This is a name resolution and connectivity fault, fixed with settings already present in Windows. No licence changes any of it.

Should I re-enable SMB1 to make an old device work?

Not for this error. 0x80070035 is a path failure, not a protocol one. A device that only speaks SMB1 produces a different code, and re-enabling that protocol carries real security cost for every connection the machine makes.

Why does it work from one PC and not another on the same network?

Compare the two network profiles first, then the firewall rules, then whether the working machine has a mapped drive or a cached answer that predates the change.

Is mapping a drive to the IP address a reasonable long-term answer?

On a small fixed network with a reserved address, yes, and it removes a whole layer of failure. In a domain it is a workaround that hides a DNS problem somebody should fix.

The port test succeeds but Explorer still fails. What now?

You are past the part this article covers. Something answered on 445, so the fault is in negotiation, in the share, or in authentication – which means a different code and a different article. Run net use to get the more specific message.

Related error codes

Was this article helpful?

Your feedback helps us improve our documentation.

Related articles

Free Fix VPN error 868: the remote access server name could not be resolved Free Fix 0xC0000234 account locked out and other logon states that block shares Free Fix Remote Desktop cannot verify the identity: certificate error 0x80090325 Free Fix Error 0x80070052: the directory or file cannot be created on a share
โ† Back to Knowledge Base