Hi, I'm facing a strange issue. We have two systems communicating via RFC, but this communication breaks everytime with the following issue: The Client receives an TCP ACK with an SLE=2734286 and SLR=2777173 Client then starts a retransmission of the "missing" packages Then receives a TCP DUP ACK with SACK: 2777089-2777173 2734286-2777173 This is weird, isnt it? The SACK parameters are overlapping. The Client then sends again the missing packages but always receives the TCP DUP ACK. After 5 tries the client gives up. Its Windows 2003 to Linux 2.6.32. Is someone of you aware of such an issue? The Network connection itself is working without issues (for ex. when copying data via SSH, there the SACK protocol seems to work correct). Thanks and kind regards Stefan asked 07 Nov '12, 07:13  sLy |
This is a static archive of our old Q&A Site.
Please post any new questions and answers at ask.wireshark.org.
you need to supply the ACK number from the Acknowledgements in order to solve this, please provide ACK and SACK information for those packets plus if possible the tcp.len of the data packets
Better yet, put the offending capture on cloudshark for us all to see.