The log showed at least 10-20 retransmit / dup ack /segment losses per minute during normal usage. Then, when I had a disconnect, it shot up to dozens of these per second. FYI, I know very little about the Wireshark tool or how to do a full analysis of this problem.
Offloading the Segmentation of Large TCP Packets - Windows Oct 24, 2019 Understanding TCP internals step by step for Software Nov 12, 2019
Offloading the Segmentation of Large TCP Packets - Windows
The Internet Protocol Stack
TCP Series #3: Network Packet Loss, Retransmissions, and
The First Segment Has Sequence Number 80; The Second Has Sequence Number 120. Host B Sends An Acknowledgement (ACK) Whenever It Receives A Segment From Host A, Indicating The Next Frame It Is Awaiting. If The First Segment Is Lost But The Second Segment Arrives At B, Wireshark: Re: Packets not captured, tcp acking lost Upon transfer of a BLOB, wire shark is showing many "Tcp ACKed lost segment" packets. On top of this there is no evidence of any of the SOAP data, other than the initial header. Now I've search for this lost segment business, and no forums really seem TCP Connection Open - freesoft.org