Inconsistent results from Windows Networking

Snookred 36 Reputation points
2026-11-07T20:00:01.8366667+00:00

I operate several different Windows computers and rely heavily on Windows Networking. In order to describe this problem I have 4 computers running on my own private network. Three of the four are connected to the network via Ethernet RJ45 Adapters. One is connected via WiFi. There is also a Network Attached Storage (NAS) device connected to the network.

The device names are as follows:

  • Uranus Windows 11 Laptop
  • Neptune Windows 10 Desktop
  • Mars Windows 10 Desktop
  • Venus Windows 7 Laptop
  • MyCloud NAS

Using File Explorer the only computer that displays the expected view is Neptune. My intention is that all the computers are setup the same way. As far as I can tell that is true but given that this problem exists I must consider the possibility that some mistake/s exist. I made 3 screenshots that demonstrate the problem. A screenshot from Neptune follows:

NeptuneView

Compare this to Mars which follows:MarsView

Compare them to Uranus which follows:

UranusView

It does appear as though Mars & Uranus have the same deficiency but the one other computer that they detect are different.

It is also a little curious the the NAS named MyCloud only appears on Neptune when selecting Network is the File Explorer. However, the Y: drive that is assigned to it functions correctly on all the computers.

Hopefully, this is a somewhat simple problem known to those with the right kind of expertise. I've now spent an awful lot of time trying to find an answer.

Windows for business | Windows Client for IT Pros | Networking | Network connectivity and file sharing
0 comments No comments

1 answer

Sort by: Newest
  1. AI answer

    2026-11-07T20:00:29.0866667+00:00

    The screenshots fit a network discovery and sharing configuration problem, not a mapped-drive problem. A mapped drive such as Y: can keep working even when devices do not appear consistently under File Explorer > Network.

    Use this checklist on all four Windows PCs:

    1. Make sure all PCs are on the same network If the devices connect through a router, confirm they are all connected through that same router.
    2. Set the network profile to Private Microsoft’s file-sharing guidance calls this out specifically for Wi-Fi networks. Since Uranus is on Wi‑Fi, verify it is using a Private network profile.
    3. Turn on Network discovery and File and printer sharing In Windows 10:
      • Start > Settings > Network & internet > Sharing options
      • Under Private, turn on Network discovery and File and printer sharing
      • Under All Networks, turn off Password protected sharing
      In Windows 11, if File Explorer > Network shows the banner “Network discovery is turned off…”, select it and then select Turn on network discovery and file sharing.
    4. Make sharing services start automatically On the Windows 10 systems:
      • Press Windows key + R
      • Run services.msc
      • For the sharing-related services listed in Microsoft’s guidance, open Properties, make sure they are Started, and set Startup type to Automatic
    5. Update Windows on all machines Microsoft recommends this as a first troubleshooting step for file-sharing issues.
    6. Check what is actually shared On each PC, open File Explorer and type \\localhost in the address bar. This shows what that computer is exposing locally. It helps confirm whether the issue is discovery, or whether the folders are not actually shared.

    A few points that match the behavior shown:

    • Seeing different device lists on different PCs is consistent with network discovery not being fully enabled or not working consistently on every machine.
    • The NAS appearing only on Neptune under Network but still working as mapped drive Y: is also consistent with discovery inconsistency. Discovery and direct access are not the same thing.
    • If the network has mixed Windows versions, Microsoft notes that putting devices in the same workgroup helps devices running different Windows versions detect and access one another.

    One important limitation in the provided Microsoft content: Windows Explorer may not enumerate all computers in some environments. Microsoft documents a case where not all domain computers are listed in Explorer. That means the Network view should not be treated as a perfect inventory by itself.

    Given the mix of Windows 11, Windows 10, and Windows 7, the most likely first fix path is:

    • verify same network
    • set every connection to Private
    • enable Network discovery and File and printer sharing on every PC
    • turn off Password protected sharing if that matches the intended setup
    • ensure the required sharing services are running automatically
    • confirm all devices are in the same workgroup

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.