search for: caaptur

Ah, ok, "directory handle leases"... Ouch, I see... :-( In this case, I will first repeat my test scenario with a Windows SMB2 server and report back here. Based on the results of this exercise, you can then advise whether you still want to move this to smb-technical and raise this with Microsoft folks (who still might have a simple workaround "fix" to improve their SMB2

...with Pattern "*" - which probably means that the Windows SMB2 server does some caching here. In order to write the ~ 1000 files in my old test scenario, the total packet capture size for a SMB1 client against both a Samba or a Windows SMB1 server is about 10 MB, while the total packet caapture size for a SMB2 client against a SMB2 server (regardless whether Samba or Windows SMB2 server!!!) is about 32 MB, which clearly points to the inefficient use of Find requests with "*" pattern. (Unfortunately, the Windows SMB2 server can still handle this 32MB communication in 18 seco...