If Windows 11 on Ethernet can’t find shared computers, start with the cable link, the local subnet, and whether the other PC is actually sharing a folder. If those are fine, the usual fix is to set the Ethernet network to Private, turn on Network discovery and File and printer sharing, and make sure the discovery services are running. If a share opens by IP but not by name, the problem is browsing or name resolution, not a dead Ethernet link.
What this problem usually means
This symptom doesn’t always point to the same cause. Sometimes Network is empty. Sometimes a PC appears, but its shared folders won’t open. Sometimes only one device is missing while the rest still show up.
If Network is empty, Windows may not be browsing that LAN. If a known share opens by IP but not by name, the network path works and the problem is usually discovery or name resolution. If nothing opens at all, the issue may be on the other PC, the NAS, the router, the switch, or a firewall or security setting on either side.
In practice, split it into two questions: can the PC reach the other device at all, and can Windows browse it by name? That keeps you from changing settings that don’t match the failure.
Before you start
- Use a Windows 11 PC with Ethernet connected to the same local network as the shared computer or NAS.
- Have the other PC’s name, a known share name, or its IP address ready.
- If the PC is managed by work or school policy, some sharing settings may be locked and need IT to change them.
- Don’t reset the network yet.
Start with the least risky checks first: physical link, same subnet, and whether the remote machine is really sharing something. If the other device is not sharing a folder, Windows can still show it as a device on the LAN and yet give you nothing useful in File Explorer.
Check the cable, link, and whether the other PC is actually sharing
- Check the Ethernet cable and link lights on the PC, switch, or router. If there is no link light, fix the cable or port first.
- Confirm both devices are on the same local network segment. They usually need the same subnet for simple home or small office file sharing, even if internet access works on both sides.
- On the other PC or NAS, confirm that at least one folder is shared and that your user account is allowed to open it. A device can be online and still not show useful shares if sharing was never set up, was removed, or is limited to different credentials.
- Compare IP addresses if you can. If one machine is on
192.168.1.xand the other is on a different prefix, fix the network path before you change Windows sharing settings.
If these checks fail, the problem is likely upstream of Windows 11: a bad cable, wrong port, separate VLAN, separate subnet, or a device that isn’t actually exposing a share.
Turn on the Windows 11 discovery and sharing settings
Windows 11 should use a Private network profile for trusted home or office LAN sharing. On a private network, Windows is more willing to discover other PCs and publish itself to them.
- Open the Ethernet network settings and check the profile.
Settings > Network & internet > Ethernet- Set the network profile to Private if it is not already.
- Open the advanced sharing settings and turn on these options for Private networks:
- Network discovery
- File and printer sharing
- Leave the profile alone if the PC is managed by work or school and those settings are controlled by policy. In that case, the local toggle may not be enough.
If your only goal is to make shared computers appear in Network, these are the first Windows settings that need to be correct. If they are already on and nothing changes, move on to services and firewall checks instead of toggling them repeatedly.
Make sure the discovery and SMB services are running
Even with the right sharing switches, Windows still relies on a few services to publish and browse computers on the LAN. If one is stopped, Network can stay empty or update very slowly.
- Open Services.
- Check that these services are running or set to start automatically:
- Function Discovery Provider Host
- Function Discovery Resource Publication
- SSDP Discovery
- UPnP Device Host
- If one is stopped, start it and wait a moment to see whether the shared computers appear.
- If a service won’t start, stop here and look for a policy issue, a security product blocking the service, or a deeper Windows problem.
SMB is the file-sharing path Windows uses for shared folders. If SMB access is blocked by a firewall rule, security software, or a disabled sharing component, the PC may still reach the internet but fail to browse or open LAN shares.
Check firewall and security settings that block shared computers
The most common block after profile and services is the firewall. Make sure the active firewall profile allows file and printer sharing on the Private network. Some third-party security suites also block local discovery even when Windows settings look right.
If you use security software, check whether it has its own network protection or local network isolation setting. I’ve seen cases where Windows Discovery is on, the services are running, and the PC still refuses to show neighbors because the security product is filtering LAN traffic.
If this is a work or school PC, group policy may also block discovery or SMB browsing. When that’s the case, you can spend a long time changing local settings and still not see a difference.
Do not weaken the whole firewall just to prove the point. If you need a test, use a temporary, documented exception for file and printer sharing on the Private profile instead of disabling protection broadly.
Test by name and by IP, then confirm the fix worked
This is the quickest way to tell browsing trouble from reachability trouble.
- Try the other PC by name in File Explorer.
- If that fails, try the same share by IP address, such as
\\192.168.1.20\Sharename.
- If the IP path opens but the name does not, the network is reachable and the issue is discovery or name resolution, not the cable or the share itself.
- If neither name nor IP opens, the problem is probably on the other PC, NAS, router, switch, or firewall rather than this Windows 11 machine.
- If the share opens by IP but not by name, keep using the direct path for now while you keep working on discovery.
A common case is that a Windows 11 PC can see some devices, like a DVR, but not the PC or NAS you actually need. That usually means the LAN is partly working, not that Ethernet itself is broken.
To confirm the fix, check both of these:
- The shared computer appears in Network.
- A direct share path opens without a credentials loop or access error.
If the share opens by IP and the device appears in Network, the problem is resolved. If only one of those works, keep that distinction in mind; it tells you whether you’re still fixing browsing or whether you’ve already fixed access.
When the issue is on the other device or the network gear
If Windows 11 is set to Private, the discovery services are running, the firewall allows sharing, and a direct IP share still fails, the problem is probably elsewhere.
Look at the other PC first if it used to share correctly and suddenly stopped. A changed password, removed share, disabled sharing, or a firewall update can break access while Windows 11 stays unchanged. Microsoft Q&A examples also show cases where one PC could see a Windows 11 machine but not access its drives, or where mapping by IP worked after name-based access did not.
Then check the router, switch, or NAS. Separate VLANs, guest isolation, or a NAS sharing rule can stop browsing even when internet access is fine.
If you are still stuck after those checks, Microsoft says network reset is a last step. It can help after an upgrade or when you can reach the internet but not shared network drives, but it also resets the network adapters and their settings.
Verify the fix
Open File Explorer and check Network again. The shared computer should appear there if discovery is working.
Then open the share directly by name and by IP. A clean test is when both work without extra prompts, loops, or access denied errors. If only the IP path works, the share is reachable but browsing is still not fixed. If neither works, the issue is still outside this PC or in the sharing setup on the target device.
If you made a firewall or security change, put it back only after you’ve confirmed which rule or setting actually fixed the problem.
Conclusion
If the shared PC still won’t appear, stop changing random settings and test the other computer, NAS, or network gear next.
Frequently Asked Questions
Why can I open a shared folder by IP but not see the PC in Network?
That usually means the network path works, but browsing or name resolution does not. The cable and switch are probably not the problem; focus on discovery, services, or the device that publishes its name on the LAN.
Should I use Network reset right away?
No. Microsoft says to use it as a last step because it removes and reinstalls network adapters and resets their settings. It can help with shared network drive problems, but it changes more than a file-sharing fix usually needs.
Sources
- Fix Ethernet connection problems in Windows | Microsoft Support (support.microsoft.com)
- Struggling to get new Windows 11 PC to share files over private ethernet network - Microsoft Q&A (learn.microsoft.com)
- windows 11 computer not seeing other network computers - Microsoft Q&A (learn.microsoft.com)