Comment 10 for bug 1697817

Adding more info, next future SAMBA version 4.7 will increase the SMB "client max protocol" to SMB3_11 to be able to connect to servers with SMB1 disabled, "client min protocol" is still SMB1.

https://download.samba.org/pub/samba/rc/samba-4.7.0rc1.WHATSNEW.txt
https://wiki.samba.org/index.php/Release_Planning_for_Samba_4.7
https://wiki.samba.org/index.php/Samba_4.7_Features_added/changed

######
The default for "client max protocol" has changed to "SMB3_11",
which means that smbclient (and related commands) will work against
servers without SMB1 support.

It's possible to use the '-m/--max-protocol' option to overwrite
the "client max protocol" option temporary.

Note that the '-e/--encrypt' option also works with most SMB3 servers
(e.g. Windows >= 2012 and Samba >= 4.0.0), so the SMB1 unix extensions
are not required for encryption.

The change to SMB3_11 as default also means smbclient no longer
negotiates SMB1 unix extensions by default, when talking to a Samba server with
"unix extensions = yes". As a result some commands are not available, e.g.
posix_encrypt, posix_open, posix_mkdir, posix_rmdir, posix_unlink, posix_whoami,
getfacl and symlink. Using "-mNT1" reenabled them, if the server supports SMB1.

Note the default ("CORE") for "client min protocol" hasn't changed,
so it's still possible to connect to SMB1-only servers by default.
######