“Network path not found” error when accessing another PC: How to fix SMB in Windows 11

If you're faced with the message "Network path not found" when trying to open a shared folder or network resource, don't worry: you're not the first. This warning typically appears in Windows 11 when the computer is unable to locate or access the UNC path of another PC or NAS. This could be due to a firewall blocking port 445, a problem with network discovery, the SMB service, or a simple name resolution failure. The good news is that with an orderly review of adjustments and tests, it can usually be fixed in minutes..

In this article, you'll find a clear, straightforward walkthrough of how to diagnose and fix SMB resource access in Windows 11. We'll cover quick checks, services that should be running, firewall rules, SMB version support, permissions and credentials, verification commands, and some advanced settings for environments with legacy devices or NAS. The idea is that you can get back into \\PC\Folder or \\IP\Resource without any headaches. Let's learn all about the error “Network path not found” when accessing another PC.

What does “Network path not found” really mean?

The message indicates that Windows could not resolve or reach the network path you entered. In SMB, paths use the UNC format, for example \\COMPUTER\Shared or \\192.168.1.50\Shared. If the system cannot translate the name to an IP address, or if it cannot connect to the remote host's SMB port (TCP 445), you will see this error. So the causes are usually divided into name resolution, connectivity and permissions/firewall.

Windows 11 uses SMB 3.x by default, which runs over TCP 445 and no longer requires NetBIOS over TCP/IP as it once did. So if something blocks that port, if there's a policy requiring signing or encryption that the other end doesn't support, or if the remote machine has an incompatible version of SMB, the connection will fail. It can also be as simple as a mistyping of the shared folder name..

To start, make sure the route exists and the remote device is powered on. Test it with the IP and name to narrow down whether the problem is a naming issue (DNS/LLMNR) or a pure connectivity issue. If it works with \\Shared\IP and not with \\Shared\Name, the focus is on the resolution.

Quick checks that save you time

Before getting into advanced settings, there are some basics that are worth ruling out. Many incidents are resolved at this point.:

• Confirm that both devices are on the same network or have routes between them (same segment or routed subnet).
• Try accessing with IP: type \\192.168.xx\ResourceName in the Explorer.
• Ping the host: Open a console and run ping NAME and ping 192.168.xx to check name resolution and latency.
• Run a port test: In PowerShell, Test-NetConnection -ComputerName NAME -Port 445. If port 445 is closed, SMB will not connect.
• Verify that the network profile is Private in Settings > Network & Internet (Public networks restrict discovery and sharing).
• Check the date and time: large discrepancies break authentication and signature.

One detail that often goes unnoticed: if the shared resource has been deleted or renamed, the client will still not be able to find it even if the network is perfect. Validates that the folder is still shared on the remote computer.

Turn on network discovery and file sharing

Windows 11 disables certain options by default on networks marked as Public. Check the following: It is the pillar for other teams to see you and you can see them..

• Go to Settings > Network & Internet > Advanced network settings > Advanced sharing options.
• Under Private Profiles, turn on Network Discovery and Enable automatic configuration of devices connected to the network.
• Also turn on File and Printer Sharing.
• Under All Networks, you can enable Password Protected Sharing (recommended) or disable it if you need guest access on a trusted network. Disabling it allows entry without a user, but reduces security.

After applying this, try accessing via UNC again. If the host still doesn't appear, remember that Network Explorer relies on discovery mechanisms (WS-Discovery/LLMNR) that sometimes fail, so typing \\Shared IP\ directly is still the most reliable test. Enabling sharing is necessary, but not always sufficient..

Essential Windows Services for SMB and Discovery

Some system services must be running for SMB discovery, publishing, and resource access to work. Open services.msc and check: Without these, the network remains “blind”.

• Server (LanmanServer): publish your shares.
• Workstation (LanmanWorkstation): SMB client of the system.
• Feature Discovery Provider Host (FDResPub) and Feature Discovery Resource Publishing: Advertise your resources.
• DNS Client and DHCP Client: essential for names and IP addresses.
• SSDP Discovery and UPnP Device Host: Help with discovery on some networks.
• Network Location Awareness (NLA): Classifies the network profile.
• NetBIOS over TCP/IP support – only if you rely on NetBIOS in legacy environments.

