About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
You map a drive or open a share and get:
System error 53 has occurred.
The network path was not found.
The message says the path was not found, so start with reaching the server: the name, the network path to TCP port 445, and the service listening on that port. The one cause Microsoft ties to error 53 by name is on the client, the TCP/IP NetBIOS Helper service, and it is covered below. Permissions are not the first thing to check. "Access is denied" is a different message, from a server that answered.
What you see
net useor File Explorer reports System error 53 has occurred. The network path was not found.- It can affect one server or all of them, and one client or many. Which of these is true is the first clue.
Why it happens
Some terms first, from Microsoft's SMB troubleshooting guidance. The SMB server is the computer that holds the share. The SMB client is the computer trying to reach it. SMB runs over TCP/IP, so an SMB problem can come from an underlying TCP/IP problem (Microsoft Learn, SMB troubleshooting guidance).
On Windows, file sharing is provided by the Server service (lanmanserver), and its SMB traffic uses TCP port 445. The NetBIOS ports 137, 138 and 139 are optional, according to Microsoft's port reference (Microsoft Learn, Service overview and network port requirements).
Microsoft's port-445 and Server service pages describe SMB access failures in general and do not name error 53. Their causes are the reachability checks to make. Only the last item below is one Microsoft links to error 53 directly.
- The name does not lead to the right server. It does not resolve, or it resolves to the wrong address.
- TCP port 445 is blocked between the two computers: by Windows Firewall on the server, by another firewall or device on the way, or by a security product. Microsoft's page on handshake failures says the cause is generally a local or infrastructure firewall blocking the traffic (Microsoft Learn, TCP three-way handshake failure during SMB connection).
- Nothing is listening on port 445, because the Server service on the server is stopped.
- A leftover IPsec policy blocks port 445 even though the port is listening. Microsoft documents this on servers cleaned of the Adylkuzz malware, which added an IPsec policy named
NETBC(Microsoft Learn, SMB sharing is not accessible when TCP port 445 is listening). - The TCP/IP NetBIOS Helper service on the client is stopped or running as the wrong account. Microsoft describes this case on its Windows 10 shared-folder page (Microsoft Learn, Can't access shared folders from File Explorer in Windows 10).
How to prove the cause
1. Use the command line, not File Explorer. Microsoft's shared-folder page suggests net use so you get a plain error:
net use <DeviceName>: \\<ServerName>\<ShareName>
2. Name or path? Try the same command with the server's IP address in place of its name. Microsoft's Remote Desktop troubleshooting page uses the same test: if the IP address works and the name does not, the issue is likely name resolution (Microsoft Learn, Remote Desktop can't connect to the remote computer).
3. Can the client reach port 445? From the client, in PowerShell:
Test-NetConnection -ComputerName <ServerName> -Port 445
This is the same cmdlet Microsoft's Remote Desktop page uses for port 3389, pointed at port 445 instead. TcpTestSucceeded : True means the port answers. False means something is blocking or nothing is listening.
4. Is the server listening? On the server, Microsoft's handshake page says to check there is a listener on TCP port 445, owned by the SYSTEM process:
netstat -ano | findstr :445
Get-NetTcpConnection -LocalPort 445
and that the Server service is started and running.
5. Port listening, but still blocked? Still on the server:
Check the File and Printer Sharing (SMB-In) rules are enabled under Windows Defender Firewall with Advanced Security > Inbound Rules. Microsoft also suggests turning on firewall logging to see if it records the drop.
Capture what the Windows Filtering Platform drops. Run
netsh wfp capture start, reproduce the error, then runnetsh wfp capture stop, and look for drops on port 445.Check for a blocking IPsec policy:
netsh ipsec static show policy allMicrosoft says there is no policy on a server that was never infected. A policy named
netbcpoints to the malware case.
6. Does the traffic arrive at all? Microsoft's handshake page separates two cases. If the server receives the client's connection request (SYN) and does not reply, the cause is on the server (steps 4 and 5). If the request never arrives, look at the devices on the network path between them, using a network trace on each one.
7. The client's own NetBIOS Helper. Microsoft's Windows 10 page describes a case where traces show no connection request sent, yet telnet to TCP port 445 works. The cause there is the TCP/IP NetBIOS Helper service being stopped, or running as Local System instead of Local Service.
The fix
Match the fix to the check that failed:
Name fails, IP works: correct the DNS record for the server, or the client's DNS settings.
Server service stopped: start it, and find out why it stopped. Microsoft's port reference describes it as the service that provides file, print and named pipe sharing; it follows that nothing is shared while it is down.
Firewall rule disabled: enable the File and Printer Sharing (SMB-In) inbound rules on the server.
Another device blocking port 445: fix the rule on that device. Microsoft's handshake page says to trace each device on the path to find which one drops the traffic.
IPsec policy
netbcpresent: Microsoft's resolution is to install the MS17-010 security update for the operating system, follow Microsoft's removal guidance for Win32/Adylkuzz.B, run the Microsoft Security Scanner, and then delete the policy:netsh ipsec static delete policy name=netbcTreat this as a security incident, not only a file sharing fault.
TCP/IP NetBIOS Helper wrong on the client: set it to run as Local Service, as Microsoft's page says.
How to confirm the fix
Test-NetConnection … -Port 445returnsTcpTestSucceeded : True.net usewith the server name connects.- If a firewall or IPsec block was the cause, the WFP capture no longer shows drops on port 445.
What to watch afterwards
- Firewall rule changes that turn the File and Printer Sharing (SMB-In) rules off again.
- New devices on the path, such as a firewall between offices or a VPN.
- Any sign of the IPsec case returning. Microsoft's page links that case to malware that uses the same SMBv1 vulnerability as Wannacrypt.
Read next
Related articles you may want next.
- TroubleshootingSMB Signing Now Required: NAS and Old Client Access FailuresNAS share fails after Windows 11 24H2 or Server 2025? Tell signing (STATUS_INVALID_SIGNATURE) from blocked guest access, audit with SMBClient events, fix the device first.Read article
- TroubleshootingFirewall Rules Stopped After a Move? Check the ProfileServices refused after a Windows server move? Read each connection's network category, trace why domain detection failed and fix that, not the rules.Read article
- TroubleshootingMapped network drives show a red X after sign-in: idle disconnects, network timing and policyA red X on a mapped drive can mean an idle connection that reconnects when you open it, a drive mapped before the network was up, a program running elevated, or a Group Policy drive map clearing other drives. Prove which one before you change anything.Read article
Risks and limits
- Microsoft's Windows 10 shared-folder page also lists steps such as turning on SMB 1.0, giving Everyone full control and enabling insecure guest logons. Those are about other errors, not error 53, and they weaken security. Microsoft's SMB guidance says to disable SMBv1. Do not use those steps to fix error 53.
- If the server answers but then refuses you, you will see a different message (access denied, or a signing or guest access error). That is a different problem from this one.
- On a DFS namespace path, Microsoft lists "The Network Path was not found" among the DFS access errors, where the cause is the referral (Microsoft Learn, Troubleshoot DFS Namespace access failures). Check the referral before the file server.
Sources
- Microsoft Learn, "Can't access shared folders from File Explorer in Windows 10", last updated 12 February 2026: https://learn.microsoft.com/en-us/troubleshoot/windows-client/networking/cannot-access-shared-folder-file-explorer
- Microsoft Learn, "TCP three-way handshake failure during SMB connection", last updated 12 February 2026: https://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/tcp-three-way-handshake-fails
- Microsoft Learn, "Service overview and network port requirements for Windows", last updated 12 February 2026: https://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/service-overview-and-network-port-requirements
- Microsoft Learn, "SMB sharing is not accessible when TCP port 445 is listening in Windows Server", last updated 12 February 2026: https://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/smb-sharing-not-accessible-when-tcp-port-445-listen
- Microsoft Learn, "SMB troubleshooting guidance", last updated 12 February 2026: https://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/troubleshoot-smb-guidance
- Microsoft Learn, "Remote Desktop can't connect to the remote computer", last updated 12 February 2026: https://learn.microsoft.com/en-us/troubleshoot/windows-server/remote/remote-desktop-cannot-connect-remote-computer
- Microsoft Learn, "Troubleshoot Distributed File System Namespace access failures in Windows", last updated 12 February 2026: https://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/dfsn-access-failures
Next step
Error 53 is a reachability fault: check the name first, then port 445, then the service on the other end. NetLeverage has looked after business servers since 2002. If your shares still can't be reached, talk to us through managed support with the net use error and the Test-NetConnection result for port 445.
This article was originally published on .