samba - Jun 2022 - Issues configuring Samba

Whats missing here is.. 
>>  I can see SMB transactions on the network using Wireshark
SMB?  1 2 or 3. 

This looks to me a case of Eclipse not using minimal SMB2. 

Also, it "looks" bit like this one. 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=410883 

I suggest report it also to eclipse. 

Greetz, 

Louis



> -----Oorspronkelijk bericht-----
> Van: samba <samba-bounces at lists.samba.org> Namens Jeremy Allison
via
> samba
> Verzonden: dinsdag 7 juni 2022 18:20
> Aan: Andy Pont <andy.pont at sdcsystems.com>
> CC: samba at lists.samba.org
> Onderwerp: Re: [Samba] Issues configuring Samba
> 
> On Tue, Jun 07, 2022 at 09:49:17AM +0000, Andy Pont via samba wrote:
> >I have done some more poking around and it appears that as the Eclipse
> >IDE is closing it is getting stuck in a loop.  I can see SMB
> >transactions on the network using Wireshark and also repeated file
> >accesses on the server using inotifywait.
> >
> >I?m not sure whether I am interpreting the data I have collected
> >correctly but it looks as though Eclipse is missing a notification that
> >file(s) have been successfully closed and so is repeating the request.
> 
> What version of Samba is this ? This smells to me like the duplicate fileid
> problem we fixed in the latest 4.15, 4.16.
> 
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba

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.  I have since run tests with 
"min protocol = SMB2? and "min protocol = SMB3? to force the version.
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.

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.