By john 
Two computers, same network, same router, and yet neither appears in the other’s Network view. This is one of Windows’ most exasperating behaviours, partly because it often worked yesterday. The explanation involves a design decision most people never learn about, and it makes the whole thing far https://saborcitosrestaurant.com/ less mysterious.
Discovery Is Not Automatic
The first misconception: being on the same network does not mean computers announce themselves. Discovery is a deliberate feature that must be switched on, and Windows switches it off in circumstances you might not expect.
When enabled, your PC broadcasts its presence and listens for others. When disabled, it stays silent, and silence looks identical to being absent. Your PCs may be perfectly able to communicate while neither is willing to say hello.
The Public Network Gate
Here is the mechanism behind most cases. Windows classifies every network as Public or Private, and that choice drives everything.
On a Private network, one you have told Windows to trust, discovery and sharing are permitted. On a Public network, Windows disables both deliberately, on the assumption that you are in a café or airport where announcing your presence to strangers is a bad idea.
That is sensible security. The problem is that networks sometimes get classified as Public without you noticing, particularly after a reconnection or a router change. Suddenly your home network is treated as hostile, and your PCs go quiet. Nothing broke; Windows is protecting you from a threat that is not there.
Why It Worked Yesterday
This explains the maddening intermittency. A network profile can change. An update can reset settings. A new router, or the same router presenting slightly differently, can produce a “new” network that Windows classifies fresh, and defaults are cautious.
So “it used to work” is usually true, and the cause is a classification change rather than a fault.
The Other Common Cause
Beyond profiles, discovery relies on supporting services running. If those services are stopped or disabled, perhaps by an optimisation guide that promised to speed things up, discovery fails silently.
This is a good argument against blindly disabling services: the cost surfaces weeks later as a problem you will never connect to the change you made.
Seeing Is Not Accessing
One clarification worth having. Discovery only makes machines visible. Being able to see a PC does not mean you can open its files; that requires sharing and permissions, which are separate.
Equally, you can often reach a machine directly by typing \\PC-NAME even when it does not appear in the list. Visibility is a convenience, not the connection itself.
The Takeaway
PCs stay invisible because discovery is deliberately disabled on networks Windows considers Public, and profiles change without announcement. Check the network profile first, then whether discovery services are running. And remember that seeing a PC and accessing it are different problems, so a machine you cannot see may still be reachable by name.