[Samba] SMB Multichannel not working?

Carter Sheehan csheehan at vestmark.com
Mon Feb 6 20:31:02 UTC 2023


That's what is so vexxing about this, the SMB client in Windows Server 2019 has SMBv1 disabled by default. Using the articles you provided, I can confirm that SMBv1 is not enabled for the SMB server/client.

Carter Sheehan
Cloud Engineer
d: +1 (781) 224-7753
e: csheehan at vestmark.com

This e-mail and any attachments hereto, are intended for use by the addressee(s) only and may contain information that is confidential information of Vestmark, Inc. If you are not the intended recipient of this e-mail, or if you have otherwise received
this e-mail in error, please immediately notify me by telephone or by e-mail, and please permanently delete the original, any print outs and any copies of the foregoing. Any dissemination, distribution or copying of this e-mail is strictly prohibited.
From: Jeremy Allison <jra at samba.org>
Sent: Monday, February 6, 2023 2:17 PM
To: Carter Sheehan <csheehan at vestmark.com>
Cc: samba at lists.samba.org <samba at lists.samba.org>
Subject: Re: [Samba] SMB Multichannel not working?

External Email
This email was NOT sent from someone at Vestmark

On Sun, Feb 05, 2023 at 09:11:41PM +0000, Carter Sheehan wrote:
> Jeremy,
> I am clearing the contents of the packet capture with my security team and
> I'll have it available to you some time tomorrow.
> Regarding protocol negotiation, I have tried using some of the available
> server/client min/max protocol config options for smb.conf hoping it would
> "force" the use of SMB3+ but I still see the same SMB/SMBv2 packets in a
> wireshark capture and both the client and server display the connection as
> using dialect 3_11, so that doesn't seem to have any impact whatsoever for
> me.

This is a clients feature I think, not controllable on the server-side.

When connecting to an unknown server a Windows client tries the SMB1->SMB2+

Just remove SMB1 from this client.



More information about the samba mailing list