Set them to Autostart (where applicable) and start them if they are stopped. A reboot after the change sometimes speeds up the computer appearing on the network..

Firewall and Antivirus: Pave the Way for SMB

The key port for modern SMB is TCP 445. On older computers, TCP 139 and UDP 137–138 (NetBIOS) may also come into play, but on Windows 11, 445 is the norm. If the firewall blocks 445, you will see “Network path not found” or timeouts.

• In Control Panel > Windows Defender Firewall > Allow an app, verify that “File and printer sharing (SMB-In)” is allowed on at least Private networks.
• If you're using a third-party firewall (or antivirus), create an inbound rule for TCP 445 on the computer hosting the shared folder.
• Temporarily disable the firewall to test. If it works, turn it back on and adjust the rules. Don't leave it permanently disabled.

With third-party antivirus, some include “smart firewalls” or traffic inspection that can interfere with SMB. Consider a local network or SMB exclusion to avoid “silent” lockouts..

SMB Versions and Support: SMB1, SMB2/3, Signing and Encryption

Windows 11 comes with SMB 2/3 enabled and SMB 1 disabled for security. If you're accessing older devices (very old NAS, printers with storage, Windows XP/Server 2003, etc.), they may only speak SMB 1. Avoid SMB1 unless strictly necessary.

Check from PowerShell: executes diagnostic commands

Get-SmbClientConfiguration
Get-SmbServerConfiguration
Test-NetConnection -ComputerName NOMBRE -Port 445

If you need SMB 1 support temporarily, go to Windows Features and enable "SMB 1.0/CIFS" (client or server as needed). Use it minimally and only on trusted networks. Another alternative is to update the NAS firmware or switch to a device that supports SMB2/3..

Also check SMB signing/encryption: If one endpoint requires signing and the other doesn't, the connection fails. In local policies (gpedit.msc): Computer Configuration > Administrative Templates > Network > Microsoft Network Workstation/Server, set "Digitally Sign" to suit your environment. In home environments, forcing a signature is often unnecessary and may break compatibility with older devices..

Permissions and Credentials: NTFS + Sharing

Just because the path exists and the port is open isn't enough; you need the appropriate permissions on the shared resource and the file system. On the sharing computer, open Folder Properties > Sharing > Advanced Sharing and check for users or groups with access. For testing, you can give “Read” to “Everyone” and then fine-tune.

On the Security (NTFS) tab, make sure that same account or group has read/write permissions as appropriate. Remember: the effective permission is the intersection of NTFS and Shared. One allowing and the other denying blocks access..

On the client, if prompted for credentials, enter the username and password for the remote computer (or domain, if applicable). You can save them in the Credential Manager so you don't have to type them every time. If a user with the same name and password exists on both computers, authentication is more transparent..

To map with a specific user from the console:

net use \\SERVIDOR\Compartida /user:SERVIDOR\Usuario LaContraseña /persistent:yes

If it returns “Access denied” but not “Network path not found,” you’ve made progress: you’ve reached the host and it’s time to fine-tune permissions or credentials. They are different errors that should be differentiated..

Resolving names: DNS, LLMNR, and NetBIOS

If \\Shared IP\works but \\Shared Name\doesn't, the problem is a troubleshooting issue. On home networks, sometimes the router doesn't resolve Windows hostnames. Try always using the IP or creating entries in the hosts file as a quick fix..

Try these commands to diagnose name resolution and caches

ping NOMBRE
ping 192.168.1.50
nbtstat -R
ipconfig /flushdns

In environments with DNS own (office/domain), check that clients are using the correct DNS server and that an A record exists for the host. LLMNR and mDNS can help on small networks, but they are not foolproof. For testing, mapping with the IP quickly clears up any doubts..

Clean up connections and restart the network stack

Sometimes the problem stems from stuck SMB sessions or cached credentials. Clean and restart network components: It is a miracle cure after several failed attempts..

net use * /delete /y
ipconfig /flushdns
ipconfig /registerdns
nbtstat -R
netsh winsock reset
netsh int ip reset

Restart your computer after running these commands. Then try accessing the Shared IP address again. If it works now, the problem was with caches or bad sockets..

Local policy settings for mixed environments

On networks with older devices or servers with strict policies, the client and server may not “negotiate” well. Open gpedit.msc to review the policies and adjust as appropriate:

