This usually means Windows can’t resolve the shared computer’s name, can’t discover it on the local network, or can reach it only by direct SMB path instead of showing it in File Explorer. The quickest safe fix is to separate DNS, network discovery, and SMB, then turn on the right sharing settings only on a private network. If the share opens by IP but not by name, you’re usually looking at name resolution rather than a broken share.
What to check on the sharing PC and when to escalate
If the client PC looks fine, check the computer that is sharing the folder or printer.
- Confirm the shared folder or printer still exists.
- Check the share permissions and the folder permissions for the account you’re using.
- Make sure Windows Firewall on the sharing PC allows file sharing and network discovery on the correct network type.
- Confirm the sharing PC is awake, on the same LAN, and not isolated from other devices.
If one machine can open the share by IP but another cannot, that usually points to local permissions, firewall profile, or a naming problem rather than the share disappearing entirely. If nothing works even by IP, the share may be down, blocked by firewall, or on the wrong network.
Router settings matter too. Guest Wi‑Fi, AP isolation, client isolation, and VLAN separation can block peer-to-peer traffic between Windows PCs. When those features are enabled, Windows discovery often fails even though internet access still works.
To confirm the fix, test in both directions. In File Explorer, open Network and see whether the shared computer appears again. Then try the UNC path directly, such as \\computername\share, and compare it with the IP path if needed. If the name path opens and the Network list repopulates, you fixed the right layer. If the share still fails only from some machines, escalate to firewall or admin policy instead of changing more Windows services.
Frequently Asked Questions
If I can open the share by IP, is DNS really the problem?
Usually the name lookup step is the problem, or at least part of it. If `\\IP-address\share` works but `\\computername\share` does not, the SMB share itself is often fine and Windows is failing to turn the name into an address.
Why does the PC not show up in Network even though the share exists?
That usually points to discovery, not the share itself. Windows Network view depends on discovery services, the private network profile, and firewall rules, so a share can still exist even when the browser list is empty.
What should I check first on Windows 11?
Check the active network profile, then turn on Network Discovery and File and printer sharing for the Private profile only. After that, confirm the DNS Client and discovery-related services are running before you change DNS servers or router settings.