[Samba] SMB Multichannel not working?

Jeremy Allison jra at samba.org
Thu Feb 2 21:20:31 UTC 2023

On Thu, Feb 02, 2023 at 08:48:01PM +0000, Carter Sheehan via samba wrote:
>Thanks for the clue, but I am confused by the response and evidence. In the screenshots, as you can see there are 2 protocol negotiation requests from the client (1 of SMB protocol, the other of SMBv2). In the first request (SMB protocol) there simply is no part of the packet that mentions capabilities. Is that expected from an SMB protocol packet, should the client have specified it's capabilities? It's only when the protocol switches to SMBv2 that the capabilities are listed (and that's where the contradictory responses from the server come from).
>It's worth noting that the Get-SmbConnection command in PowerShell on my client side shows that the dialect chosen is SMB 3_1_1, and when I run the command smbstatus on my server I can see the client connected with SMB3_1_1.

You have to realize I can't read the things you posted,
and you're not giving access to the wireshark traces,
so I'm just going via your text descriptions.

So it looks like your client is doing the SMB1 -> SMB2 bootstrap
in negprot. That usually only done for "old" connections to
unknown servers.

Try just removing the SMB1 client code from your client.
Why is it even there ?

More information about the samba mailing list