From: samba-bugs@samba.org
To: cifs-qa@samba.org
Subject: [Bug 14713] SMBv3 negotiation fails with a Solaris server
Date: Tue, 25 May 2021 18:51:59 +0000 [thread overview]
Message-ID: <bug-14713-10630-kvGkNHSHah@https.bugzilla.samba.org/> (raw)
In-Reply-To: <bug-14713-10630@https.bugzilla.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.
next prev parent reply other threads:[~2021-05-25 18:52 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-14713-10630@https.bugzilla.samba.org/>
2021-05-25 14:14 ` [Bug 14713] SMBv3 negotiation fails with a Solaris server samba-bugs
2021-05-25 18:19 ` samba-bugs
2021-05-25 18:26 ` samba-bugs
2021-05-25 18:51 ` samba-bugs [this message]
2021-05-25 19:03 ` samba-bugs
2021-05-25 19:09 ` samba-bugs
2021-05-25 19:09 ` samba-bugs
2021-05-25 19:13 ` samba-bugs
2021-05-25 19:19 ` samba-bugs
2021-05-25 19:27 ` samba-bugs
2021-05-25 19:37 ` samba-bugs
2021-05-25 19:42 ` samba-bugs
2021-05-25 19:43 ` samba-bugs
2021-05-25 19:47 ` samba-bugs
2021-05-25 20:31 ` samba-bugs
2021-05-25 20:38 ` samba-bugs
2021-05-25 20:55 ` samba-bugs
2021-05-25 21:40 ` samba-bugs
2021-05-25 22:33 ` samba-bugs
2021-05-26 8:57 ` samba-bugs
2021-05-26 9:00 ` samba-bugs
2021-05-26 9:47 ` samba-bugs
2021-05-26 15:36 ` samba-bugs
2021-05-26 18:59 ` samba-bugs
2021-05-26 21:51 ` samba-bugs
2021-05-26 21:54 ` samba-bugs
2021-05-26 22:09 ` samba-bugs
2021-05-26 22:26 ` samba-bugs
2021-05-26 22:39 ` samba-bugs
2021-05-27 17:33 ` samba-bugs
2021-05-30 13:51 ` samba-bugs
2021-06-04 6:42 ` samba-bugs
2021-06-04 10:17 ` samba-bugs
2022-02-20 19:07 ` samba-bugs
2022-05-11 18:46 ` samba-bugs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-14713-10630-kvGkNHSHah@https.bugzilla.samba.org/ \
--to=samba-bugs@samba.org \
--cc=cifs-qa@samba.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).