smb2 between client and server fails every single time for large file transfers , while small file transfers work just fine.
https://www.cloudshark.org/captures/6... --small
https://www.cloudshark.org/captures/c... --large
cant seem to understand why
Do you have some load balancer, VPN gateway, WAN optimizer or other active device in your WAN?
Both traces include a broken connection resulting in a three way handshake.
We see in both traces
Client 10.241.5.133 SYN with MSS = 1460
Server 192.168.5.123 SYN/ACK with MSS = 1338
Since the smaller value is 1338, no TCP segment should hold more than 1338 byte. The client keeps to that limit, but the server is sending packets with a payload of 1380 byte. This suggests, that there is at least one device in the return path that modifies the MSS of the SYN/ACK packet. My guess is that packets are modified in transit in both directions with different values for incoming or outgoing packets.
Certain VPN gateways or DSL routers would modify the segment size in transit. Obviously client and server are working with a different MSS which can lead to all types of trouble.
I would only continue this analysis after both server and client work with the same MSS. This might be a good opportunity to review all other settings of this intermediate device.
Remarkably the server offers an initial receive window of 8192 * 2^8 which results in a 2 GByte buffer. I find this a surprisingly aggressive value that is helpful for "Long Fat Networks" (LFN), like 10 GBit/sec or more for links with very long round trip times (way above 100 msec).
Good luck
Eddi
That was also my first thought. But the segments with a payload >1338 bytes are all comming from 192.168.5.123 and going to 10.241.5.133, and 10.241.5.133 has a MMS of 1460 bytes. All segments from the client 10.241.5.133 to the server 192.168.5.123 are less or equal 1338 bytes. So everything is fine there. If there is a router or middlebox on the way with a smaller MSS, we should see this in the SYN/SYNACK packet.
Asked: 2020-05-15 22:39:14 +0000
Seen: 445 times
Last updated: May 18 '20
It's not the file size, it's the direction.
SMB transfer from 10.241.5.133 to 192.168.5.123 is bad because the ACKs from 192.168.5.123 to 10.241.5.133 get lost or delayed during the transmission to 10.241.5.133.
SMB transfer from 192.168.5.123 to 10.241.5.133 runs fine.
Maybe a port duplex mismatch on the way? Bandwidth utilization of down- or upload? IPS?