Metanis
Well-Known Member
- Reaction score
- 941
- Location
- Medford, WI, USA
Problem: Some of my networked computers could not browse or see other networked computers in Network Neighborhood.
Solution: Reset all devices to use SMB 1.0. ( SMB stands for Server Message Block )
I have a Microsoft domain setup here at my home shop.
Main Server = Microsoft Server 2008R2
Aux Server = Microsoft Server 2012
Workstations = Variety of Linux Mint, WinXP, Win7, Win8, & Win10 machines.
The newest Win10 ver 1511 machines could only "see" Win7 machines in Network Neighborhood. These 1511 machines could not see the servers or other 1511 machines. However I could manually map a drive or explore to shares by typing in the explicit \\server\sharename without any problems. This problem is new to the 1511 version of Win10.
Tried a number of things over the last month but nothing worked until I reset all boxes on the network to use the lowest common denominator SMB v1.0. Now everything is fast and everything "sees" every other device on the network. Of course this defeats some of the speed and security features of the newer SMB versions but if you can't reliably enumerate your network what good are they?
Here are some links that can explain this much better than I can:
http://technocreativo.com/2015/08/27/fix-for-connecting-to-os-x-smb-shares-from-windows-10/
https://support.microsoft.com/en-us/kb/2696547
https://redmondmag.com/articles/2014/05/16/network-performance-problems.aspx
http://woshub.com/smb-1-0-support-in-windows-server-2012-r2/
Solution: Reset all devices to use SMB 1.0. ( SMB stands for Server Message Block )
I have a Microsoft domain setup here at my home shop.
Main Server = Microsoft Server 2008R2
Aux Server = Microsoft Server 2012
Workstations = Variety of Linux Mint, WinXP, Win7, Win8, & Win10 machines.
The newest Win10 ver 1511 machines could only "see" Win7 machines in Network Neighborhood. These 1511 machines could not see the servers or other 1511 machines. However I could manually map a drive or explore to shares by typing in the explicit \\server\sharename without any problems. This problem is new to the 1511 version of Win10.
Tried a number of things over the last month but nothing worked until I reset all boxes on the network to use the lowest common denominator SMB v1.0. Now everything is fast and everything "sees" every other device on the network. Of course this defeats some of the speed and security features of the newer SMB versions but if you can't reliably enumerate your network what good are they?
Here are some links that can explain this much better than I can:
http://technocreativo.com/2015/08/27/fix-for-connecting-to-os-x-smb-shares-from-windows-10/
https://support.microsoft.com/en-us/kb/2696547
https://redmondmag.com/articles/2014/05/16/network-performance-problems.aspx
http://woshub.com/smb-1-0-support-in-windows-server-2012-r2/
