Windows 10: Windows 10 1511 Network Browsing Issue

Confirmed. ShareEnum on a Windows 7 VM on the same network shows all available servers and shares.

Bart

 

But still the big question is why isn't everyone's network affected?

 

Yes, AND why doesn't Microsoft have an update to solve this?

Bart

 

That's another good question! After all, we have given them a lot of good info on where to look.

The MS social network thread on this said that the info had been passed to the appropriate MS people.

Strangely, I don't seem to have a master browser, now. That won't help.

 

I have done some more testing and, like others have said, it definitely seems to be a SMB version issue.

If I turn off SMB 2&3 in the Lanman client I can then see all shared devices, including my NAS WD Mybooklive that was invisible since 10586. I can access the NAS shares also but I can't access the other device shares. I get the dreaded 80070035 error and that means that my Lanman client is asking the Lanman server to display its shares but because the SMB version is different, there is no communication and that results in the client issuing the 80070035 path not found error.

I have tried various combinations but can't get it working as pre 10586.

As far as I can see, all my five win 10 10586 comps have got messed up SMB versions hence a failure to communicate the shares.

I have left my main comps in the mode where I can see the NAS and hope that MS will fix this soon.

 

Today, I had two updates installed, KB3120677 and KB3118754. No solution for the browsing problem.

Funny thing is that the new Update app is lying about the Update history. It says that KB3120677 was installed on November 25, but that only happened today. Good old Control Panel Update tells me the correct date.
Well, may be the update arrived on November 25 and I rebooted this morning. I believe that the reboot date is more relevant.

We continue waiting!

Bart

 

Yep, we wait. Wonder how hard it is to see how to fix it considering it was fine pre 586?

 

Advanced sharing is enabled for domain computers and the appropriate services are running. PW sharing not present in domain.

 

I have a WIndows 7 Professional x64 VM, which I occasionally use for testing.

It was able to see all the systems on the network. But today I installed a lot of updates (I guess about 6 months of those) and surprise: it can no longer see the other systems.

It seems to me that MS was so proud of an "enhancement" in Windows 10, that they back ported it to Windows 7.

I am not going to find out which update causes the problem.

Bart

 

Looks like there is issue here. Since it involves network browsing, finding a fix should be high priority for Microsoft. This type of problem is great way to bother IT managers of big organization trying out windows 10. We can hope that network objects will magically appear on network browsing. Sooner would be better than later.

 

In Windows 10 v1511, I noticed that it uses WSD protocol to identify a computer with Windows 7 SP1 on my LAN (peer to peer).

I can not understand because the other computers with Windows 7 SP1 does not are displayed by Windows 10.

All computers with Windows 7 SP1 are displayed among themselves (using the WDS protocol) and they can also display the computer with Windows 10.

So, why Windows 10 sees only one using WDS protocol?

All computers have the same workgroup.

Thanks

Bye

 

*SOLUTION*
I discovered that my server on the network had defaulted to smb2. I changed the server to smb1, and yikes everything appeared under Network in Win 10 Pro 64. It seems any networked computer not on smb1 will cause all network browse to fail.

 

Still not fixed after last updates.

 

OK, I don't know much about SMB versions (if anything). But I could not find anything in the registry of both my Windows 2012 R2 server and the Windows 10 1511 client which could indicate what SMB version is being used.

Could someone please elaborate on this? Which registry keys are involved here?

Thanks in advance!

Bart

 

From: https://support.microsoft.com/en-us/kb/2696547

To obtain the current state of the SMB server protocol configuration, run the following cmdlet: Code: Get-SmbServerConfiguration | Select EnableSMB1Protocol, EnableSMB2Protocol[/quote] Run in PowerShell as Administrator

For the Win10 client run this is PowerShell Command Prompt:
Code: sc qc lanmanworkstation[/quote] Unless you've messed with it one of the dependencies should read as "MRxSmb20"
Edit: My apologies: In the Win10 client that should be run in Command Prompt not PowerShell.