smbclient --max-protocol=NT1: why it requres setting MIN protocol too?

Jeremy Allison jra at
Tue Oct 25 16:45:32 UTC 2022

On Tue, Oct 25, 2022 at 06:45:55PM +0300, Michael Tokarev via samba-technical wrote:
>When trying to use current smbclient to connect to, say, a windowsXP machine
>(which implements only NT1 protocol), smbclient has to be told to use lower
>protocol version than it's default - this is intended.
>But the thing is that it doesn't work:
>  $ smbclient --max-protocol=NT1 //testhost/share
>  Unable to initialize messaging context
>  protocol negotiation failed: NT_STATUS_INVALID_PARAMETER_MIX
>Using -m/--max-protocol=NT1 *also* requires setting another option:
>  $ smbclient --max-protocol=NT1 --option='client min protocol = CORE' //testhost/share
>This way it actually works.
>Can't smbclient either warn about this situation, or better yet,
>lower its min protocol automatically if it is greater than
>the requested max protocol?

I think that's a great idea for usability. Can you log
a bug so we can track it ?



More information about the samba-technical mailing list