Windows 10: Network discovery not working
SolvedILV -
Hello,
I have created a home local network with several machines running W10 to share resources.
But on one of them, I can't activate network discovery: when I go to "Network and Sharing Center / Advanced sharing settings," I click on "Turn on network discovery," but when I save the changes, the setting automatically reverts to "Turn off network discovery."
I checked the network adapter settings, everything is fine. I even reinstalled Windows to restore the default service configuration. Nothing works. I'm stuck...
Thank you for your help ????
6 réponses
Problem solved!
By following each step of this tutorial: https://www.malekal.com/decouverte-reseau-fonctionne-pas-windows-10-11/
It was the resetting of Winsock and the TCP/IP stack that allowed the "Function Discovery Resource Publication" service to start and consequently I was able to enable network discovery.
Thank you all for your help!
Hello,
start by checking that you're on a private network, not a public network.
And there you go ....
But for heaven's sake, those line spacings are so annoying!!
Network discovery is not useful for exchanges via SMB; you should be able to connect to a network share on the other machine even without it appearing in the discovery by the UNC path:
\\ip address\share name, then the appropriate user account.
Network discovery is net view
https://superuser.com/questions/361277/explain-windows-net-view-command-switches
net view ip address
In fact, discovery encompasses several protocols in parallel, from lldp to nbt (netbios) through ssdp and other dlna, it all depends on what we are looking for and especially what we announce; I’m giving you these keywords if you want to know more.
I click on "enable network discovery" but when I save the changes, the setting automatically reverts to "disable network discovery."
Hi
??? If you have enabled network discovery, it's normal for the option to disable it to be presented to you afterward.
Otherwise, is SMBV1 enabled?

Weird,
if you reinstalled Windows, you normally don't need to reset the tcpip stack, it should be in place.
Yes, I admit my limitations in understanding the problem; perhaps resetting winsock helped. I don't have a grasp on it... but the result is there.