What causes system error 53?

Windows could not reach the path: the computer name will not resolve, the host is unreachable (off, different subnet, or firewalled), File and Printer Sharing is disabled on the host, the network profile is Public, or the host's Server (LanmanServer) service is stopped. It is a connection/name problem, not a wrong-password problem.

How do I fix "system error 53 the network path was not found"?

Connect by IP address (net use Z: \\192.168.x.x\Share) to test. If the IP works but the name does not, it is name resolution — use the IP, PC-NAME.local, or a hosts-file entry. If the IP also fails, on the host set the network profile to Private, enable File and Printer Sharing, allow SMB (port 445) through the firewall, and confirm the Server service is running.

Why does net use work by IP but not by computer name?

Because modern Windows has weak NetBIOS name resolution and there is no DNS entry for that PC, so the name cannot be turned into an address even though the machine is reachable. Use the IP address, the PC-NAME.local form, or add the machine to the hosts file for a durable fix.

System Error 53 — The Network Path Was Not Found (net use Fix)

What This Error Means

You run a command like net use Z: \\PC-NAME\Share and Windows answers:

System error 53 has occurred. The network path was not found.

This is the command-line cousin of the graphical error 0x80070035. It means the same thing: Windows tried to reach that path and could not — either it cannot resolve the machine's name, cannot reach the machine, or the machine is not offering the share the way you asked for it.

Error 53 is a reachability and name-resolution error, not a permissions error. If you had reached the share and been refused, you would see access denied / error 0x80070005 instead.

Root Cause 1 — The Name Does Not Resolve

The most common cause: Windows cannot turn PC-NAME into an IP address. Modern Windows has weak NetBIOS name resolution, so a bare computer name often fails even when the machine is on.

Test it — connect by IP instead of name:

net use Z: \\192.168.1.50\Share

If the IP works but the name does not, this is a name-resolution problem, not a connection problem. Find the host's IP on the host machine with ipconfig.

Fixes:

Use the IP address, or the fully qualified name PC-NAME.local.
Ensure the DNS Client service is running on both machines.
As a durable fix for a fixed host, add a line to C:\Windows\System32\drivers\etc\hosts: 192.168.1.50 PC-NAME.

Root Cause 2 — The Host Is Unreachable

If neither name nor IP works, the two machines cannot reach each other at all.

Test:

ping 192.168.1.50

No reply means a network-layer problem: the host is off, on a different subnet, on a different VLAN or Wi-Fi network, or a firewall is dropping the traffic. Confirm both machines show addresses in the same range (for example both 192.168.1.x).

The host must actually be offering SMB. If File and Printer Sharing is disabled, the ports are closed and you get error 53 even though the machine pings.

Test the SMB port from the client:

Test-NetConnection -ComputerName 192.168.1.50 -Port 445

If TcpTestSucceeded is False, port 445 is closed or blocked. On the host, enable File and Printer Sharing (Control Panel → Network and Sharing Center → Advanced sharing settings → turn it on for the Private profile) and confirm the firewall rule "File and Printer Sharing (SMB-In)" is enabled.

Root Cause 4 — The Network Profile Is Public

On a Public network profile, Windows blocks inbound sharing regardless of every other setting. A profile that silently flips from Private to Public — common after an update or reconnecting to the network — produces error 53 out of nowhere. This is the same silent failure behind computers disappearing from the network.

Fix: On the host, Settings → Network & Internet → your connection → set Network profile type to Private.

Root Cause 5 — SMB Is Disabled or the Server Service Is Stopped

If the host's Server (LanmanServer) service is stopped, or SMB has been removed, no shares are served.

On the host (elevated PowerShell):

Get-Service LanmanServer
Get-SmbServerConfiguration | Select-Object EnableSMB2Protocol

Start the service if stopped (Start-Service LanmanServer) and set it to Automatic. If SMB2 is disabled, re-enable it with Set-SmbServerConfiguration -EnableSMB2Protocol $true -Force.

Step-by-Step Diagnostic

Run these in order — each one narrows the cause:

ping HOST-IP — no reply → network/reachability problem (causes 2, 4).
Test-NetConnection HOST-IP -Port 445 — False → sharing off or firewall (cause 3).
net use Z: \\HOST-IP\Share — works by IP but not by name → name resolution (cause 1).
On the host, check the network profile is Private (cause 4) and LanmanServer is running (cause 5).

If it works by IP every time, map the drive by IP or add a hosts entry and you are done. For a whole office, the Windows networking checklist and the network settings guide turn these checks into a repeatable routine.

Why This Keeps Happening

Error 53 comes from the same fragile stack as every other Windows sharing error: NetBIOS name resolution, the discovery services, the network profile and SMB all have to line up, and Windows updates keep knocking one of them out of alignment. Tools that transfer over their own protocol and do their own discovery — Oxolan among them — sidestep error 53 entirely, because there is no \\NAME\Share path to resolve in the first place.