NETWizz
Well-Known Member
- Reaction score
- 1,885
You folks ARE going to very likely find some customers (predominantly businesses) who after the November 14th, 1709 Windows 10 can no longer connect to some network shares, and everyone is going to be besides themselves raising a stink about it.
Essentially SMBv1 was used up through XP/2003
Windows Vista/Server 2008 try to negotiate SMBv2
Windows 7/Server 2008 R2 try to negotiate SMBv2.1
Windows 8/Server 2012 and tries to negotiate SMBv3
Windows 8.1/Server 2012 R2 will try and negotiate SMBv3.0.2
Finally:
Windows 10/Server 2016 will try and negotiate SMBv3.1.1
****************
Windows 10 ALL versions will Disable SMBv1/CIFS Server by default.
Windows 10 Education/Enterprise disable SMBv1/CIFS Client & Server by default.
*************************
Hence, a customer with Windows 10 Enterprise in a network with leftover Windows Server 2003 R2 and older will NOT connect.
Solution - Check here... get and paid:
OR. Upgrade their servers... Get paid MORE...
Essentially SMBv1 was used up through XP/2003
Windows Vista/Server 2008 try to negotiate SMBv2
Windows 7/Server 2008 R2 try to negotiate SMBv2.1
Windows 8/Server 2012 and tries to negotiate SMBv3
Windows 8.1/Server 2012 R2 will try and negotiate SMBv3.0.2
Finally:
Windows 10/Server 2016 will try and negotiate SMBv3.1.1
****************
Windows 10 ALL versions will Disable SMBv1/CIFS Server by default.
Windows 10 Education/Enterprise disable SMBv1/CIFS Client & Server by default.
*************************
Hence, a customer with Windows 10 Enterprise in a network with leftover Windows Server 2003 R2 and older will NOT connect.
Solution - Check here... get and paid:
OR. Upgrade their servers... Get paid MORE...