If shared computers don’t appear in Windows Network or File Explorer on a wired office switch, the usual cause is not the switch “failing to find” them. It is usually a reachability problem, a Windows discovery or sharing setting, or a network split such as a VLAN or isolation rule. The safest fix order is to check whether the PCs answer by IP first, then check Windows discovery and file sharing, and only then touch switch or cabling settings. If `\\PCNAME\Share` works but the computer never shows in the browse list, you’re usually looking at discovery or name resolution, not a dead share.
Symptom
The usual symptom is straightforward: one or more shared PCs are missing from Network or File Explorer. They are still plugged into the office switch, and they may look fine at the desk.
Sometimes you can reach the PC by IP address but not by name. Sometimes you cannot reach it at all.
The pattern matters. If ping works but browsing does not, that usually points to name discovery, browse-list behavior, or Windows sharing settings. If ping fails too, treat it as a basic connectivity or network-segmentation problem first, not a Windows folder-sharing problem.
Before you start
Use a PC that is on the same office switch or at least the same local wired LAN as the missing share. If you can, test from a second PC on the same switch port group. That helps separate a PC problem from a network problem.
Start with checks that do not change settings:
- Make sure the target PC is on and its network link light is on.
- Make sure you know the target PC’s IP address.
- Be ready to undo any change you make on the PC or switch port.
What this problem usually means
This usually does not mean the switch itself is broken. A switch forwards traffic; it does not build the Windows browse list.
When shared computers do not appear, I usually see one of three cases: the PC is offline, the PC is online but not discoverable, or the network is split so the PCs are not actually in the same local broadcast domain.
A quick decision tree helps:
- If the PC does not answer by IP, look at power, cable, port, VLAN, or subnet placement.
- If the PC answers by IP but not by name, look at Windows discovery and name resolution.
- If some PCs appear and others do not, compare their Windows sharing settings and their network placement.
That is the fastest way to avoid chasing the wrong layer.
First check the easy stuff before touching switch settings
Start with the physical link and a basic reachability test. I’d do this before changing anything in Windows or on the switch. It tells you whether you’re dealing with a transport problem or a discovery problem.
- Check the PC’s power and link lights. - The network port on the PC and the switch port should show link. - If there is no link light, reseat the cable at both ends. - If you can, try a known-good cable and a different switch port.
Test basic reachability from another PC on the same office network.
Command Prompt ping 192.168.1.25Replace the address with the PC’s actual IP address. If the ping works, the device is alive on the path you tested. If it fails, do not assume it is a Windows sharing problem yet.
- Stop here if the PC still has no link or no ping response after a cable swap. That points to a transport problem, a bad port, a wrong patch lead, a disabled switch port, or a network split. There is no point changing discovery settings on a machine that is not actually reachable.
How to tell whether the PCs are unreachable or only undiscoverable
On Windows, compare the IP address, subnet mask, and default gateway on both PCs. If the numbers do not match the same network pattern, the machines may be on different subnets even if they sit on the same switch.
Run ipconfig or open the network details on both PCs and compare three things:
- IP address
- Subnet mask
- Default gateway
If one PC is 192.168.10.x and another is 192.168.20.x, they are likely on different subnets. In a managed office network, that often means different VLANs or a routing setup that does not allow easy peer-to-peer sharing. A ping may still work if routing is allowed, but Windows browse discovery can still fail across subnets.
If the addresses are in different subnets and you expected them to be together, check the switch port profile, VLAN assignment, and DHCP scope before changing anything on the PCs. That is usually the cleaner fix.
If the PCs are on the same subnet and ping works, but they still do not appear in Network, that is a discovery or sharing issue, not a cabling issue.
Fix Windows discovery and sharing settings
If the PCs are on the same subnet and you can ping by IP but still cannot see shared computers, Windows discovery is the first place I would look. A machine can be link-up, online, and still hidden from Network because discovery or file sharing is turned off.
- Confirm the network profile is set to Private, not Public. On a Public network, Windows often turns down discovery and sharing. Change it to Private only if this is a trusted office network.
- Turn on Network Discovery and File and Printer Sharing. In Windows sharing settings, make sure both are enabled for private networks. If the PC is meant to host shares, it should also allow SMB access through the firewall.
- Check the firewall rules for file sharing. A firewall can block SMB traffic even when the adapter is working. If ping works but
\\PCNAME\Sharedoes not, this is a common place to look.
Test the direct share path instead of the browse list.
Expected path \\192.168.1.25\SharedFolderIf the direct UNC path works but the PC still does not show in Network, the issue is discovery, not the share itself.
If the direct path fails too, the problem is no longer just discovery. At that point I would check permissions, the share name, firewall rules, and whether SMB is blocked on the target PC.
In mixed office networks, older name-discovery methods such as NetBIOS or LLMNR may be off, filtered, or inconsistent. That can make browsing feel broken even when the actual share is fine by direct path.
Look for VLANs, isolation, or direct-share problems
If Windows settings look right, the next suspect is the network itself. A managed switch can look perfectly healthy while VLANs quietly split the office into separate islands. Port isolation, guest networks, or wireless AP isolation can do the same thing.
A few checks help separate those cases:
- If the PCs are on different VLANs, they may need routing and firewall rules before they can see each other.
- If one port is isolated, traffic to other client ports may be blocked even though the port has link.
- If a PC is on Wi-Fi through a guest or isolated SSID, it may not see wired shares on the office LAN.
Test by IP first, then by direct share path. If ping works but browsing does not, and \\IP\share works, the transport path is fine and the problem is name discovery or browse-list behavior. If ping works but \\IP\share fails, you are dealing with SMB access, firewall rules, or permissions instead of simple discovery.
If you suspect the switch, confirm the port’s VLAN and any isolation feature against the current switch configuration or controller settings. The exact menu names vary by vendor, so check the current official documentation for that model before changing anything.
To confirm the fix from another PC on the same switch, repeat the same two tests after the change: ping the IP, then open the direct UNC path. If both work, try the machine name in File Explorer. If the name now resolves and the share opens, you have fixed both reachability and discovery. If the name still does not appear in Network but the direct path works, that is usually a browse-list problem, not a network outage.
Verify the fix
Use a second PC on the same switch segment and check three things in order:
- Ping the target PC by IP.
- Open the share by direct UNC path, such as
\\192.168.1.25\SharedFolder. - Try the computer name in File Explorer or Network.
If ping works and the direct path opens, the share is reachable. If the computer name also works or the PC appears in Network after a refresh, the discovery path is fixed too. If ping works but the name still does not appear, the remaining issue is usually browse discovery or name resolution, not file access.
Conclusion
If you still cannot find the shared computers after these checks, the next step is to compare the switch port configuration, VLAN assignment, and Windows firewall rules on the specific PC that is missing. If you want, I can help you turn this into a short checklist for your office network.
Frequently Asked Questions
Why can I ping a PC but not see it in Network?
Because ping only proves the device answers ICMP, not that Windows discovery or SMB browsing is working. The PC may be hidden by its network profile, firewall, or name-discovery settings, or it may sit on another subnet or VLAN that still routes basic traffic.
What if the share opens by IP but not by computer name?
That usually means name resolution or browse discovery is the problem, not the share itself. Check Windows Network Discovery, firewall rules for file sharing, and whether the machine name is the one other PCs should use.