[Samba] Issues configuring Samba

Rowland Penny rpenny at samba.org
Wed Jun 8 09:42:57 UTC 2022

On Wed, 2022-06-08 at 09:26 +0000, Andy Pont via samba wrote:
> Louis wrote...
> > Whats missing here is..
> > > >  I can see SMB transactions on the network using Wireshark
> > SMB?  1 2 or 3.
> When I initially found the issue after the upgrade to Samba there was
> no 
> version definition in the configuration.

If there is no 'client min protocol' and/or 'server min protocol' set
in smb.conf, then you will be using the default setting. Before Samba
4.11.0 , the default was 'CORE', from 4.11.0 this was raised to

>   I have since run tests with 
> "min protocol = SMB2” and "min protocol = SMB3” to force the
> version.  

'min protocol' is a synonym for 'server min protocol'

> Whilst doing so, I have also configured the protocol_vers_map option
> in 
> the macOS /etc/nsmb.conf to match.  From the Wireshark trace, it is 
> showing as having negotiated SMB 3.11.

You shouldn't have to set any 'min protocol', negotiation should find
the best one to use, it should start at SMBv3 and work down from that.

> The same third party tool that is based on Eclipse (v4.18 possibly
> also 
> known as 2020-12) works without issue on a Windows machine when 
> accessing the same share.
> -Andy.

We are going to need wireshark traces from both the Windows connecting
and the other (MacOS ?) machine that connects.


More information about the samba mailing list