Lag Spikes, Cmd results

Status
Not open for further replies.
here is a game server from the laptop on my network... i think i was mistaken about its lags... sorry bout that...:eek:
untitled-8.jpg
 
Okay, and here are the results from the desktop. Both pathpings were done at the same time and to the same server.

Untitled-9.jpg
 
ok; BOTH have similar losses at nodes 5-6-7 :(

the desktop had 1% lost at your dslrouter (likely due to parallel outgoing traffic; ie workloading on your lan)

laptop had physical link errors between nodes 8-9;
this can be due to hi traffic volumes in/out bound from the "server"

btw: did you notice that the desktop reports only EIGHT nodes while the laptop
reports NINE? the losses between 8-9 are 99% and likely this cause the pathping to not find the
last node

other issue: node 9 has an invalid ip address [0.0.0.0] AND
this is not the ip address that you were pinging in the first place!! (72.5.250.84)
this is NOT good to say the least :(

Code:
$ whois -H 72.5.250.84
Internap Network Services PNAP-09-2004 (NET-72-5-0-0-1)
                                  72.5.0.0 - 72.5.255.255
The Ultimate Game Server INAP-DAL-EXT1-[B]ULTIMATEGAME[/B]-9721 (NET-72-5-250-0-1)
                                  72.5.250.0 - 72.5.250.255
 
Is the packet suppose to come back.., like on the laptop where it comes to "basement" (name of laptop)?
 
ping (and the derived pathping) has a protocol that sends a short message and
then listens for the reply. the time for the round trip is 'the ping response time'.
by setting some special bits in the tcp header, the reply records the node names that it has traversed.

'Basement' is just bogus.

I think you and I have taken this as far as the original request can be taken.

yes you have variable lag times.

no, it's not on your system.

this is just life on tcp/internet.

have a good day.
 
Status
Not open for further replies.
Back