yes its in the average range :)
yes it is an external command.
Ping command is used to check the network connectivity. You can use ping command from windows shell only, not from DOS OS as DOS does not supports networking. You can use "-t" switch with ping for continuously network checking.Syntax: Ping Example: ping 192.168.1.15 or ping 192.168.1.15 -t or ping -t 192.168.1.15
If ping is reporting large numbers on a ping request it generally means the network is congested or there are bad connections between some of the routers in the route.
A ping is like your connection bars on the scoreboard, if you have a four bar connection you have full "ping". It is more used on the PC than consoles. A ping is the amount of time it takes for data to travel to a server, and to get back to you, this varies on many different internet connections, here are some: ms = milliseconds * Cable (20+ms) * DSL (50-200ms) * Dial up (500+ms) * Satellite (690-1200+ms) * EVDO/3G/CDMA (100+) But really most of the time it just depends on your speed. These are just average pings. If only the "bars" were numerical.
It is the effect caused by the MS to wildly switch links with either BS when the MS is exactly between the two BSs. pk.thapa66@gmail.com
A Ping is a command which can be executed form a command prompt on a windows linux or unix machine which tests network connectivity. It uses the format: PING (IP address) e.g. ping 192.168.0.1 On a windows machine three attempts are sent to the target IP address and each attempt is timed and displayed in milliseconds. A low ping is a subjective estimate of this "round trip time" (RTT) time. The smaller the number the faster the computer being "pinged" is responding. A very small ping time is described as a low ping, a longer delay would be a high ping time. All of the times described by the term "Low ping" is subjective and defined by experience, but as a guide a ping time of less than 100 mS would be considered a low ping time and one of 250 mS or more would be considered high.
This "ms" is only used for your ping. It stand for milliseconds. Say if you where to have 100ms connection to a server that would mean that it takes 0.100 seconds to send information to the server and for it to return it.
When you "ping" something you test the time it takes, usually in ms, to reach another computer or router, and for that data to come back. So if you were to "ping" google.com, you would get the length of time it takes to teach them and come back. This is useful in testing connection latency, if you have a connection at all, or if a website/computer is down.
It depends if you can communicate with the distant end or not. Successful pings will look like this: lap:~$ ping google.com PING google.com (66.102.7.99) 56(84) bytes of data. 64 bytes from lax04s01-in-f99.1e100.net (66.102.7.99): icmp_seq=1 ttl=50 time=65.7 ms 64 bytes from lax04s01-in-f99.1e100.net (66.102.7.99): icmp_seq=2 ttl=50 time=62.2 ms 64 bytes from lax04s01-in-f99.1e100.net (66.102.7.99): icmp_seq=3 ttl=50 time=66.4 ms 64 bytes from lax04s01-in-f99.1e100.net (66.102.7.99): icmp_seq=4 ttl=50 time=64.5 ms ^C --- google.com ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3003ms rtt min/avg/max/mdev = 62.262/64.749/66.417/1.586 ms Unsuccessful ping attempts will look like this: lap:~$ ping 192.168.1.244 PING 192.168.1.244 (192.168.1.244) 56(84) bytes of data. From 192.168.1.147 icmp_seq=1 Destination Host Unreachable From 192.168.1.147 icmp_seq=2 Destination Host Unreachable From 192.168.1.147 icmp_seq=3 Destination Host Unreachable ^C --- 192.168.1.244 ping statistics --- 6 packets transmitted, 0 received, +3 errors, 100% packet loss, time 5020ms , pipe 3
From the command line prompt, type "PING 127.0.0.1" (current IP address) and press ENTER From the commFrom the command line prompt, type "PING 127.0.0.1" (current IP address) and press ENTER and line prompt, type "PING 127.0.0.1" (current IP address) and press ENTER
See the Clear Ping and Road Runner Ping from below. I have both currently and was able to plug in and test both on the same comp within a minute of each other. However Road Runner Seems to vary between awesome and absolute crap. I have seen Road Runner be as bad as 200+ ping times reliably for days. Then some time later it magically fixes itself and no I do not torrent. I have had technicians out to my home 8 separate times. If I wasn't a hardcore gamer I would definitely choose clear over road runner. Clear vs Road Runner CLEAR (from underneath the tower) over a maximum of 30 hops: 1 1 ms 1 ms 1 ms 192.168.2.1 2 2 ms 1 ms 1 ms 3 71 ms 94 ms 99 ms 4 88 ms 88 ms 90 ms 5 86 ms 95 ms 94 ms 66.192.62.1 6 65 ms 94 ms 99 ms 66.192.249.222 7 126 ms 99 ms 99 ms 66.109.6.176 8 79 ms 109 ms 104 ms 66.109.6.33 9 93 ms 100 ms 93 ms 66.109.10.76 10 93 ms 110 ms 56 ms 66.109.6.125 11 96 ms 89 ms 111 ms 24.30.192.206 12 89 ms 104 ms 105 ms 24.28.199.168 Trace complete. over a maximum of 30 hops: 1 4 ms 1 ms 1 ms 192.168.2.1 2 1 ms 1 ms 2 ms 3 65 ms 79 ms 45 ms 4 76 ms * 40 ms 71.22.7.161 5 * 43 ms 84 ms 66.192.62.1 6 45 ms 94 ms 110 ms 66.192.249.222 7 104 ms 106 ms 137 ms 66.109.6.176 8 108 ms 138 ms 90 ms 66.109.6.33 9 114 ms 93 ms 134 ms 66.109.10.76 10 127 ms * 188 ms 66.109.6.125 11 100 ms 104 ms 102 ms 24.30.192.206 12 58 ms 100 ms 63 ms 24.28.199.168 Trace complete. ROAD RUNNER over a maximum of 30 hops: 1 51 ms 1 ms 1 ms 192.168.2.1 2 11 ms 8 ms 17 ms 3 9 ms 10 ms 17 ms 4 13 ms 10 ms 9 ms 24.28.224.171 5 20 ms 31 ms 18 ms 24.93.64.178 6 30 ms 22 ms 24 ms 66.109.6.80 7 26 ms 21 ms 32 ms 66.109.10.76 8 26 ms 19 ms 30 ms 66.109.6.125 9 20 ms 21 ms 20 ms 24.30.192.206 10 30 ms 21 ms 19 ms 24.28.199.168 Trace complete. over a maximum of 30 hops: 1 1 ms 1 ms 1 ms 2 19 ms 7 ms 7 ms 3 13 ms 25 ms 7 ms 4 14 ms 14 ms 222 ms 24.28.224.171 5 15 ms 15 ms 12 ms 24.93.64.178 6 20 ms 21 ms 33 ms 66.109.6.80 7 30 ms 35 ms 22 ms 66.109.10.76 8 25 ms 19 ms 21 ms 66.109.6.125 9 30 ms 26 ms 21 ms 24.30.192.206 10 22 ms 22 ms 34 ms 24.28.199.168