[Samba] Samba client doesn't work SMB2 with MAC 0S 10.9.5

[Ralph Böhme]

On Tue, Sep 30, 2014 at 10:06:01AM -0700, Jeremy Allison wrote:
> On Tue, Sep 30, 2014 at 06:55:42PM +0200, Ralph Böhme wrote:
> > On Tue, Sep 30, 2014 at 09:31:08AM -0700, Jeremy Allison wrote:
> > > On Tue, Sep 30, 2014 at 06:27:15PM +0200, Ralph Böhme wrote:
> > > > On Tue, Sep 30, 2014 at 08:55:46AM -0700, Jeremy Allison wrote:
> > > > > On Tue, Sep 30, 2014 at 10:16:46AM +0000, Tompkins, Michael wrote:
> > > > > > Jeremy, we have implemented your updates for to support SMB2 in both 3.6.5 and 4.0.7.
> > > > > > That is working fine for both, with the exception of MAC OS 10.9..5 servers.
> > > > > 
> > > > > Ah ok - that's information we didn't originally have :-).
> > > > > 
> > > > > So this is actually a custom version of 3.6 then.
> > > > > 
> > > > > > There is a lot of discussion on the web about the problems, and most people talk
> > > > > > about a workaround to dummy down to SMB1(NT1), which really is not a desirable
> > > > > > option, especially for FIPS support. Was there a specific fix to so the smbclient
> > > > > > and the MAC OS 10.9.5 server work together?  That's the information we are looking for.
> > > > > 
> > > > > Easiest thing to do is make your modified 3.6.x source available
> > > > > (there are others who might want to see that patchset) and then
> > > > > upload a wireshark trace of the problem. Remember you're asking
> > > > > for help with a modified (unsupported) smbclient version.
> > > > > 
> > > > > Do the 10.9..5 servers work with the 4.1 client ? If so, then
> > > > > there's an error in your back-port. If not, then we have a
> > > > > generic bug we need to fix.
> > > > > 
> > > > > Knowing which is the case would be very valuable :-).
> > > > 
> > > > got mixed results here: on my system Samba 4.1.6 [1] and master fail,
> > > > while I've been told by Björn Jacke that it works on his system with
> > > > 4.1.6. Needs more testing.
> > > 
> > > Can you get me a packet trace ?
> > 
> > attached.
> > 
> > $ ./bin/smbclient4 -U 'ralph%SECRET' //10.10.10.30/indexed -mSMB2
> > Connection to \\10.10.10.30\indexed failed - NT_STATUS_REVISION_MISMATCH
> > 
> > $ ./bin/smbclient4 -U 'ralph%SECRET' //10.10.10.30/indexed 
> > smb: \> exit
> > $ 
> 
> You're using the wrong smbclient (curse source3 and source4 !).

*ouch*

> bin/smbclient4 is no longer maintained (we really should remove
> it).
> 
> Can you just use:
> 
> ./bin/smbclient -U 'ralph%SECRET' //10.10.10.30/indexed -mSMB2
> 
> instead ?

*stumped*

I was both using smbclient and smbclient4 in testing this afternoon,
and both failed reproducibly. Looks like smbclient works now with SMB1
and with SMB2 too:

$ ./bin/smbclient -U ralph%SECRET //10.10.10.30/indexed -mSMB2
Domain=[MACMINI] OS=[] Server=[]
smb: \> exit
$ 

This is again with git/master.

-Ralph

-- 
SerNet GmbH, Bahnhofsallee 1b, 37081 Göttingen
phone: +49-551-370000-0, fax: +49-551-370000-9
AG Göttingen, HRB 2816, GF: Dr. Johannes Loxen
http://www.sernet.de,mailto:kontakt@sernet.de