Network Resource Unavailable Error on Windows 10? Fix It

The “Network resource unavailable” error on Windows 10 usually appears when you try to access a shared folder or printer on another computer, and Windows cannot reach that resource due to network discovery, permission, or credential issues. The fix typically involves enabling network discovery, checking your network profile, or mapping the drive with explicit credentials. Below is a structured guide to resolve it, along with the background you need to understand why it happens.

What Triggers the Error

This error is most common when you attempt to open a network path like \\COMPUTERNAME\SharedFolder or \\192.168.1.10\Public from File Explorer, and Windows reports “Network resource unavailable” or “Windows cannot access the specified device, path, or file.” It can also occur when mapping a network drive or connecting to a network printer. The underlying causes are usually:

• Network discovery is turned off, so Windows cannot see the target computer.
• The network profile is set to “Public,” which blocks file sharing by default.
• The target computer’s firewall is blocking SMB (port 445) or NetBIOS (port 139).
• The credentials you are using are incorrect or lack permission on the target.
• The target computer is turned off, asleep, or has a different subnet.
• The SMB 1.0 protocol is required but disabled (common for older devices).

Understanding which of these applies to your situation is the first step, because the fix differs for each.

Step-by-Step Fixes

Work through these in order. Most cases are resolved by the first two steps.

1. Turn on network discovery and file sharing. Go to Control Panel > Network and Sharing Center > Advanced sharing settings. Under your current profile (Private or Guest/Public), select “Turn on network discovery” and “Turn on file and printer sharing.” Save changes.
2. Check your network profile. Open Settings > Network & Internet > Status, click “Properties” on your active connection, and ensure the network profile is set to “Private,” not “Public.” Public networks block file sharing by default.
3. Try accessing the resource by IP address. Instead of the computer name, use the IP address: \\192.168.1.20\share. If that works, the issue is name resolution (DNS or NetBIOS).
4. Map the drive with explicit credentials. In File Explorer, right-click “This PC” and select “Map network drive.” Choose a drive letter, enter the path, and check “Connect using different credentials.” Enter the username and password for the target machine (e.g., COMPUTERNAME\Username).
5. Enable SMB 1.0 if the target is old. Some legacy devices (Windows XP, older NAS) require SMB 1.0. Go to Control Panel > Programs > Turn Windows features on or off, check “SMB 1.0/CIFS File Sharing Support,” and restart. Use this only if necessary, as SMB 1.0 is insecure.
6. Check the target computer’s firewall. On the computer hosting the shared folder, allow “File and Printer Sharing” through Windows Defender Firewall (or your third-party firewall). Look for inbound rules for TCP 445 and UDP 137-138.
7. Reset the network stack. Open Command Prompt as administrator and run: netsh winsock reset, netsh int ip reset, then restart. This clears corrupted network settings.

Why Network Discovery Matters

Windows 10 uses network discovery to find other computers and devices on the local network. When it’s off, File Explorer’s Network section shows nothing, and direct UNC paths may fail with “Network resource unavailable.” Network discovery relies on the Function Discovery Resource Publication service and the SSDP Discovery service. If those services are stopped, discovery fails even if the setting is on. You can check them by opening Services (type services.msc in Run), finding “Function Discovery Resource Publication” and “SSDP Discovery,” and ensuring they are set to “Automatic” and running.

Common Misconception: It’s a Password Issue

Many users assume the error means they typed the wrong password. While that’s possible, the error message specifically says “network resource unavailable,” which usually indicates the resource isn’t reachable at all, not that credentials were rejected. If credentials were wrong, you’d typically see “Access is denied” or “The user name or password is incorrect.” So if you’re getting “unavailable,” focus on connectivity and discovery, not passwords.

When to Use IP vs. Computer Name

Using the computer name requires name resolution. Windows uses DNS first, then NetBIOS over TCP/IP. If the target computer’s name is not in DNS (common on home networks), NetBIOS must work. If NetBIOS is disabled on either machine, the name won’t resolve, and you’ll get the error. Using the IP address bypasses name resolution entirely. To find the target’s IP, run ipconfig on that computer and look at the IPv4 address. If you can ping it and access the share via IP, the problem is name resolution, and you might want to add an entry to the hosts file (C:\Windows\System32\drivers\etc\hosts) or fix NetBIOS settings.

Advanced Troubleshooting: Check SMB Signing and Guest Access

Windows 10 also enforces SMB signing by default, which can cause issues with older devices that don’t support it. You can temporarily disable SMB signing on the client to test: open Local Security Policy (secpol.msc), go to Security Settings > Local Policies > Security Options, and set “Microsoft network server: Digitally sign communications (always)” to Disabled. Also, some Windows 10 versions disable insecure guest logons for SMB. If the target is a network-attached storage (NAS) that uses guest access, you may need to enable insecure guest logons via Group Policy: Computer Configuration > Administrative Templates > Network > Lanman Workstation, set “Enable insecure guest logons” to Enabled.

Frequently Asked Questions

Why does the error appear when I try to map a network drive?
Mapping a drive uses the same UNC path as opening it directly. If the path is unreachable due to discovery, firewall, or name resolution, mapping fails with the same error. Try the steps above, especially enabling discovery and using the IP address.

Can I fix this without changing my network profile to Private?
Yes, but it’s harder. You can keep the network as Public and manually enable network discovery and file sharing for that profile in Advanced sharing settings. However, Windows may still block some connections. Changing to Private is the simplest and recommended for trusted networks.

Does this error affect network printers?
Yes, the same error can occur when connecting to a shared printer. The printer must be shared on the host, and the host’s firewall must allow file and printer sharing. Also ensure the printer is powered on and connected to the same network.

What if the target computer is a Windows 11 machine?
Windows 11 has similar settings. The steps for network discovery and profile are nearly identical, so the same fixes apply. Just note that Windows 11 also disables SMB 1.0 by default, so older devices may need that feature enabled.

Is it safe to enable SMB 1.0?
No, SMB 1.0 is outdated and has known vulnerabilities. Only enable it temporarily to connect to legacy devices, and disable it once you’ve transferred files or updated the device. Prefer using SMB 2.0 or 3.0 if the device supports it.

Related

• How to Reset a Mac Password in macOS Sierra
• How to Set Up and Use Notifications on iPhone & iPad
• Windows 11 Freeze on Startup? Fixes That Work