New
#21
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.
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:Run in PowerShell as AdministratorCode:Get-SmbServerConfiguration | Select EnableSMB1Protocol, EnableSMB2Protocol
For the Win10 client run this isPowerShellCommand Prompt:
Unless you've messed with it one of the dependencies should read as "MRxSmb20"Code:sc qc lanmanworkstation
Edit: My apologies: In the Win10 client that should be run in Command Prompt not PowerShell.
I have a Synology server. In the server Control Panel under File Services/Advanced Setting/Max Protocol for Windows File Service/Dropdown box SMB1,2, or 3. It defaulted to SMB2. I chose SMB1 and the Network reappeared in the Win 10 desk top. Hope this helps you.
OK, thanks. Now I have seen that when I disable SMB2 on my server, the network neighborhood on my Windows 10 system reappears. So it seems that SMB2 on Windows 10 1511 is broken.
Regards,
Bart