Network is not showing up in the File Explorer Network Tab (Still accessible through pathways)

Question

The company network is all connected via ethernet. Typically when I've run into this issue in the past it has had more to do with my personal computer. However, everyone in the office is currently unable to see the network when navigating "Network" in File Explorer. As mentioned in the title, we can still access files and utilize the server through pathways and shortcuts, but when trying to use STAAD, a structural analysis software, it is unable to access the network directly itself. I have updated my personal computer fully and ensured that all Windows network settings are correct on my end, but the issue still remains both on my computer and every other computer in the office. Any ideas on what I can do to solve this issue?

Answer 1

Hi Aidan Gallagher,

The reason direct file paths work while the Network tab remains empty is that your core SMB file sharing over TCP port 445 is healthy, but the multicast broadcast packets required for network enumeration are failing to propagate across your office subnet.

This happened simultaneously across the entire office, the most likely culprit is that the Network Location Awareness service momentarily dropped its connection to your domain controller or gateway, defaulting the network profile on your machines from Private to Public. When Windows classifies a network as Public, the Windows Defender Firewall automatically engages stealth mode, silently dropping all inbound and outbound WS-Discovery multicast traffic on UDP port 3702. You must open the Windows Settings, navigate to Network & Internet, and verify that your active Ethernet connection profile is strictly set to Private.

Once the network profile is confirmed as Private, you must ensure the background services responsible for this discovery are executing. You need to open the Services console by executing services.msc and locate both the Function Discovery Provider Host, internally known as fdPHost, and the Function Discovery Resource Publication, known as FDResPub. You must configure both services to Automatic Delayed Start to ensure they load properly after the network stack initializes upon boot. Starting these services forces your server and workstations to broadcast their presence, fully repopulating the Network tab for your STAAD software.

Hope this answer has brought you some useful information. If it did, please hit “accept answer”. Should you have any questions, feel free to leave a comment.

VPHAN