samba - Feb 2023 - SMB Multichannel not working?

Jeremy,

I am still looking into getting more debug logs from the Samba server but I
wanted to ask you where the details about the tcon bits are? I can't seem to
find the info in my wireshark capture, maybe I'm looking at the wrong
packet. Which packet(s) were you looking at?

Also, I wanted to share that I realized we exclusively access these shares as a
"guest" which should be mapped to the "samba-client" user on
the Samba host. But, when looking at the session setup packets I noticed the
user in the requests were "sso-csheehan" which is my local user on the
Windows client side. I am wondering if this is potentially the culprit of my
problem and what would be more appropriate instead.


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: Tuesday, February 7, 2023 1:56 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 Tue, Feb 07, 2023 at 03:55:58PM +0000, Carter Sheehan
wrote:
> Jeremy,
> Are you suggesting we need more debugging on the client or server side or
> both?
Server side. If the connecting user has r/w access to this
share, why is the access mask in the tcon being reported
as READ_ONLY.

On Wed, Feb 08, 2023 at 05:19:44PM +0000, Carter Sheehan
wrote:
>   Jeremy,
>   I am still looking into getting more debug logs from the Samba server but
>   I wanted to ask you where the details about the tcon bits are? I
can't
>   seem to find the info in my wireshark capture, maybe I'm looking at
the
>   wrong packet. Which packet(s) were you looking at?
In your Windows -> Samba trace, it's packet number 14 (Tree Connect
Response).

Expand that packet out with wireshark and you'll see at the end
of the reply.

Access Mask: 0x001f00a9
>   Also, I wanted to share that I realized we exclusively access these
shares
>   as a "guest" which should be mapped to the
"samba-client" user on the
>   Samba host. But, when looking at the session setup packets I noticed the
>   user in the requests were "sso-csheehan" which is my local user
on the
>   Windows client side. I am wondering if this is potentially the culprit of
>   my problem and what would be more appropriate instead.
If this share should be read-write, pick an appropriate
user that exists on the server with read-write access to
that data. As I don't know anything about your setup,
that's the only advice I can give.

Avoid "guest" with SMB2+ if you can.