12-17-2018, 03:52 PM
Additional SMB info that I always post:
Don't forget "min protocol = SMB2" in your Samba config (and restart smbd), because otherwise it allows for SMB1, and Windows could accidentally select SMB1 instead of SMB2 unless you ALSO configured your Windows client specifically NOT to use SMB1.
On the Windows side: https://support.microsoft.com/en-us/help...indows-and
It's best to specify on both ends that you want SMB2 so there's no way it can mess up.
[ If you've already mitigated Windows for 'wannacry', then you should have SMB1 off and SMB2 on already. ]
( In the future, we'll want SMB3, but Samba's SMB3 support is limited. You could try 3 if you are able, but I personally haven't tested Samba's SMB3 since I can't exceed SMB2 performance. )
Don't forget "min protocol = SMB2" in your Samba config (and restart smbd), because otherwise it allows for SMB1, and Windows could accidentally select SMB1 instead of SMB2 unless you ALSO configured your Windows client specifically NOT to use SMB1.
On the Windows side: https://support.microsoft.com/en-us/help...indows-and
It's best to specify on both ends that you want SMB2 so there's no way it can mess up.
[ If you've already mitigated Windows for 'wannacry', then you should have SMB1 off and SMB2 on already. ]
( In the future, we'll want SMB3, but Samba's SMB3 support is limited. You could try 3 if you are able, but I personally haven't tested Samba's SMB3 since I can't exceed SMB2 performance. )
