Pinging Servers Checking the webhosts speed

The instruction's below were tested on Windows XP only.

1) Click on the "Start Menu" then click on "Run".

2) Type "command" (without quotes) into the run box and click OK.

3) Wait for text to appear on the screen.

4) Type "ping" (without quotes) followed by a space and the web host's domain.

Example: "ping http://forums.xisto.com/;(without quotes)

5) Wait for text to finish appearing on the screen.

6) The text on the screen should look something like this:

Ping  geocities.com/ [66.218.77.68] with 32 bytes of data:

 

Reply from 66.218.77.68: bytes=32 time=79ms

Reply from 66.218.77.68: bytes=32 time=78ms

Reply from 66.218.77.68: bytes=32 time=78ms

Reply from 66.218.77.68: bytes=32 time=78ms

Reply from 66.218.77.68: bytes=32 time=78ms

Reply from 66.218.77.68: bytes=32 time=78ms

 

Ping statistics for 66.218.77.68:

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

Approximate round trip times in milli-seconds:

Minimum = 78ms, Maximum = 79ms, Average = 78ms

 

The thing that we are intrested in is the very last number (shown in bold above). That number shows the average number of milliseconds it took the host to respond to your computers ping request.

Note 1: Note that the response time is not limited to server's connection, but the Internet itself, and and user's connection.

Note 2: The ping request works for checking the speed of all websitesm not just web hosts.

Nice it works

Wow this actually worked .. Awesome tutorial which even works on my crapy computer too.. But I have only one small question what means all thous IP and byte sizes which showes up? .. Im not very smart in such things.. GooD JoB by the way uiop.. Kepp the tutorials coming

of course it will work on a crappy computer. this uses ms dos. i mainly use this to test if my connection is working, or if my ISP is down.

There are some neat useful options that come with "ping", for example, try this command:

ping http://forums.xisto.com/ -w 5000 -t -l 65500

This command pings http://forums.xisto.com/, the "-w" attribute (followed by 5000) tells the program to wait 5 seconds (5x1000 milliseconds = 5000 milliseconds = 5 seconds) between each ping and the "-l" attribute (followed by 65500) tells the program to use a specified buffer size, in this case, it is 65500 bytes (that's pretty much large), you can call that a "heavy duty" ping. And finally, the "-t" attribute makes the program ping the specified address until you stop it manually.

If you would like to do a more advanced ping, try "tracert"! Type it in your CMD prompt and you will see through what servers does your little package go!

Example:
tracert http://forums.xisto.com/

Result:

Tracing route to Xisto.com [64.27.18.99]over a maximum of 30 hops:  1    29 ms   174 ms   111 ms  62.108.98.153  2   126 ms    20 ms    51 ms  core-l3.vline.verat.net [62.108.96.66]  3   107 ms    24 ms    18 ms  213-163-36-57.vnet.hu [213.163.36.57]  4   636 ms   169 ms   212 ms  fe2-5-bors-gsr0.vivendi-th.net [213.163.53.245]  5    84 ms    31 ms    20 ms  fe2-5-bors-gsr0.vivendi-th.net [213.163.53.245]  6   157 ms   101 ms    67 ms  80.120.176.249  7   132 ms    34 ms    96 ms  IIX2-WARSSW01.highway.telekom.at [195.3.70.164] 8   146 ms    93 ms    94 ms  212.73.202.1 9   274 ms   124 ms   146 ms  4.68.124.185 10   252 ms   190 ms   226 ms  ae-0-0.bbr2.LosAngeles1.Level3.net [64.159.1.126] 11   229 ms   222 ms   247 ms  ae-12-55.car2.LosAngeles1.Level3.net [4.68.102.141] 12   200 ms  1040 ms   479 ms  unknown.Level3.net [63.209.82.190] 13   337 ms   594 ms   730 ms  64.27.18.99Trace complete.

you can pull down old servers like that. and if you get tons of people to do it at once, you can take down people's networks...i also don't recommend you do that or you'll have a call from your ISP and the FBI knocking at your door

