Network Discovery not working on Windows 11 — other computers don’t appear in File Explorer’s Network section, or your machine doesn’t appear to other computers — is a specific Windows networking feature that requires several services and firewall rules to work together. When any one of them is wrong, the entire feature stops working. We go deeper on the whole subject in our Complete Guide to Fixing Windows, Browser, and Software Errors.
This guide assumes you’re on a trusted home or work network where network discovery should be enabled. If you’re on a public network (coffee shop, hotel), network discovery is intentionally disabled by Windows for security.
The fastest fix: change network profile to Private
Network Discovery only works on Private network profiles. If your network is set to “Public,” Windows disables discovery for security reasons and won’t show you other computers — or let other computers find you.
Settings → Network and internet → your connection → “Network profile type” → select Private.
After changing, File Explorer → Network should start populating within a minute. If your network was set to Public and changing it to Private solves the problem, you’re done.
Enable Network Discovery in File Explorer
Even with the correct network profile, Network Discovery might be turned off. Open File Explorer → click “Network” in the left sidebar. If a yellow banner appears saying “Network discovery is turned off,” click it → select “Turn on network discovery and file sharing.”
This is a per-profile setting. Make sure to confirm it for your current network type (Private).
Fix the required services
Network Discovery depends on five Windows services all running simultaneously. If any one is stopped or disabled, discovery fails. Win+R → type services.msc → find and set all of these to Running with Startup type Automatic:
- Function Discovery Resource Publication
- SSDP Discovery
- UPnP Device Host
- DNS Client
- Function Discovery Provider Host
For any service that isn’t running: right-click → Properties → Startup type: Automatic → Apply → Start. Some of these services are set to “Manual” by default in Windows 11, which means they only start when something explicitly requests them — and if the requester (the Network Discovery process) itself needs them to already be running, they never get started. Setting them to Automatic ensures they’re available from boot.
Windows Firewall rules for network discovery
Windows Firewall includes built-in rules specifically for Network Discovery. If these are turned off (which can happen after a firewall reset or a third-party security suite installation), network discovery fails even with all services running.
- Win+R →
control firewall.cpl→ Allow an app or feature through Windows Firewall - Find “File and Printer Sharing” in the list → check the Private checkbox (and Domain/Work if applicable)
- Also find “Network Discovery” if it appears separately → enable for Private
Alternatively, use the more complete approach via Advanced Firewall settings:
- Win+R →
wf.msc(Windows Defender Firewall with Advanced Security) - Inbound Rules → right-click → Filter by Group → “Network Discovery”
- Enable all the Network Discovery rules that are currently disabled for the Private profile
Enable network discovery via Command Prompt
For a fast way to enable all the necessary settings at once, run these in an administrator Command Prompt:
netsh advfirewall firewall set rule group="Network Discovery" new enable=Yes
netsh advfirewall firewall set rule group="File and Printer Sharing" new enable=Yes
This enables all the relevant firewall rules in one step, equivalent to checking all the boxes in the firewall GUI.
Computers appear sometimes but not reliably
If network discovery is intermittent — computers appear in the Network folder for a few minutes then disappear — the Function Discovery Resource Publication service is likely stopping after startup. Check whether it’s set to “Automatic” (not “Automatic (Delayed Start)”) and whether it’s actually staying running:
- Services.msc → Function Discovery Resource Publication → Properties → Startup type: Automatic → OK
- Wait 10 minutes → open Services again → check whether it’s still Running
- If it stopped: look at the Recovery tab → set First failure to “Restart the Service”
Computers visible in Network but can’t connect
If you can see computers in the Network folder but get “access denied” when trying to connect: this is a separate file sharing permissions issue, not a Network Discovery problem. Network Discovery (making devices visible) and File Sharing (accessing their files) are configured separately.
For access denied issues: on the remote computer, check that the shared folder has permissions set for the connecting user account, or enable “Password protected sharing” on both machines and use the same account credentials.
Our guide on network connectivity issues covers the underlying Windows network configuration that affects both network discovery and general connectivity. For corporate environments where Windows network discovery interacts with Active Directory, our network profile guide covers the domain versus workgroup distinction. Microsoft’s network discovery documentation covers the WSD (Web Services for Devices) and LLMNR (Link-Local Multicast Name Resolution) protocols that network discovery uses, and how to troubleshoot when specific devices don’t appear despite discovery being enabled.
Mixed Windows versions on the network
Network Discovery uses different protocols depending on Windows version:
- Windows 10/11: uses WSD (Web Services for Devices) for discovery and DNS-SD
- Windows 7/8: relied more heavily on NetBIOS and browser service
- NAS devices and older network-attached hardware: often use SMBv1 or NetBIOS for network visibility
If older Windows machines or NAS devices don’t appear in Windows 11’s Network folder: this is because Windows 11 disabled SMBv1 (for security) which older devices depended on for network announcement. Solutions:
- Access NAS devices directly by typing their UNC path (\NAS-name or \IP-address) in File Explorer’s address bar — they can be accessed even if they don’t appear via discovery
- Check whether the NAS has a firmware update that adds WSD/DNS-SD support for Windows 10/11 compatibility
- Enable SMBv1 in Windows 11 only as a last resort and only on isolated networks — it has known security vulnerabilities: Control Panel → Programs → Turn Windows features on or off → “SMB 1.0/CIFS File Sharing Support”
VPN affecting network discovery
A connected VPN changes how Windows routes local network traffic. Many VPN configurations route all traffic through the VPN tunnel, which prevents network discovery packets from reaching local network devices — the VPN captures the broadcast traffic before it reaches the local LAN.
Test: disconnect the VPN and check whether network discovery works. If it does: the VPN is intercepting local discovery traffic. Check the VPN client for a “Split tunneling” or “Local network access” option that allows local LAN traffic to bypass the VPN while work traffic goes through it. Most enterprise VPN solutions support this but may need IT to configure it.
Network Discovery on Domain networks
On Active Directory domain-joined machines: network discovery and file sharing settings are often controlled by Group Policy rather than local Windows settings. If the network profile shows “Domain” and you can’t change discovery settings, the IT department controls this via GPO.
Check: netsh advfirewall show currentprofile — this shows which profile (Domain, Private, Public) is active. On domain networks, the Domain profile is active, and discovery rules for the Domain profile must be enabled, not just the Private profile rules. IT can configure Group Policy to enable network discovery for the Domain profile.
Checking discovery with ping and name resolution
If computers don’t appear in the Network folder but you know their names, test whether they’re reachable before assuming network discovery is broken:
ping computername
ping \computername
If ping succeeds: the computer is on the network and reachable; network discovery just isn’t showing it visually. You can access it directly via \computername in File Explorer. If ping fails: there’s a deeper network connectivity issue beyond discovery configuration.
Also try:
net view /all
This shows all computers visible on the network using NetBIOS, separate from Windows’ visual Network folder. If computers appear in net view output but not in the Network folder, it’s a WSD/GUI issue rather than a connectivity problem.
Third-party firewall blocking discovery
When a third-party security suite (Norton, Kaspersky, ESET, Bitdefender) is installed, it often replaces Windows Firewall’s rules with its own. This can block the network discovery traffic even when Windows Firewall allows it. Check your security suite for:
- “Network protection” or “Firewall” section → look for local network or home network settings
- Some security products have a “trust this network” prompt for new networks — if you clicked “Public” when setting up the network, the security software treats it as untrusted and blocks discovery
- Temporarily disabling the third-party firewall (not the whole security suite) and testing confirms whether it’s the blocker
PowerShell commands for troubleshooting network discovery
Administrator PowerShell provides more detailed information than the GUI for diagnosing discovery issues:
# Check current discovery and sharing settings
Get-NetFirewallProfile -Name Private | Select-Object DisabledInterfaceAliases
# View all Network Discovery firewall rules and their status
Get-NetFirewallRule -DisplayGroup "Network Discovery" | Select-Object DisplayName, Enabled, Direction, Profile
# Start all discovery-related services at once
Get-Service -Name fdphost, FDResPub, SSDPSRV, upnphost, dnscache | Start-Service
The PowerShell output is more diagnostic than the GUI — it shows exactly which firewall rules are enabled for which profiles, making it easy to identify which specific rule is missing.
When network discovery works but is very slow to populate
The Network folder can take 30-90 seconds to show all network devices even when discovery is working correctly. This is normal — devices announce themselves using WSD broadcasts, and Windows waits to collect all announcements before displaying the list.
If you consistently see devices appear then disappear, or the list changes frequently: the Function Discovery Resource Publication service is starting and stopping. Ensure it’s set to Automatic and staying running. If Windows keeps stopping it for resource management reasons, this service’s priority can be set higher using the sc command, though this is rarely necessary on modern hardware.
| Issue | Cause | Fix |
| Network section completely empty | Network profile is Public, or discovery disabled | Change to Private profile; enable discovery via yellow banner |
| Discovery enabled but computers missing | Services not running or firewall rules off | Enable five services; check firewall rules |
| Computers appear, then disappear | Function Discovery Resource Publication stopping | Set to Automatic startup with restart-on-failure recovery |
| See computers but can’t connect | File sharing permissions, not discovery | Configure share permissions on target computer |
| NAS/older devices invisible | SMBv1 dependency on older hardware | Access via direct path; check NAS firmware updates |
Network Discovery in Windows 11 is genuinely more complicated than it needs to be — it requires multiple services, specific firewall rules, and the correct network profile all working together. The single most common fix (changing from Public to Private network profile) fixes the majority of cases in five seconds. The services and firewall rules approach covers most of the rest. The more complex scenarios (VPN, SMBv1 compatibility, domain GPO) are real but affect a smaller portion of users.
If network discovery has never worked on this machine despite following all the steps above, it’s worth checking whether the network adapter supports multicast traffic — some older USB Ethernet adapters and certain Wi-Fi drivers don’t properly handle multicast packets that WSD relies on. Testing with a different network adapter (USB Ethernet adapter or different Wi-Fi) quickly confirms or rules out this cause.
Homegroup vs Workgroup vs Domain in Windows 11
Homegroup was removed in Windows 10 version 1803, so Windows 11 machines use Workgroup-based file sharing instead. All Windows 11 machines should be in the same workgroup (default: WORKGROUP) for network discovery to show them in the same Network folder view.
Check your workgroup name: right-click This PC → Properties → look for “Workgroup” → it should say WORKGROUP (or match whatever your other machines use). To change: System → Advanced system settings → Computer Name tab → Change → Workgroup → change to match other machines → restart.
Machines in different workgroups can still share files and be accessed directly, but they may not appear automatically in each other’s Network folder via discovery. Direct UNC path access (\computername or \IP-address) works regardless of workgroup membership.
DNS-SD and mDNS for modern network discovery
Windows 11 uses DNS-SD (DNS Service Discovery) and mDNS (Multicast DNS, port 5353 UDP) for discovering devices that support it — this is the same protocol used by Apple’s Bonjour. Devices like smart TVs, printers, and NAS units that advertise via mDNS will appear in Windows 11’s Network folder even without SMBv1.
If specific devices don’t appear via mDNS discovery: check whether your router’s mDNS forwarding (also called “mDNS proxy” or “Bonjour proxy”) is enabled if you have multiple subnets. mDNS packets don’t cross subnet boundaries by default, so devices on different IP ranges won’t discover each other without router-level mDNS forwarding configured.
For most home users, the combination of Private network profile + all five discovery services running + Windows Firewall rules enabled resolves network discovery. For IT administrators managing Windows 11 in enterprise environments, the Group Policy approach for configuring network discovery at scale (Computer Configuration → Windows Settings → Security Settings → Network List Manager Policies) is more sustainable than per-machine configuration — it ensures discovery settings persist across OS updates and user profile changes. You might also run into Windows 11 Scanner Not Working.
