PDA

View Full Version : WARNING!! This may make you sick!



Linus van Pelt
06-01-00, 09:29 PM
To reveal terrible pings i usually resort to the DOS Ping utility because I always thought netdiag.exe was lying to me. Now I am happy to report that netdiag works as is disgustingly illustrated in this little picture in a series of gruesome lag examples i like to call 1.4 Seconds of Agony http://www.speedguide.net/ubb/eek.gif. Enjoy

http://members.home.net/mikegreen/lag4.jpg

By the way 24.5.224.1 is my gateway. Ping it all you want I really dont care anymore.

Linus

John
12-29-00, 11:53 PM
I can't see the picture.

donald_k
12-30-00, 12:44 AM
neither can I

valley_hi
12-30-00, 01:14 AM
I am from Calif. Comcast @Home. I can't see your pic, but i pinged your gateway. 10pm pst friday night.
Pinging 24.5.224.1 with 32 bytes of data:

Reply from 24.5.224.1: bytes=32 time=72ms TTL=12
Reply from 24.5.224.1: bytes=32 time=70ms TTL=12
Reply from 24.5.224.1: bytes=32 time=59ms TTL=12
Reply from 24.5.224.1: bytes=32 time=65ms TTL=12

Ping statistics for 24.5.224.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 59ms, Maximum = 72ms, Average = 66ms

Bababooey
12-30-00, 01:27 AM
From Southern California
Reply from 24.5.224.1: bytes=32 time=50ms TTL=148
Reply from 24.5.224.1: bytes=32 time=51ms TTL=148
Reply from 24.5.224.1: bytes=32 time=51ms TTL=148
Reply from 24.5.224.1: bytes=32 time=56ms TTL=148
Ping statistics for 24.5.224.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 50ms, Maximum = 56ms, Average = 52ms



[This message has been edited by Bababooey (edited 12-30-2000).]

cablenut
12-30-00, 01:40 AM
I thought you were going to post something entirley different http://www.speedguide.net/ubb/smile.gif

------------------
Head webcheese and geek guru @ http://www.cablenut.com

cablenut
12-30-00, 01:42 AM
When your in dos box you can output to a text file like this

ping *.*.*.* > name.txt

Pinging Gateway with 32 bytes of data:

Reply from 24.13.142.1: bytes=32 time=70ms TTL=255
Reply from 24.13.142.1: bytes=32 time=70ms TTL=255
Reply from 24.13.142.1: bytes=32 time=40ms TTL=255
Reply from 24.13.142.1: bytes=32 time=50ms TTL=255
Reply from 24.13.142.1: bytes=32 time=20ms TTL=255
Reply from 24.13.142.1: bytes=32 time=30ms TTL=255
Reply from 24.13.142.1: bytes=32 time=20ms TTL=255
Reply from 24.13.142.1: bytes=32 time=70ms TTL=255
Reply from 24.13.142.1: bytes=32 time=60ms TTL=255
Reply from 24.13.142.1: bytes=32 time=130ms TTL=255
Reply from 24.13.142.1: bytes=32 time=50ms TTL=255
Reply from 24.13.142.1: bytes=32 time=70ms TTL=255
Reply from 24.13.142.1: bytes=32 time=110ms TTL=255
Reply from 24.13.142.1: bytes=32 time=20ms TTL=255
Reply from 24.13.142.1: bytes=32 time=10ms TTL=255
Reply from 24.13.142.1: bytes=32 time=20ms TTL=255
Reply from 24.13.142.1: bytes=32 time=20ms TTL=255
Reply from 24.13.142.1: bytes=32 time=50ms TTL=255
Reply from 24.13.142.1: bytes=32 time=50ms TTL=255
Reply from 24.13.142.1: bytes=32 time=120ms TTL=255

Ping statistics for 24.13.142.1:

Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 10ms, Maximum = 130ms, Average = 54ms

------------------
Head webcheese and geek guru @ http://www.cablenut.com

[This message has been edited by cablenut (edited 12-30-2000).]

blebs99
12-30-00, 03:57 AM
Pinging 24.5.224.1 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 24.5.224.1:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
03:56 est. 12/30/00

dannjr
12-30-00, 04:09 AM
Hey if everyone is sending a ping I figure I could send one too mine came out like the picture...
Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-1999 Microsoft Corp.

C:\>ping 24.5.224.1

Pinging 24.5.224.1 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 24.5.224.1:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

------------------