LOL!That's just plain WRONG, and you can't "kill" a server like that! You can only choke up it's connection to the internet, and that's still a maybe (first condition: a xxx MBps connection).Such attacks are called DoS (denial of service) attacks and attacks from multiple computers are called DDoS attacks (distributed denial of service attacks). If you intentionally use them, then there is a **SMALL** chance that you will get in trouble. Anyway, if you ping a server like you're crazy (with large packets), you will probably be warned first. And if you are dumb enough not to stop, then you will (again: maybe) get into trouble. This is the worst case scenario... But, when you ping a server, you BARELY do anything to it! If you open a web site hosted by that server, you will do more "damage" to it then pinging it!!! After all, servers were made to serve, right? Besides, if the server feels that you are pinging it too much, it can simply ban your IP address, and... end of story.So, feel free to use ?ping?, FBI doesn't care !

oh yeah, thats a great manual ^^...I can ping any IP with this system?Thanks all..Cpuser

Yea, I know a person who made a program that did this in VB class at school, and he took down the web server because it pinged a infinate amount of times. Fortunately, he was friends with the District Tech Coordinator, so he didn't get in trouble.

Yes man i know about this. If we ping we can easily know the server host ip address and it also shows how fast is your conn, this can only observed by ISP or else a well know person of networking sort. I always ping my server from my computer to maintain the conn. at its full speed instead of landing up in slow speed, try this if u want to know the servers are active or not. Good luck..!!!

Wow, thnx a lo. Nice tutorial. BTW that meens that this is very fast Host? not Xisto but home.lv (code down). Cus here are 17 ms but for trap it was much more...

Microsoft(R) Windows DOS(C)Copyright Microsoft Corp 1990-2001.
C:\DOCUME~1\TEST>ping home.lv/
Pinging home.lv/ [159.148.223.232] with 32 bytes of data:
Reply from 159.148.223.232: bytes=32 time=28ms TTL=247
Reply from 159.148.223.232: bytes=32 time=18ms TTL=247
Reply from 159.148.223.232: bytes=32 time=14ms TTL=247
Reply from 159.148.223.232: bytes=32 time=11ms TTL=247
Ping statistics for 159.148.223.232:	
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:	
Minimum = 11ms, Maximum = 28ms, Average = 17ms


C:\DOCUME~1\TEST>

Edited September 24, 2016 by OpaQue (see edit history)

My ISP blocks ping requests greater than 520 bytes.

Wow, thnx a lo. Nice tutorial. BTW that meens that this is very fast Host? not Xisto but home.lv (code down). Cus here are 17 ms but for trap it was much more...

Microsoft(R) Windows DOS(C)Copyright Microsoft Corp 1990-2001.C:\DOCUME~1\TEST>ping https://items.lv 
Pinging https://items.lv 
 [159.148.223.232] with 32 bytes of data:Reply from 159.148.223.232: bytes=32 time=28ms TTL=247Reply from 159.148.223.232: bytes=32 time=18ms TTL=247Reply from 159.148.223.232: bytes=32 time=14ms TTL=247Reply from 159.148.223.232: bytes=32 time=11ms TTL=247Ping statistics for 159.148.223.232:	Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds:	Minimum = 11ms, Maximum = 28ms, Average = 17msC:\DOCUME~1\TEST>

A 17ms ping time is usually considered pretty good. Most free webhosts have 40ms and greater ping times. Also, keep in mind that all ping times are subject to a large number of variables (see my original post). What ping time did you get for Xisto?

The host took 249ms to repond to me. If anyone is interest the following site contains a lot of web based tools like these ones -

http://home01.wxs.nl/~houwe135/wbnt1/index-exp.htm

with the explaination of what they are and what they do.

Edited June 23, 2006 by tonyused (see edit history)

I knew about this a while ago.You can ping a server or an IP addresss.On Windows XP computers, type cmd in the Run box instead of command.You should use ping packets too big.Pinging home computers can cause them to bounce your "attack".