https://bugzilla.samba.org/show_bug.cgi?id=14713 --- Comment #20 from Steve French <sfrench@xxxxxxxxx> --- Comparing with smbclient, there are a few interesting things which differ: a) smbclient sets a default domain name ("SAMBA"). To make this identical for the kernel mount ("mount -t cifs ...") case you could try setting domain= parameter to the same. I doubt this will make a difference because in neither case does the server indicate in its SessionSetup response that authentication ended up as 'guest' so presumably Solaris server thinks the user authenticated properly in both cases (albeit it could be a very unlikely case where "SAMBA/username" is different than "username") b) there are some NegotiateFlags (NTLMSSP flags) set differently during negotiation: 1) smbclient sets "Negotiate Version" 2) cifs.ko sets "Negotiate Seal" and "Negotiate Target Info" and "Negotiate 56" but otherwise the flags look the same. c) smbclient sends both an old Lanman (Lanmanv2) and NTLM (NTLMv2) response in the NTLMSSP_AUTH SessionSetup request, but zeroes the Lanman field, while cifs.ko doesn't send Lanman. This is unlikely to be related -- You are receiving this mail because: You are the QA Contact for the bug.
