Reg:SMB1.0 disabled in 2012
vigneshdhanraj.g at gmail.com
Fri May 29 04:07:59 MDT 2015
Thank you so much for the update. Andrew
My Debian PC joins the domain hosted by Windows2012ServerR2 as a member
server. “smb.conf” is from the Debian PC running samba 4.0.25.
The problem I am facing is that the RPC client on the Debian PC is not
sending 0x72 with dialects up till “SMB 2.002” and “SMB 2.???”
Even with 'client max protocol = smb2' RPC client still sends 0x72 with
dialects up till “NT LM 0.12” (SMB 2.002 and SMB 2.??? are missing)
Results were same even with the following directives.
"max protocol= SMB2"
"server max protocol= SMB2"
On Thu, May 28, 2015 at 11:44 PM, Andrew Bartlett <abartlet at samba.org>
> On Thu, 2015-05-28 at 14:51 +0530, VigneshDhanraj G wrote:
> > Please find below smb.conf
> > security= ADS
> Thanks. It wasn't clear if you were an AD client or server. You have a
> domain member server in an AD domain running Windows 2012 on the DC.
> > > I found windows 2012 R2 server not supporting SMB1.0 Then
> > why it is
> > > necessary to be enabled. I am using samba 4.0.25.
> You will need to either upgrade to Samba 4.2 or set 'client max protocol
> = smb2'. I recommend the upgrade, as our SMB2 RPC client and the
> handling require in winbindd is more mature in more recent versions.
> In all versions SMB2 is disabled in the client by default, but in 4.2 we
> make an exception for winbindd, which runs up to SMB2 by default.
> Andrew Bartlett
> Andrew Bartlett http://samba.org/~abartlet/
> Authentication Developer, Samba Team http://samba.org
> Samba Developer, Catalyst IT
More information about the samba-technical