On Wed, 2022-06-08 at 09:26 +0000, Andy Pont via samba wrote:> Louis wrote... > > > Whats missing here is.. > > > > I can see SMB transactions on the network using Wireshark > > SMB? 1 2 or 3. > When I initially found the issue after the upgrade to Samba there was > no > version definition in the configuration.If there is no 'client min protocol' and/or 'server min protocol' set in smb.conf, then you will be using the default setting. Before Samba 4.11.0 , the default was 'CORE', from 4.11.0 this was raised to 'SMB2_02'.> I have since run tests with > "min protocol = SMB2? and "min protocol = SMB3? to force the > version.'min protocol' is a synonym for 'server min protocol'> Whilst doing so, I have also configured the protocol_vers_map option > in > the macOS /etc/nsmb.conf to match. From the Wireshark trace, it is > showing as having negotiated SMB 3.11.You shouldn't have to set any 'min protocol', negotiation should find the best one to use, it should start at SMBv3 and work down from that.> > The same third party tool that is based on Eclipse (v4.18 possibly > also > known as 2020-12) works without issue on a Windows machine when > accessing the same share. > -Andy.We are going to need wireshark traces from both the Windows connecting and the other (MacOS ?) machine that connects. Rowland
Hmm, which samba version per server is used, that needs clearity. This might be an old bug.> -----Oorspronkelijk bericht----- > Van: samba <samba-bounces at lists.samba.org> Namens Rowland Penny via > samba > Verzonden: woensdag 8 juni 2022 11:43 > Aan: samba at lists.samba.org > CC: Rowland Penny <rpenny at samba.org> > Onderwerp: Re: [Samba] Issues configuring Samba > > On Wed, 2022-06-08 at 09:26 +0000, Andy Pont via samba wrote: > > Louis wrote... > > > > > Whats missing here is.. > > > > > I can see SMB transactions on the network using Wireshark > > > SMB? 1 2 or 3. > > When I initially found the issue after the upgrade to Samba there was > > no version definition in the configuration. > > If there is no 'client min protocol' and/or 'server min protocol' set in > smb.conf, then you will be using the default setting. Before Samba > 4.11.0 , the default was 'CORE', from 4.11.0 this was raised to 'SMB2_02'. > > > I have since run tests with > > "min protocol = SMB2? and "min protocol = SMB3? to force the version. > > 'min protocol' is a synonym for 'server min protocol' > > > Whilst doing so, I have also configured the protocol_vers_map option > > in the macOS /etc/nsmb.conf to match. From the Wireshark trace, it is > > showing as having negotiated SMB 3.11. > > You shouldn't have to set any 'min protocol', negotiation should find the best > one to use, it should start at SMBv3 and work down from that. > > > > > The same third party tool that is based on Eclipse (v4.18 possibly > > also known as 2020-12) works without issue on a Windows machine when > > accessing the same share. > > -Andy. > > We are going to need wireshark traces from both the Windows connecting > and the other (MacOS ?) machine that connects. > > Rowland > > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba
Rowland wrote?>We are going to need wireshark traces from both the Windows connecting >and the other (MacOS ?) machine that connects.I have captured both Windows and macOS traces with Wireshark which can be downloaded from [1]. With the Windows trace, the IDE was opened, one source file was edited and saved and then the IDE closed. In the macOS trace, it shows the mapping of the share, the same workspace being opened, and the same source file being edited and saved. In the macOS case, it actually locked up saving the file - when the IDE window has focus the spinning beach ball is shown. -Andy. [1] - https://drive.google.com/file/d/168-Qopm3E1I5vvLZw--5ktjETt-f2ZBd/view?usp=sharing