- Understanding the origin of 0x80070035 narrows the diagnosis and avoids blind testing.
- Services, firewall, and name resolution are the key trio for SMB in Windows 11.
- Prioritize SMB2/3, limit SMB1, and use well-configured permissions/credentials.
When Windows 11 displays the "Network path not found" warning when you try to open a shared folder on another computer, you may feel completely blocked. In reality, this message means the system can't locate the resource you're trying to access via SMB, either due to a network, permissions, services, or name resolution issue. There is almost always a logical cause and an orderly solution.
In this guide, I offer a clear and practical guide to identifying what's wrong and how to fix it in Windows 11, without wasting time fumbling around. We'll cover quick checks, sharing settings, services and firewall, DNS/NetBIOS, SMB versions, permissions, and diagnostic commands. go from the basics to the specificLet's learn all about the error “Network path not found” when accessing another PC.
What exactly does "Network path not found" (0x80070035) mean?
This error appears when Windows can't reach or recognize the network resource you specify (for example, \\COMPUTER\Folder). This could be because the other computer is turned off, a firewall is blocking it, the name doesn't resolve, the SMB server service isn't running, or there's an SMB version mismatch. Windows cannot find the path due to access blocking or resolution.
Although the message is generic, it usually fits into four categories: connectivity (the remote computer is not responding), discovery and naming (does not resolve \\NAME), services and ports (SMB blocked or stopped), and permissions/credentials (you do not have rights to log in). fit the symptom into a category.
It's also worth remembering that SMB primarily operates over TCP port 445 and, in older environments, may use NetBIOS (ports 137-139). If these ports are filtered by a firewall, the client will not be able to reach the file server. 445 open towards destination is essential.
Finally, Windows 11 prioritizes SMB 2/3 and disables SMB 1.0 by default (for security reasons). Older devices or NAS that only support SMB 1 can cause incompatibilities. use SMB2/3 and avoid SMB1.
Quick checks that rule out the obvious
Before touching advanced settings, it's a good idea to check the basics. Although they may sound basic, these steps fix a large number of issues. simple steps are critical.
- Is the other PC on, logged in, and not in sleep mode? If the computer sleeps, the resource stops responding..
- Are both devices on the same network and using the Private network profile? In Settings > Network & Internet > Connection Properties, select the network as Private. The Public profile blocks sharing by default..
- Test by IP address: In Explorer, type \\IP\ShareName. If the IP address works but the name doesn't, the problem is a resolution issue. This quickly separates DNS/NetBIOS from SMB.
- Ping the other device (ping IP or ping NAME). If there's no response, check connectivity, Wi-Fi/Ethernet, and VPNs. Without IP connectivity, SMB has nowhere to go.
- Temporarily disconnect VPNs, proxies, or third-party security filters to avoid blockages. Many VPNs cut local traffic to 445.
If these basic tests fail, fix them first. If they work (for example, you're arriving by IP but not by name), you already have a clear clue as to where to go next. Narrowing the problem speeds up resolution.
Turn on sharing and discovery in Windows 11
To make a computer visible and share folders, you need to turn on two toggles: network discovery and file and printer sharing. In Windows 11, go to Control Panel > Network and Sharing Center > Change advanced sharing settings. Turn on discovery and sharing in Private.
Also, make sure you're sharing the appropriate folder on the destination computer: right-click > Properties > Sharing > Advanced Sharing. You can allow read or read/write access and limit it to specific users. share with appropriate permissions.
In home environments, it's sometimes worth temporarily disabling "Password-protected sharing" in that same panel (only on trusted networks). This allows access without a username or password, but reduces security. values security over comfort.
In Explorer, try entering the full UNC path: \\PC-NAME\Shared or \\192.168.1.X\Shared. Sometimes, mapping a network drive with "Map Network Drive" makes it easier to access and maintain. a mapped unit provides stable path.
Essential Services and Firewalls for SMB
SMB relies on several system services. In services.msc, verify that "LanmanServer" and "LanmanWorkstation" are running and set to "Autostart." Active Server and Workstation. You can start in Windows Safe Mode with Networking to check services if you think some configuration or software is blocking normal startup.
For discovery, also check: "Role Discovery Provider Host (FDResPub)", "Role Discovery Resource Publication (FDResPub)", "DNS Client", and optionally "SSDP Discovery" and "UPnP Device Host". discovery services enabled.
In Windows Defender Firewall, go to Inbound Rules and confirm that "File and Printer Sharing (SMB-In)" is enabled in the Private profile. If you're using a third-party firewall, create a rule to allow TCP 445 on the local network. 445 closed prevents SMB.
If there are strict corporate security policies or firewall profiles, verify that the destination computer is on the allowed segment. On managed networks, the administrator may have isolated subnets. Segmentation can block access.
Computer name, DNS and NetBIOS: Let them find you
If \\NAME doesn't work but \\IP does, the problem is name resolution. For home networks, the router's DNS or mDNS is usually sufficient; for offices, the domain's DNS is sufficient. clear caches with ipconfig /flushdns and consider advanced options such as Encrypt your DNS without touching your router to avoid external interference.
Use ipconfig /all to verify that you have the correct DNS server and that there are no old, static IP addresses pointing elsewhere. If the computer name contains strange characters or has recently changed, restart both computers to propagate it. name consistency on the network.
For environments that still rely on NetBIOS, enabling “NetBIOS over TCP/IP” in IPv4 > Advanced > WINS properties can help, although today it’s common to rely on DNS. use NetBIOS only as a last resort.
If you suspect the router, try reserving IP addresses via DHCP so they don't change and thus minimize resolution conflicts. You can also create a local entry in C:\Windows\System32\drivers\etc\hosts for testing (temporary only). reserving IP reduces conflicts.
SMB in Windows 11: Versions, Compatibility, and SMB1
Windows 11 uses SMB 2/3 by default and disables SMB1 for security reasons. If you try to access a NAS or very old device that barely supports SMB1, the client will fail with messages like "network path not found" or incorrect credentials. update or enable SMB2/3.
Only if there is no alternative, you can temporarily enable SMB1 from Windows Features: Control Panel > Programs and Features > Turn Windows features on or off > "SMB 1.0/CIFS file sharing support" (client). enable SMB1 only temporarily.
In PowerShell, you can check the status: Get-SmbServerConfiguration and Get-SmbClientConfiguration show whether SMB1/2/3 are enabled. Set-SmbServerConfiguration -EnableSMB2Protocol $true to ensure that SMB2/3 are active on the server. Verify SMB settings with PowerShell.
Another sticking point is guest logins. Windows 11 blocks them by default because they're insecure. If a resource requires guest logins, there's a policy (Enable insecure guest logins in Lanman Networking), but it's not recommended. use password-protected accounts instead of guest accounts.
Permissions, accounts and credentials: let them pass you by
To open a shared folder, you need two layers: sharing permissions and NTFS permissions. If either of these denies access, you'll see path or credential errors. user with NTFS reading and sharing.
If you access the system from a computer outside the domain or with another account, the system may prompt you for a username and password. Use Credential Manager (Control Panel) to create a Windows credential pointing to \\PC-NAME with the local user name of the target computer (for example, COMPUTER\\User). saving credentials prevents errors.
Mapping a drive with "Map Network Drive" can be simple: choose a letter, paste \\COMPUTER\\Shared, and select "Connect with different credentials" if applicable. You can also use the console: net use Z: \\EQUIPO\\Compartido /user:EQUIPO\\Usuario. map drive check permissions and path.
If everything looks fine but you're still not logged in, temporarily create the "Everyone" group with read permissions on the shared folder to rule out identity issues. Once confirmed, return to a secure configuration. Testing "All" temporarily clarifies the origin.
Useful commands and diagnostics
These commands will help you locate the exact point of failure and, at the same time, clean up old connections that may be interfering. execute these commands with permissions.
ping NOMBREyping IP: confirms basic connectivity. If ping by name fails, think about DNS.Test-NetConnection -ComputerName IP -Port 445(PowerShell): Check the SMB port. If 445 does not respond, the firewall or route cuts off the passage.net viewynet view \\EQUIPO: lists available resources. If nothing is returned, there is a visibility or permissions problem..net useynet use * /delete: View and delete stuck mapped connections. Clearing sessions resolves credential conflicts.ipconfig /flushdns,ipconfig /registerdns,nbtstat -R: refresh name caches. Ideal after IP or team name changesIf your troubleshooting fails, you can also review guides on localhost issues and troubleshooting in Windows 11.netsh winsock resetynetsh int ip reset: reset TCP/IP stack. Useful if the problem persists after ruling out everything else.
You can also check the Event Viewer under Applications and Services Logs > Microsoft > Windows > SMBClient/Connectivity and SMBServer. Specific connection and authentication errors appear there. review events for detailed clues.
Typical scenarios: NAS, routers, VPNs, and small offices
Older NAS (or TVs, disk-based printers) may require SMB1 or guests. If you can't upgrade, temporarily enable the SMB1 client in Windows and assign a Private network with a relaxed firewall. planning migration to SMB2/3.
With VPNs active, many settings block traffic to the local LAN for security reasons. Look for an option like "Allow access to the local network" or disconnect the VPN while accessing the resource. VPN usually blocks local traffic.
On routers with Wi-Fi client isolation (AP Isolation), wireless devices can't see each other. Disable it or connect the sharing device via a cable. disable Wi‑Fi client isolation.
For SMBs, combining Windows 11 with Azure AD-joined computers may require explicit authentication (corporate email) or local file server credentials. If this fails with a Microsoft account, try creating a local mirror user with the same password on both computers. create local mirror users.
Good practices so that it doesn't happen again
Set DHCP-reserved IP addresses for file-sharing computers, use clear computer names, and avoid renaming them frequently. stability in names and IPs.
Maintain the Windows Firewall with appropriate rules for the Private profile and uninstall duplicate firewalls if they're not essential. Third-party antivirus software should respect SMB; if not, create exclusions for 445 on the local subnet. avoid duplicate firewalls.
Update Windows 11 and the firmware on your NAS or router. Recent versions of SMB bring performance and security improvements, and fix incompatibilities. Update OS and firmware regularly.
Avoid SMB1 unless required, disable anonymous invitations, and use password-protected accounts. Document which folders you share and with what permissions. Do not reactivate SMB1 or anonymous invitation.
Quick Solution Checklist
- Connectivity and network profile: ping OK, Private network, no VPN blocking. No IP base, no SMB.
- Discovery and sharing enabled; folder successfully shared. Share wisely.
- Server/Workstation Services running; firewall allows 445. Open ports where appropriate.
- Name resolution: \\IP and \\NAME work; clean caches. If IP yes and name no, check DNS.
- SMB2/3 enabled; SMB1 only if no other option exists and only temporarily. Compatibility without sacrificing security.
- NTFS and resource permissions aligned; credentials saved if applicable. Access granted to whom it should be.
If you've followed the path and tested by IP, confirmed services and firewall, checked name resolution and adjusted permissions, the error 0x80070035 should normally disappear. when connectivity, discovery, SMB and permissions are aligned. Now you know much more about the error “Network path not found” when accessing another PC.
Passionate about technology since he was little. I love being up to date in the sector and, above all, communicating it. That is why I have been dedicated to communication on technology and video game websites for many years. You can find me writing about Android, Windows, MacOS, iOS, Nintendo or any other related topic that comes to mind.