First, do the actions described in the video, especially enabling "network discovery".
But your problem is most likley SMB:
There is something called SMB (Server Message Block) which was deprecated (taken away) in Windows 10/11 because of Microsoft’s “security” paranoia. Microsoft didn’t see it fit to replace this with something else that works, but SMB can be re-installed via “Turn Windows features on and off”. Find any and all SMBs in the list and check it to install and reboot. Hopefully that will fix your problem. This worked for me.
If SMB didn’t fix the problem, then make sure the following services are set to Automatic and turned on (running). You can always experiment and turn off any of the services that did not fix your problem, because some of these can be more of a security risk than SMB (by allowing unwanted connections).
Function Discovery Provider Host fdPHost
Function Discovery Resource Publication FDResPub
Network Connected Devices Auto-Setup
Network Connection Broker
SSDP Discover SSDPSRV
UPnP Device Hos upnphost
Peer Networking Grouping p2psvc
Peer Networking Identity Manager p2pimsvc
Peer Name Resolution Protocol PNRPsvc
Next, the problem may be a firewall issue. The following command (entered in command prompt as admin) may help:
netsh advfirewall firewall set rule group=”Network Discovery” new enable=Yes
Next, there is this weird concept called “master browser computer” (not a browser like Firefox). This is related to SMB and has to do with one computer on the network that has the list of other computers on the network. I don’t have a good understand of this, and it sounds like a kludge which is prone to going bad (getting corrupted). To clear up any conflicts, turn off all your computers and routers (and modem). Then boot up one at a time: modem first, routers next, then one computer at a time.
Finally (or maybe you want to do this first): The list of connected devices in Windows Explorer Network can get corrupted and keep showing devices that are no longer there. To clear up the network device list cache, run this command on the command prompt (with upper case R):
nbtstat –R
If nothing works, then you know where the problem lies - 25H2.
