ping this IP 69.56.238.122 and this IP 63.247.94.13 and tell me what lowest ms response you get for each one.
I'm deciding on how to increase performance for the site
ping this IP 69.56.238.122 and this IP 63.247.94.13 and tell me what lowest ms response you get for each one.
I'm deciding on how to increase performance for the site
51 for the first IP and 25 for the second. The averages for both were higher, do you care about that? If so avg. 55ms for the first, 42 for the second.
I love the summer months!
How do you "ping"?Originally posted by SaintHax@Sep 30 2004, 02:27 AM
ping this IP 69.56.238.122 and this IP 63.247.94.13 and tell me what lowest ms response you get for each one.
Only thing worse than failure is not trying
i just wanna know where it went in xp !! i havent used ping since windows 98
"One day the absurdity of the almost universal human belief in the slavery of other animals will be palpable. We shall then have discovered our souls and become worthier of sharing this planet with them."
~Martin Luther King Jr.
I'm not signing this without my lawyer.
bring up a command prompt (winXP: START->RUN->"cmd") and type "PING put.ip.address.here" and press ENTER.
to leave the command prompt, type "exit" and press ENTER
Sorry Brian
Call me comp-illeterate!!!
I don't understand that!! I should, butttttttttttttt I don't!!
Xplane!!
Only thing worse than failure is not trying
Gotcha!!Originally posted by -Kosh-@Sep 30 2004, 10:14 AM
bring up a command prompt (winXP: START->RUN->"cmd") and type "PING put.ip.address.here" and press ENTER.
to leave the command prompt, type "exit" and press ENTER
Only thing worse than failure is not trying
http://en.wikipedia.org/wiki/PingOriginally posted by Chukwuka@Sep 30 2004, 10:16 AM
Sorry Brian
Call me comp-illeterate!!!
I don't understand that!! I should, butttttttttttttt I don't!!
Xplane!!
You're the man, -Kosh-
Only thing worse than failure is not trying
Z:\>ping 69.56.238.122
Pinging 69.56.238.122 with 32 bytes of data:
Reply from 69.56.238.122: bytes=32 time=51ms TTL=53
Reply from 69.56.238.122: bytes=32 time=52ms TTL=53
Reply from 69.56.238.122: bytes=32 time=52ms TTL=53
Reply from 69.56.238.122: bytes=32 time=52ms TTL=53
Ping statistics for 69.56.238.122:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 51ms, Maximum = 52ms, Average = 51ms
Z:\>ping 63.247.94.13
Pinging 63.247.94.13 with 32 bytes of data:
Reply from 63.247.94.13: bytes=32 time=28ms TTL=239
Reply from 63.247.94.13: bytes=32 time=28ms TTL=239
Reply from 63.247.94.13: bytes=32 time=30ms TTL=239
Reply from 63.247.94.13: bytes=32 time=27ms TTL=239
Ping statistics for 63.247.94.13:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 27ms, Maximum = 30ms, Average = 28ms
there we go, just right. keep walking...
Pinging 69.56.238.122 with 32 bytes of data:
Reply from 69.56.238.122: bytes=32 time=133ms TTL=52
Reply from 69.56.238.122: bytes=32 time=129ms TTL=52
Reply from 69.56.238.122: bytes=32 time=129ms TTL=52
Reply from 69.56.238.122: bytes=32 time=159ms TTL=52
Ping statistics for 69.56.238.122:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 129ms, Maximum = 159ms, Average = 137ms
C:\Documents and Settings\FD>PING 63.247.94.13
Pinging 63.247.94.13 with 32 bytes of data:
Reply from 63.247.94.13: bytes=32 time=110ms TTL=246
Reply from 63.247.94.13: bytes=32 time=109ms TTL=246
Reply from 63.247.94.13: bytes=32 time=109ms TTL=246
Reply from 63.247.94.13: bytes=32 time=119ms TTL=246
Ping statistics for 63.247.94.13:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 109ms, Maximum = 119ms, Average = 111ms
C:\Documents and Settings\FD>
IF YOU CANT BEAT THEM, AVOID THEM FOR THE REST OF YOUR LIFE.
Microsoft® Windows DOS
©Copyright Microsoft Corp 1990-2001.
U:\>ping 69.56.238.122
Pinging 69.56.238.122 with 32 bytes of data:
Reply from 69.56.238.122: bytes=32 time=12ms TTL=56
Reply from 69.56.238.122: bytes=32 time=12ms TTL=56
Reply from 69.56.238.122: bytes=32 time=13ms TTL=56
Reply from 69.56.238.122: bytes=32 time=12ms TTL=56
Ping statistics for 69.56.238.122:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 13ms, Average = 12ms
U:\>ping 63.247.94.13
Pinging 63.247.94.13 with 32 bytes of data:
Reply from 63.247.94.13: bytes=32 time=48ms TTL=239
Reply from 63.247.94.13: bytes=32 time=48ms TTL=239
Reply from 63.247.94.13: bytes=32 time=48ms TTL=239
Reply from 63.247.94.13: bytes=32 time=48ms TTL=239
Ping statistics for 63.247.94.13:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 48ms, Maximum = 48ms, Average = 48ms
U:\>
Only thing worse than failure is not trying
Somehow, I suspect that this won't come as much of a surprise:
I:\Documents and Settings\byrdie>ping 69.56.238.122
Pinging 69.56.238.122 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 69.56.238.122:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
I:\Documents and Settings\byrdie>ping 63.247.94.13
Pinging 63.247.94.13 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 63.247.94.13:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
I:\Documents and Settings\byrdie>
"Uncertain emotions force an ... uncertain smile." - The The
what the hell...you're on the forum but you can't ping a server in either datacenter...you're ISP must block ICMP
Or, it simply didn't occur to me that being behind a household firewall would affect pinging. whoops. Maybe I'm not really a computer person. I assumed that knowing what "ping" meant helped me rate. Heck, I just figured that by the time I saw your request, you'd pulled the sites down for maintainence ... which would be interesting as I'd been logged on shortly thereafter. :tinker:Originally posted by SaintHax@Sep 30 2004, 09:59 PM
what the hell...you're on the forum but you can't ping a server in either datacenter...you're ISP must block ICMP
*cough*
The resident computer guru provided me with the following from his much more useful session:Hope this helps, late though it is.
- $ uname -a
Linux www.llamacom.com 2.4.21-15.0.2.EL #1 Wed Jun 16 23:12:30 EDT 2004 i686 i686 i386 GNU/Linux
$ ping 69.56.238.122
PING 69.56.238.122 (69.56.238.122) 56(84) bytes of data.
64 bytes from 69.56.238.122: icmp_seq=0 ttl=54 time=56.0 ms
64 bytes from 69.56.238.122: icmp_seq=1 ttl=54 time=57.9 ms
64 bytes from 69.56.238.122: icmp_seq=2 ttl=54 time=55.4 ms
64 bytes from 69.56.238.122: icmp_seq=3 ttl=54 time=56.1 ms
64 bytes from 69.56.238.122: icmp_seq=4 ttl=54 time=71.9 ms
64 bytes from 69.56.238.122: icmp_seq=5 ttl=54 time=74.8 ms
64 bytes from 69.56.238.122: icmp_seq=6 ttl=54 time=55.5 ms
--- 69.56.238.122 ping statistics ---
7 packets transmitted, 7 received, 0% packet loss, time 6057ms
rtt min/avg/max/mdev = 55.424/61.118/74.832/7.825 ms, pipe 2
$ ping 63.247.94.13
PING 63.247.94.13 (63.247.94.13) 56(84) bytes of data.
64 bytes from 63.247.94.13: icmp_seq=0 ttl=245 time=61.5 ms
64 bytes from 63.247.94.13: icmp_seq=1 ttl=245 time=66.1 ms
64 bytes from 63.247.94.13: icmp_seq=2 ttl=245 time=60.7 ms
64 bytes from 63.247.94.13: icmp_seq=3 ttl=245 time=61.2 ms
64 bytes from 63.247.94.13: icmp_seq=4 ttl=245 time=59.5 ms
--- 63.247.94.13 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4040ms
rtt min/avg/max/mdev = 59.574/61.854/66.179/2.268 ms, pipe 2
"Uncertain emotions force an ... uncertain smile." - The The