Windows 10: Home network discovery not working after latest W10 Update

double posted some how is there a delete some where?

 

So after 1 1/2 days lately and since win 10 release and countless clean installs I finally got the network to finally half work but at least I can get files/drives that I need connected to where I need them more. Primary pc 1 starts a homegroup but when pc 3 boots pc 1 homegroup disappears and wants to join again but it errors out of re joining but pc1 can read pc 3 and pc3 can read pc1, now pc 2 can read pc 1 but not 3 and 3 can't read 2, 3 is off homegroup is back on 1 but 1 can't read 2. Pc 4 and 5 I'm afraid to even consider at this point.

Oddly win7 homegroup/network was perfect for 5yrs then on to win 10 networking and bam one big disaster.

 

You can even access another Win10 machine that way if you open the appropriate port on it's firewall with a:
Code: \\win10-host-name.local[/quote] I also don't think it's a SMB version issue. When I connect to a Linux box for example it's connecting via SMB3.

The problem appears to be network discovery as it is displayed under "Network" in explorer. All of this appears to point to an issue with the "Function Discovery" process.

I work mostly with small networks ( less than 10 hosts ) so accessing by name is really not an issue. I also don't use Homegroups since I have no idea what that is and as most of the other hosts on my network are either Linux or OSX machines a Homegroup is irrelevant.[/quote] I agree, you can access the devices with \\name but that is not the issue with me and many others at the moment. Even with the dreaded 80070035 Path not found scenario it was always possible to ping devices and access shares with \\name. But prior to 10586 we used to be able to see all networked devices and then access their shares directly from file explorer.

The Function services do not display the networked devices available as I have disabled both those services, re-booted, and my shared devices still appear in file explorer as usual.

The use of SMB with Linux is probably variable depending on the Linux device. With my Linux based WD MyBookLive NAS, it does not show with 10586 but if I disable SMB2&3, thus forcing SMB1, it does show and all shares are displayed. So, in my system, SMB version does matter.

Going on from device discovery we come to seeing the shares on each device. This relies on the Lanman client talking to the Lanman server via SMB. In my current case I can see the NAS shares but not the shares of other computers. These give the 80070035, Path not found error. This means that the Lanman client asks the Lanman server for the shares and if there is no answer from the server, the client puts up the Path not found error. This non communication is caused by the use of wrong SMB versions as I proved several months ago.

We also get the situation where we can see the shares for a while, then we can't. This adds another confusion to the mix. I am sure this is tied up with which comp is the master browser. If you are working on the comp that is the master browser, you can see shares but if the master browser moves to another comp, you can't. This all points to a break in communication as no communication is required if you are on the master browser. At least this sounds logical to me!

So, currently, I have SMB2&3 client disabled allowing access to my NAS shares but this stops simple access to my other comp shares but NAS visibility is more important.

At the end of the day, we have to face the fact that before 10586 there was none of this nonsense and after 10586 we have these problems. I am also convinced by my current testing, and by my earlier skirmish with SMB version mismatches, that this is the cause of the changes we see.

 

Win 10 started off fine for me when I upgraded months ago with 2 Laptops that were running Win 7 and 1 with Win 8.1. There were just a couple small things like the program Speccy being deleted for incompatibility which I figured out how to get working compatibly. Then it seemed like all was fine until this Threshold 2 upgrade.

So anyways I had and still seem to have a situation like yours upcoast. I have my Network and Homegroup working fine as long as I boot Laptop1 first which was the creator of the homegroup. It was all working without needing to do that after tweaking and fixing settings but there was another update a few days ago that messed it all up again.

So there doesn't seem to be a solid fix yet that stays good as each update modifies settings. Do any software engineers from Microsoft ever read these forum posts???

 

I've tried three different "fixes" and the network is still a mess. Can see different units on various units but no unit sees all units. My wifes documents directory/files seem to have been made read only and she can no longer use them from other computers.

Have been wondering if those having troubles can still use the cloud and whether the problem is related to MS big push to it

ALSO, this morning, opened exel and before I could use it I was forced to agree to a new license agreement. ??? office 2013 that has been installed for months.

 

One of the recent updates and I'm not sure which one also reset licenses on my PC's. I've had to re-apply licenses on about 5 different software programs so far. Not sure exactly what caused that yet.

 

No issues with office 2016 here, or any other software. Fully patched 10586.14 10 Pro clean install.

 

@linw

I agree there is a problem with host discovery in Win10. At the moment my Win10 can't even see itself under Network.

The reason for my post on smb versions is that the implication is actual host name resolution if fixed by disabling smb2/3 and forcing smb1. If I run Get-SmbConnection in powershell after connecting to a samba server it tells me I'm connecting via smb3. If it couldn't resolve the host name I wouldn't be able to connect.

As for the WD NAS device it looks perhaps like a variation of this issue:
http://answers.microsoft.com/en-us/i...a-b85ae133c887

Accessing NAS's from Linux has always been a struggle since these devices all seem to use archaic versions of samba or something similar. In Linux you are forced to do a manual CIFS mount and pass it a deprecated security mode for NT lanman ( sec=ntlm ) and not an SMB version ( which is another option ) in order to make the connection since the default in cifs or using a linux file manager is more in line with OSX and Win7+.

I'm not sure if Windows can make a specific mount of a remote share using a different set of options than the global ones. Maybe it's something powershell can do.

EDIT: Don't remember if I said this or not but Microsoft is aware of this issue of host discovery - Well, one Microsoft employee is anyway:

Cannot connect to CIFS / SMB / Samba Network Shares Shared Folders in Windows 10 after update 1511/10586

 

Thanks for that info.

Yes, I did see that MS had taken it up.

I am patiently waiting for the fix. Well, actually, not that patiently!

Cheers.

 

Ok so I reset the Advanced Sharing settings for Discovery that had reset themselves to OFF earlier today. Just came back online and checked and they reset themselves to OFF again. WTF.

 

Public or Private network type? The default for Public is off and for Private it's on. Still shouldn't change it once you set what you want though? Unless you connected to a different network like a coffee shop free WIFI or something.

 

Private network. All the Sharing setting reset themselves to OFF this morning. Bizarre.

 

I can access 2/3 laptops by using their Microsoft oneDrive login name (email) and password (Microsoft, why on earth you would want that setting I don't know but the programmer must have been smoking weed during that time). But then I just created the same type of login on my wife's laptop to map a drive to her and it will not accept it. This is a ridiculous major bug that is costing me, and a lot of other people, time and money.

 

I just dumped the Homegroup from all 3 Laptops and now just using Workgroup. This has been a ridiculous waste of time having to keep fixing it.

I also did the CMD as an ADMIN > netsh winsock reset
REBOOT

To fix the Missing Winsock error. That seems to have worked for fixing the recent web connectivity error messages.

 

YES that is another bug I had where your login credentials apparenetly get deleted to access other PC's on the Network. And the bug also prevents the use of the original correct stored username/password and instead you have to set all your PC's to the same MS ACCOUNT to get the network passwords working again.