client max protocol defaults to NT1

Christof Schmitt cs at samba.org
Wed Nov 18 20:06:53 UTC 2015


On Wed, Nov 18, 2015 at 02:03:56PM -0600, Scott Lovenberg wrote:
> On Wed, Nov 18, 2015 at 12:41 PM, Jeremy Allison <jra at samba.org> wrote:
> >
> > On Wed, Nov 18, 2015 at 11:37:03AM -0700, Christof Schmitt wrote:
> > > docs-xml/smbdotconf/protocol/clientmaxprotocol.xml documents the current
> > > config:
> > >
> > >     <para>The value <constant>default</constant> refers to the default protocol in each
> > >     part of the code, currently <constant>NT1</constant> in the client tools and
> > >     <constant>SMB3_02</constant> in winbindd.</para>
> > >
> > > Is there a reason why the default of client tools is limited to only
> > > NT1? With newer Windows server having the option of disabling SMB1
> > > support, should we change the default to also negotiate higher protocol
> > > dialects?
> >
> > Yep. Move to SMB3 I think.
> >
> 
> Well, if we go and do that, my OS/2 Warp, and other equally notable
> and supported platforms, won't be able to communicate!  Now I'm going
> to have to run Plan9. ;)

Why would that be the case? Note that this is for the 'client max
protocol' setting, 'client min protocol' still defaults to CORE.

Christof



More information about the samba-technical mailing list