0x80070035: The network path was not found (System error 53)
Windows can’t reach the shared folder — name resolution, SMB settings, firewall or network discovery is preventing it.
Seen on:
Windows
Meaning
Typical on home networks after updates: SMB1 removed, guest access disabled (SMB signing), Network Discovery off, or the target’s firewall blocking File and Printer Sharing.
Common causes
- Target name not resolvable (use IP to test)
- File and Printer Sharing blocked by firewall
- Insecure guest logons/SMB1 disabled for old NAS devices
- Network profile Public with discovery off
⚡ Quick fix
- Try \\IP\share instead of the name
- Enable File and Printer Sharing / Network Discovery on a Private network
- Update the NAS to SMB2/3 and use credentials instead of guest
Detailed fix by platform
PowerShell
- powershell
Test-NetConnection 192.168.1.20 -Port 445 Get-SmbClientConfiguration | Select EnableInsecureGuestLogons, RequireSecuritySignature
How to diagnose
- Reach — Port 445 open?
- Name — Works by IP?
- Protocol — NAS SMB version
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in Windows
Other ways to find it
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
Was this page helpful?
Report a correction or suggest an improvement
Last updated 7 Oct 2026