https://bugzilla.samba.org/show_bug.cgi?id=14713 --- Comment #10 from Steve French <sfrench@xxxxxxxxx> --- Since the Solaris server logs: 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)! are you sure that you mounted without encryption (ie did not specify "seal=" on mount)? If this connection is defaulting to encryption whether or not the client specifies it on mount, that implies that the server is configured with encryption as required ... which is odd - because the server allowed vers=2.1 (which is not encrypted, encryption was added in the SMB3 and later versions of the protocol and not supported with SMB2.1) but fails with vers=3.0 or 3.1.1 (smb3.1.1 is the typical default) which presumably means the server is negotiating with encryption required (but only for a subset of dialects). Strange server configuration. Can you send or attach the vers=3.1.1 (or default with no vers= specified) wireshark trace so we can see what crypto algorithm the server is defaulting to (even if we can't see the keys - we can see how it is trying to encrypt/decrypt if smb3.1.1 is used instead of smb3.0) -- You are receiving this mail because: You are the QA Contact for the bug.
