Heya folks, Ned here again. As part of a small series on esoteric SMB settings, today I’m going to explain how to control SMB client dialects in Windows 10 and Windows Server 2019.
Background ...
Updated Nov 08, 2022
Version 11.0
Blog Post
Hi Zenhawk219,
Yes, you can do SMB mandating for the SMB client with the purpose of achieving SMB 2.0 as the negotiated SMB version. Set the minimum and maximum to 2.0.2 (as 2.000 isn't supported here, although typically this doesn't matter, as 2.000 is only available in Windows Vista RTM):
- Minimum:
- Hive: HKEY_LOCAL_MACHINE
- Key: SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters
- Named value: MinSMB2Dialect
- Value type: REG_DWORD
- Default: named value doesn't exist (= existing with the lowest value supported by the Windows instance in casu)
- Remark: explicit minimum value = 0x00000202 => this is SMB 2.0.2, so you can't set it lower than SMB 2.0.2!
- Maximum:
- Hive: HKEY_LOCAL_MACHINE
- Key: SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters
- Named value: MaxSMB2Dialect
- Value type: REG_DWORD
- Default: named value doesn't exist (= existing with the highest value supported by the Windows instance in casu)
Be aware that the SMB server should at least support 2.0.2, otherwise this won't work of course.
Grtz,
Pedro