This is our old Q&A Site. Please post any new questions and answers at

We are experiencing a strange behaviour in some TCP connection. During a tcp connection we are sending data from compiter A to computer B. (wireshark is capturing packet on computer B) wiresharking the connection we can see the data from A to B , the SEQ number are ok and the ACKs are coming from B to A... after a while we can see the the computer B doesn't acknoledge the data any more, even if the data are captured by wireshark. (we are just downloading a JPG using a browser from "A" http server, it happen with different browser).. Example

A send packet 100 B ACK it
A send packet 101 B ACK 100 again (I can see packet 101 in wireshark capture)
A send packet 102 B ACK 100 again or do nothing (I can see packet 102 as well)
after a while A resend packet 101 then B ack 101 and 102....

that can happen several times... with several packets... and of course often the connection is terminated..

asked 30 Jul '13, 06:06

OmarP's gravatar image

accept rate: 0%

edited 30 Jul '13, 08:00

grahamb's gravatar image

grahamb ♦

seems to be something wrong on hardware calculated checksum....

(30 Jul '13, 07:49) OmarP

Posting a link to a public capture showing the symptoms (if you can share the capture) would be a great help.

Cloudshark, Google Drive and Dropbox are all useful options.

(30 Jul '13, 08:02) grahamb ♦
Be the first one to answer this question!
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text]( "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:


question asked: 30 Jul '13, 06:06

question was seen: 988 times

last updated: 30 Jul '13, 08:02

p​o​w​e​r​e​d by O​S​Q​A