Wireshark-users: Re: [Wireshark-users] [TCP Previous segment lost], TCP [TCP Dup ACK 125#1]
: Wes <wes_r@xxxxxxxxx
: Tue, 8 Sep 2009 08:15:58 -0700 (PDT)
You could try using something like Pingplotter. It might give you a better understanding of where the problem is.
Wireshark will not tell you where a packet was lost.
--- On Tue, 9/8/09, Nikolai Longolius <longolius@xxxxxxxxxxxxxx> wrote:
> From: Nikolai Longolius <longolius@xxxxxxxxxxxxxx>
> Subject: Re: [Wireshark-users] [TCP Previous segment lost], TCP [TCP Dup ACK 125#1]
> To: wireshark-users@xxxxxxxxxxxxx
> Date: Tuesday, September 8, 2009, 9:23 AM
> Martin + Jeffrey,
> thanks for your quick response. In the meantime I am in
> contact with the ISP who "produces" the packet
> loss. At least I hope its them. Its pretty hard to find out
> who's the bad guy in the chain. I did use mtr on my mac
> to trace + ping all hosts on the route but that didn't
> turn out any useful information to me.
> Am I right, that from Wireshark capturing there is no way
> to reconstruct on what route a packet got lost?
> Nikolai Longolius
> schnee von morgen webTV GmbH
> Manteuffelstr 66
> 10999 Berlin
> M +49 170 4777 477
> -----Inline Attachment Follows-----
> 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