THE WORLDS THINNEST BOOK: Things I can't afford - by Bill Gates
Chicago Microsystems (http://microsyspro.com)
dannjr@microsyspro.com
Speedguide has a great search engine (http://www.speedguide.net/cgi-bin/search.cgi?action=intro&default=2)

donald_k
12-30-00, 04:15 AM
Tracing route to cr4-hfc1.mntp1.il.home.net [24.5.224.1]
over a maximum of 30 hops:

1 29 ms 29 ms 30 ms 24.70.178.1
2 29 ms 29 ms 27 ms rd1tb-fe0-1-0.tb.shawcable.net [24.64.191.129]
3 38 ms 34 ms 35 ms rd1nr-fe1-1-0.wp.shawcable.net [204.209.213.25]

4 60 ms 60 ms 66 ms rc1sh-atm3-0-1.mt.shawcable.net [204.209.215.129
]
5 88 ms 64 ms 66 ms home1-pos.mt.shawcable.net [204.209.215.238]
6 122 ms 126 ms 126 ms c1-pos7-0.bflony1.home.net [24.7.74.25]
7 128 ms 124 ms 126 ms c1-pos1-0.clevoh1.home.net [24.7.65.5]
8 121 ms 126 ms 126 ms c1-pos3-0.chcgil1.home.net [24.7.64.173]
9 126 ms 126 ms 124 ms bb1-pos5-0.rdc1.il.home.net [24.7.74.90]
10 122 ms 125 ms 127 ms 10.0.244.30
11 * * * Request timed out.

hehe I am glad Shaw does not route through the @Home backbone all the time though. The pings may be a slight bit higher because Shaw right now is screwed up.

robbo486
12-30-00, 07:51 AM
C:\WINDOWS>ping -t 24.5.224.1

Pinging 24.5.224.1 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 24.5.224.1:
Packets: Sent = 5, Received = 0, Lost = 5 (100% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

somehow I think it ain't workin boys :-)

shaft01
12-30-00, 08:21 AM
Originally posted by robbo486:
C:\WINDOWS>ping -t 24.5.224.1

Pinging 24.5.224.1 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 24.5.224.1:
Packets: Sent = 5, Received = 0, Lost = 5 (100% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

somehow I think it ain't workin boys :-)

I dunno about that.......I got an average of about 60ms with 0 loss.....

shaft01
12-30-00, 08:26 AM
Originally posted by robbo486:
Some how I think it ain't workin boys :-)[/B]

whoops.....as I was trying to say http://www.speedguide.net/ubb/smile.gif

Pinging 24.5.224.1 with 32 bytes of data:

Reply from 24.5.224.1: bytes=32 time=69ms TTL=11

Reply from 24.5.224.1: bytes=32 time=55ms TTL=11

Reply from 24.5.224.1: bytes=32 time=41ms TTL=11

Reply from 24.5.224.1: bytes=32 time=55ms TTL=11

Ping statistics for 24.5.224.1:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 41ms, Maximum = 69ms, Average = 55ms

Seems to work here......

HalfLifer
12-30-00, 09:27 AM
Works fine for me.

http://www.speedcorp.net/broadband/images/24gateway.jpg

HalfLifer
12-30-00, 10:38 AM
I can bet you he isnt on DOCSIS...

HalfLifer
12-30-00, 01:10 PM
Its his gateway.

STV
12-30-00, 01:16 PM
Tracing route to cr4-hfc1.mntp1.il.home.net [24.5.224.1]

over a maximum of 30 hops:

1 11 ms 8 ms 10 ms 10.78.7.1

2 14 ms 11 ms 8 ms bb1-fe1-0.ovrlnd1.mo.home.net [24.8.86.1]

3 33 ms 51 ms 32 ms c1-se6-0.kscymo1.home.net [24.7.73.173]

4 31 ms 36 ms 56 ms c1-pos4-0.omahne1.home.net [24.7.64.145]

5 43 ms 61 ms 50 ms c1-pos1-0.desmia1.home.net [24.7.64.138]

6 52 ms 46 ms 51 ms c1-pos2-0.chcgil1.home.net [24.7.64.166]

7 64 ms 72 ms 83 ms c1-pos5-0.chcgil1.home.net [24.7.77.169]

8 67 ms 85 ms 83 ms bb1-pos5-0.rdc1.il.home.net [24.7.74.90]

9 58 ms 62 ms 81 ms 10.0.244.30

10 76 ms 84 ms 83 ms cr4-hfc1.mntp1.il.home.net [24.5.224.1]

Trace complete.

tekelberry
12-30-00, 04:01 PM
Pinging 24.5.224.1 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 24.5.224.1:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Mystic
12-30-00, 06:43 PM
Heck,,,nothing else to do right now,,,might as well:

ping 24.5.224.1

Pinging 24.5.224.1 with 32 bytes of data:

Reply from 24.2.192.59: bytes=32 time=80ms TTL=4
Reply from 24.2.192.59: bytes=32 time=70ms TTL=4
Reply from 24.2.192.59: bytes=32 time=150ms TTL=4
Reply from 24.2.192.59: bytes=32 time=151ms TTL=4

Ping statistics for 24.5.224.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 70ms, Maximum = 151ms, Average = 112ms

IndyOST
12-30-00, 06:58 PM
All right, time for my lemming-esque post http://www.speedguide.net/ubb/wink.gif :

Pinging 24.5.224.1 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 24.5.224.1:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Scoot
12-31-00, 12:34 AM
24.5.224.1 =What is this IP?
Gateway? Are they all different?

C:\WINDOWS\Desktop>ping 24.5.224.1

Pinging 24.5.224.1 with 32 bytes of data:

Reply from 24.5.224.1: bytes=32 time=57ms TTL=12
Reply from 24.5.224.1: bytes=32 time=71ms TTL=12
Reply from 24.5.224.1: bytes=32 time=312ms TTL=12
Reply from 24.5.224.1: bytes=32 time=56ms TTL=12

Ping statistics for 24.5.224.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 56ms, Maximum = 312ms, Average = 124ms


------------------
Quest for Knowledge

Beelzebub
12-31-00, 12:56 AM
Cool, a ping party! - count me in...

Pinging 24.5.224.1 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 24.5.224.1:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

darn, I hate when that happens

------------------
despite all my rage, I am still just a rat in a cage . . .

rmrucker
12-31-00, 03:23 AM
OK, this is crazy! I ignored that title for a long time, then I just had to check it out! http://www.speedguide.net/ubb/smile.gif

YES, I pinged that address and I got "timed out". My tracert dies at hop 8. It finally stops with a "Destination net unreachable" message.

What I find fascinating is this: CHECK OUT THOSE TTL's!!!!!!

Mystic TTL = 4
Scoot TTL = 12
Halflifer TTL = 13
etc...

OK, those ICMP Echo Replies are leaving their destination with a TTL of 255 (the default for ICMP ping commands). Hmmm...

tekelberry
01-01-01, 02:26 AM
My trace route to that address: my cable modem ip is x'ed out for security:


Tracing route to cr4-hfc1.mntp1.il.home.net [24.5.224.1]

over a maximum of 30 hops:

1 14 ms <10 ms 13 ms xx.xxx.xx.x

2 <10 ms 14 ms 14 ms mke-rtco-gsr-a-srp2-0.wi.rr.com [24.160.225.17]

3 27 ms 14 ms 28 ms pos-5-3.clmboh1-rtr3.columbus.rr.com [24.95.80.133]

4 27 ms 14 ms 14 ms srp0-0.clmboh1-rtr4.columbus.rr.com [24.95.81.230]

5 55 ms 55 ms 68 ms 12.125.143.61

6 55 ms 68 ms 55 ms gbr1-p50.cgcil.ip.att.net [12.123.5.74]

7 55 ms 55 ms 55 ms gr2-p340.cgcil.ip.att.net [12.123.5.130]

8 55 ms 69 ms 55 ms att-gw.chi.home.net [192.205.32.62]

9 55 ms 54 ms 69 ms bb1-pos5-0.rdc1.il.home.net [24.7.74.90]

10 55 ms 55 ms 69 ms 10.0.244.30

11 * * * Request timed out.

12 * * * Request timed out.

13 * * * Request timed out.

14 * * * Request timed out.

15 * * * Request timed out.

16 * * * Request timed out.

17 * * * Request timed out.

18 * * * Request timed out.

19 * * * Request timed out.

20 * * * Request timed out.

21 * * * Request timed out.

22 * * * Request timed out.

23 * * * Request timed out.

24 * * * Request timed out.

25 * * * Request timed out.

26 * * * Request timed out.

27 * * * Request timed out.

28 * * * Request timed out.

29 * * * Request timed out.

30 * * * Request timed out.

Trace complete.

balakov10
01-01-01, 05:11 AM
C:\WINDOWS>ping 24.5.224.1

Pinging 24.5.224.1 with 32 bytes of data:

Request timed out.
Request timed out.
Reply from 24.5.224.1: bytes=32 time=3980ms TTL=11
Request timed out.

Ping statistics for 24.5.224.1:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
Approximate round trip times in milli-seconds:
Minimum = 3980ms, Maximum = 3980ms, Average = 995ms

b/c this was so fun and I'm downloading something I will try it again http://www.speedguide.net/ubb/smile.gif)

THERE WE GO BOYS
C:\WINDOWS>ping 24.5.224.1

Pinging 24.5.224.1 with 32 bytes of data:

Reply from 24.5.224.1: bytes=32 time=408ms TTL=11
Reply from 24.5.224.1: bytes=32 time=228ms TTL=11
Reply from 24.5.224.1: bytes=32 time=240ms TTL=11
Reply from 24.5.224.1: bytes=32 time=375ms TTL=11

Ping statistics for 24.5.224.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 228ms, Maximum = 408ms, Average = 312ms