Network discovery stopped working

DaveJ61 said:

Hi, I like a lot of other people are having this issue with network discovery not working. I have a few boxes, some Linux boxes (NAS and webserver), one win7, one win10 laptop and my win10 pc. I can manually type the machine name into the address bar and networking and sharing will be fine until you close file explorer down.
I just got off the phone from microsoft and spoke to some guy there. I explained the problem and then he put me on hold for 2 minutes. When he came back, he said that this functionality was taken away from windows10 and that I would never get it this to work. When I asked why, he got very rude and terse with me to the point of forcing me to cut the phone call short. There was certainly no "Can I help you with anything else today?".

Further to my post above, I read a post from Saddleback further back up this thread and thought I would try what he has suggested. So I changed my pc's workgroup to Home, and then changed one of my linux boxes to the same and all of a sudden, if by magic, it started working. However, it does work for all machines. It strikes me that there is more to this than meets the eye. Also Mr rude from M$ doesn't know everything that he is talking about... he said it would never work... but clearly I have it partly working on three machines.

This long thread may be illuminating :-
Cannot connect to CIFS / SMB / Samba Network Shares Shared Folders in Windows 10 after update 1511/10586

So, this thread might be old, but it was a top result in google, so I thought I'd add what helped me.

It was all services, making sure the below services were enabled and set to Automatic solved my problems:

(these are from another support site)
Computer Browser
DHCP Client
DNS Client
Network Connections
Network Location Awareness
Remote Procedure Call (RPC)
Server
TCP/IP Netbios helper
Workstation

(and these are from here and my own tinkering)
SSDP Discovery
UPnP Device Host

After enabling all those, the "Turn on network discovery" toggle stayed on and all my network devices started showing up!

:D

Hope this can help Someone eventually!

Cheers!

DaveJ61 said:

So I changed my pc's workgroup to Home, and then changed one of my linux boxes to the same and all of a sudden, if by magic, it started working. However, it does work for all machines. It strikes me that there is more to this than meets the eye. .

Worked for me, too! Changed my workgroup name from WORKGROUP to Home, rebooted, and UPNP was working again!

I know this an old post but the network discovery issue seems to be on going with windows 10. Just purchased a brand new laptop and ran into the same problem. I spent a day looking for suggestions and then tried almost all of them. Nothing worked until I changed the workgroup back to how its original workgroup name "WORKGROUP" followed by rooting the laptop, then network discovery started working again!

I then search for explanation on google and came across this discussion group. May be, it is a bad image from the laptop manufacturer, may be it was some corrupted network protocols installed. Thought I'd share my findings to have network discovery working again!

dotcomsurfr said:

I know this an old post but the network discovery issue seems to be on going with windows 10. Just purchased a brand new laptop and ran into the same problem. I spent a day looking for suggestions and then tried almost all of them. Nothing worked until I changed the workgroup back to how its original workgroup name "WORKGROUP" followed by rooting the laptop, then network discovery started working again!

I then search for explanation on google and came across this discussion group. May be, it is a bad image from the laptop manufacturer, may be it was some corrupted network protocols installed. Thought I'd share my findings to have network discovery working again!

a few WU back turned off SMB 1.0 this had us all scrambling for awhile until someone found it. Services Homegroup listener and provider were also turned off and need to be reset to turn on Auto

I am having a hell of a time fixing my network shares which are asking for username/passwords even though I changed no settings at all and it used to work fine without them.

I have SMB 1.0/CIFS enabled in the Features (except Auto Remove) and have the two Homegroup services (even though I don't use Homegroups) set to run on Auto and I am STILL having the same issue....

Running Windows 10 Home on a wired LAN with two Windows-7s and one Windows-8.1. The W-10 computer could see all the others in its File Explorer but the none of them could see it in theirs. This condition appeared suddenly after everything worked for a year.

After studying this thread I tried turning off Network Discovery, rebooting and turning it back on. Now the W-10 machine is visible on the others. Wonderful!

Windows-10 networking is flakey. Does anyone know of a method to list network parameters when an error condition exists? Surely someone with such a list, a description of the error and access to the source code could fix the problem.

--rLsj

Had a customer with this problem, they had a brand new Dell Optiplex 3050, with Windows 10 1709, and Realtek Gbit Family of lan adapters (wired connection). After much troubleshooting (many suggestions listed in the course of this thread), it turned out the PC needed a bios update. Among the updates listed on the dell website for bios version 1.52 (I flashed it with the latest 1.92) was "Update RealtekLOM".

LOM is "lan on motherboard" and the Realtek has flashable firmware.

One step for others having this issue is to check their computer manufacturer's website for "Lom" firmware updates for the particular network adapter - whether integrated or an add-in.

Eric2139 said:

Had a customer with this problem, they had a brand new Dell Optiplex 3050, with Windows 10 1709, and Realtek Gbit Family of lan adapters (wired connection). After much troubleshooting (many suggestions listed in the course of this thread), it turned out the PC needed a bios update. Among the updates listed on the dell website for bios version 1.52 (I flashed it with the latest 1.92) was "Update RealtekLOM".

LOM is "lan on motherboard" and the Realtek has flashable firmware.

One step for others having this issue is to check their computer manufacturer's website for "Lom" firmware updates for the particular network adapter - whether integrated or an add-in.

Wow had the same issue here, with a brand-new OptiPlex 3050, everything installed, but no way getting the networkshares running. Reset the PC, nothing better, clean installation, NOTHING. Now busy with cloning the previous PC, but I will check these things! I already updated the bios and installed the latest drivers, but the Realtek flash not. So will do this now!