 | 1 | initial version |
The screenshot suggests that the systems use SMB (not SMB2) to exchange data.
Most applications make blocking calls when they read or write files. In other words: Send data, wait for an acknowledgement, then send the next block etc. In case of an error, the client has to wait until the TCP retransmission has been resolved.
One of the improvements with SMB2 was the introduction of pipelining, where clients could fire away a bunch of requests at once. A sequence like "Create File, Query Information, Close" takes only one TCP turn.
I wonder, how your application reacts, if SMB2 is used. Of course, the calls have to be non-blocking ...
Good luck
Eddi
Copyright Wireshark Foundation, 2017-2023 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