• Computer Configuration > Administrative Templates > Network > Microsoft Network Workstation: Require digital signature (disable this if the server doesn't support it during testing).
• Computer Configuration > Administrative Templates > Network > SMB Client/Server: SMB dialect minimums and maximums if your environment requires it. Generally leave SMB2/3 as default.
• Computer Configuration > Administrative Templates > Network > Microsoft Network Workstation > Insecure Guest Logon: Enable this only if you need guest access to legacy devices.
• Security Settings > Security Options > Network Security: LAN Manager Authentication Level: Use NTLMv2 if possible; lower the level only for legacy computers, knowing the risk.

To log in with local administrative accounts over the network on some editions, you may need to create the registry value LocalAccountTokenFilterPolicy=1 in HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System. Use it wisely and only on trusted networks..

Revisions on the computer that shares the folder

If the problem persists, focus on the host that “serves” the folder: That's where you'll find the most clues..

• Confirm that the “Server (LanmanServer)” service is running.
• Check that the folder is actually shared and that the resource name is correct (Properties > Sharing > Advanced Sharing).
• Open Event Viewer > Windows Logs > System and look for entries related to “Srv”, “SMBServer” or “LanmanServer”.
• Check that no security software is blocking incoming 445/TCP connections.
• Try temporarily giving “Read” permissions to “Everyone” on Sharing and NTFS to rule out permissions. Then return to a safe configuration.

If the remote host is a NAS, check its dashboard to make sure the SMB service is active, which SMB versions it allows (minimum and maximum), whether it requires signing/encryption, and which users have permission. On older NAS, enabling SMB2 is often the key..

Related errors and how to interpret them

“Network path not found” is often accompanied by the code 0x80070035 or system error 53. This indicates that the host or path cannot be resolved or reached. However, if you see 0x80070005 (Access Denied), connectivity is already present and the issue is with permissions or credentials. Distinguishing the type of error guides your diagnosis.

0x80004005 (unspecified error) may also appear due to generic SMB failures or if the security negotiation fails. In these cases, enable auditing or review Event Viewer for more detailed messages from the SMB client and server. The more clues the event gives you, the faster you will get to the cause..

If you access legacy devices (old NAS, printers, media boxes)

For devices that don't support SMB2/3, you have several temporary options, prioritizing security:

• Enable “SMB 1.0/CIFS Client” in Windows Features on the client computer. Keep it only as long as necessary.
• On the NAS, upgrade the minimum version to SMB2 if the firmware allows it; disable anonymous guest and use usernames/passwords.
• If the device requires NTLMv1, temporarily set the “LAN Manager Authentication Level” policy to a supported mode.
• Check whether or not the server requires SMB signing; aligning this policy on both sides prevents silent rejections.

If an upgrade isn't possible and you use your device daily, consider replacing the device or looking for a more secure alternative (e.g., a modern microserver or NAS). Security and compatibility will save you headaches in the long run..

Practical tips and useful diagnostics

These shortcuts speed up diagnosis and help you confirm connectivity:

• Explorer: Type \\Shared\IP directly to isolate naming issues.
• PowerShell: Test-NetConnection -ComputerName IP -Port 445 to validate the port.
• CMD: net view \\SERVER to list shares if SMB connectivity is OK.
• PowerShell: Get-SmbSession on the server to see active sessions and errors. It tells you who is connecting and how.
• Remove zombie mappings: net use * /delete /yy remap with explicit credentials.

Another tip: change your network profile to Private if it appears as Public, especially on new Wi-Fi networks. This unlocks discovery and sharing by default. You'll find it in Settings > Network & Internet > Network Properties.

Finally, keeping your network drivers up-to-date prevents incompatibilities with modern SMB features (offloading, RSS, etc.). In Device Manager, check for updates for your Ethernet/Wi-Fi adapter or download them from the manufacturer. An old driver can “break” just what you need.

If you've gotten this far by trying everything from connectivity, discovery, services, firewall, SMB, permissions, and policies, you should usually be able to open the folder that was previously resisting your efforts. The "Network path not found" error sounds serious, but it's usually due to a loose setting or a missing rule; once located, Access by \\Name or \\IP is working again as it should.

Related article:

What is Safe Mode with Networking and how to use it to repair Windows without reinstalling it?

Cristian Garcia

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.