Wireshark-users: Re: [Wireshark-users] Ack number always equals 1

From: dan meyer <dan@xxxxxxxxxxxxxxxx>
Date: Sat, 24 Oct 2009 15:21:48 -0500
Hello Giovanni
 
From http://wiki.wireshark.org/TCP_Relative_Sequence_Numbers 
 
'By default Wireshark and TShark will keep track of all TCP sessions and convert all Sequence Numbers (SEQ numbers) and Acknowledge Numbers (ACK Numbers) into relative numbers. '
 
Since you are using a crossover cable, it's very unlikely you have a network problem. That leaves OS, driver or application issues. If other apps don't have any network problems, your application is probably at fault here

Good luck, and let us know what you find!
 
-- Dan Meyer
 
On Sat, Oct 24, 2009 at 11:02 AM, Giovanni Parodi <giovanniparodi79@xxxxxxxx> wrote:

Good morning everyone,
I'm a newbye in networking application and I trying to debug a strange problem that I have sending through TCP protocol some data from a DSP based system to a PC application
The problem is that that the application running on PC disconnects after few packets, and so I used wireshark to debug the problem.
It seems some packet get lost (I use a cross cable to connect the devices) and that the system isn't able to recover from such a problem.
Furthermore I found out that Acknowledgement number generated by the DSP runnign the server appl always equals 1.
Do you have any idea about some wrong setting that could generate such a behaviour?
Giovanni


___________________________________________________________________________
Sent via:    Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx>
Archives:    http://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
            mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe