[Bug 14713] SMBv3 negotiation fails with a Solaris server

[samba-bugs@samba.org]

https://bugzilla.samba.org/show_bug.cgi?id=14713

--- Comment #9 from Richard Flint <richard.flint@gmail.com> ---
1) As long as you are running a reasonably recent kernel or distro update (5.0
or later kernel should be fine, and current RHEL/CentOS/Oracle client ie
RHEL/CentOS/Oracle 8.4 or 8.3 should be fine as well since Redhat backports
many fixes to their older kernel) can you try not specifying "vers=" at all and
see what it negotiates with the server?  (should be 3.1.1 - you can see in
/proc/fs/cifs/DebugData)

If I fail to specify the vers= option. Mounting fails completely. Dmesg says
our usual:

[162979.482987] CIFS: VFS: \\nonsuch failed to connect to IPC (rc=-11)
[162979.484449] CIFS: VFS: session 0000000083b7840c has no tcon available for a
dfs referral request
[162979.485899] CIFS: VFS: cifs_mount failed w/return code = -2

and the Solaris server says:

May 24 23:09:46 nonsuch smbcmn: [ID 997540 kern.warning] WARNING:
../../common/fs/smbsrv/smb2_dispatch.c:smb2_dispatch_message:134:Decryption
failure (71)!
May 25 19:44:21 nonsuch smbcmn: [ID 997540 kern.warning] WARNING:
../../common/fs/smbsrv/smb2_dispatch.c:smb2_dispatch_message:134:Decryption
failure (72)!

I have also seen the above Solaris server side messages intermittently and
think they may be related to the issue I am experiencing. But if SMBv3 is
broken on Solaris, I do not understand why it works fine with MacOS.

2) Does mounting with "vers=2.1" work?

Yes, it works fine. In fact, it is required to make anything work as omitting
it results in the above behaviour.


Regarding your other comments about traces and encryption keys, I will need to
time to get these, but will indeed do so.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.