https://bugzilla.samba.org/show_bug.cgi?id=14713 --- Comment #16 from Steve French <sfrench@xxxxxxxxx> --- Based on the trace you sent - can see that when mounting with 3.1.1 (or default which ends up the same thing), the server responds with SMB2_ENCRYPTION_CAPABILITIES set to CipherId: AES-128-GCM which is interesting because that is the 'normal' case we see (Windows, Azure, current Samba server etc.) so this is less likely to be a bug in the client due to falling back to something different than the more common GCM. Do you have the equivalent trace from smbclient (the Samba userspace tool) to the same share (trying to negotiate SMB3.1.1) for comparison? -- You are receiving this mail because: You are the QA Contact for the bug.
