One computer sees another on the network while the reverse fails because Windows Firewall or Network Discovery settings are asymmetrically configured. This common issue arises when one machine allows inbound connections but the other blocks them, preventing bidirectional communication despite basic connectivity existing.
Understanding Asymmetric Visibility
When Computer A can ping or browse to Computer B, but Computer B cannot see Computer A, the problem is rarely about physical cabling or router configuration. Instead, it points to a security policy difference between the two endpoints. Windows 10 uses Network Profiles to determine how strictly to enforce firewall rules and discovery protocols. If one PC is set to
Public and the other to
Private, their behaviors will diverge significantly. The Public profile disables most discovery features to protect the device from unknown networks, while the Private profile enables file sharing and network visibility. This mismatch creates the exact scenario where one side is visible and the other remains hidden.
Verifying Network Profile Settings
The first step in resolving this asymmetry is to ensure both computers are using the same network profile type. You must check the active connection status on both machines to confirm they are recognized as part of a trusted local network rather than an untrusted public zone.
To check and change the network profile:
- Open the Settings app by pressing
Win + I.
- Navigate to Network & Internet and select Wi-Fi or Ethernet depending on your connection type.
- Click on the name of the connected network (e.g., "HomeNetwork").
- Under Network profile type, select Private. This action tells Windows that you trust devices on this network.
Repeat this process on the computer that is currently invisible. Once both machines are set to Private, Windows automatically adjusts firewall rules to allow local discovery traffic. This single change often resolves the visibility issue immediately without requiring deeper technical intervention.
Enabling Network Discovery and File Sharing
Even with the correct profile, the underlying services responsible for broadcasting presence may be disabled. Windows relies on specific discovery protocols to announce its existence to other peers. If these are turned off, the computer effectively goes dark to its neighbors.
Navigate to the classic Control Panel interface to manage these settings:
- Press
Win + R, type control, and press Enter.
- Go to Network and Sharing Center and click Change advanced sharing settings on the left pane.
- Expand the Private section.
- Ensure Turn on network discoveryTurn on automatic setup of network connected devices.
- Similarly, expand the All Networks section and verify that File and printer sharing is enabled.
After making these changes, click
Save changes. It is crucial to apply these settings on both machines. If only one side has discovery enabled, it will continue to listen for broadcasts but not respond to them, maintaining the asymmetric state.
Checking Firewall Rules for Inbound Traffic
If visibility persists after adjusting profiles and discovery settings, the Windows Defender Firewall may be blocking specific inbound ports required for network identification. While the general rule of thumb is that Private profiles allow discovery, custom rules or third-party antivirus software can override these defaults.
You should verify that the following core services are allowed through the firewall:
- Function Discovery Provider Host: Allows the system to discover resources on the network.
- SSDP Discovery: Enables detection of UPnP devices.
- Web Client: Supports mapping network drives and browsing shared folders.
To inspect these rules, open
Windows Defender Firewall with Advanced Security from the Start menu. Under
Inbound Rules, look for rules related to "Network Discovery" and ensure they are Enabled for the Private profile. If you have installed third-party security suites, they may have created their own firewall layers. Temporarily disabling such software can help isolate whether it is the cause of the blockage. For more complex network layer issues, consider reviewing
DNS and NSLOOKUP: Troubleshooting Network Connectivity Issues to rule out resolution problems.
Restarting Critical Services
Sometimes the configuration is correct, but the background services handling network announcements have stalled or crashed. Restarting these services forces Windows to re-register the computer's presence on the local subnet.
Open Command Prompt as Administrator and execute the following commands in order:
net stop fdrespub
net start fdrespub
net stop upnphost
net start upnphost
net stop SSDPSRV
net start SSDPSRV
These commands restart the Function Discovery Resource Publication, UPnP Device Host, and SSDP Discovery services. After running these, wait a few minutes and check if the computer appears in the network list on the other machine. This step clears any cached stale data that might be preventing immediate visibility.
Frequently Asked Questions
Why does my computer appear offline even though I am connected to Wi-Fi?
This usually happens because the network is classified as Public, which hides the device for security reasons. Switching the network profile to Private restores visibility by allowing local discovery protocols to function correctly.
Can third-party antivirus software cause this visibility issue?
Yes, many antivirus programs include their own firewalls that may block inbound discovery packets regardless of Windows settings. You should check your antivirus dashboard for network protection settings and ensure local network access is permitted.
What should I do if both computers are on Private but still cannot see each other?
Verify that both machines are on the same subnet and that no VLAN isolation is configured on your router. Additionally, ensure that the guest or anonymous access policies in the registry are not restricting local peer-to-peer communication.
Does IPv6 affect network discovery visibility in Windows 10?
IPv6 can influence how addresses are selected and routed, potentially causing confusion in mixed environments. If you suspect address selection issues, refer to guides on
Prefer Similar IPv6 Source Address for Outbound Connections in Windows 10/11 to optimize protocol behavior.
How long does it take for a computer to become visible after changing settings?
Visibility typically updates within 5 to 10 minutes as the network discovery service broadcasts the new status. You can force an immediate update by restarting the Network Discovery services or rebooting the machine entirely.