Menu
I'm on the World Wide Web right now, as evidenced by posting on StackOverflow. However, if I try to ping stackoverflow.com from the command line, the ping times out. What do I need to do for ping to work?
> ping stackoverflow.com
Pinging stackoverflow.com [198.252.206.140] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 198.252.206.140:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
tracert
> tracert stackoverflow.com
Tracing route to stackoverflow.com [198.252.206.140] over a maximum of 30 hops:
1 * * * Request timed out.
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
...
Trace complete.
It's Request timed out. all the way to 30 hops.
ping google.com
Same result. :-)
947
In most cases, a "Request Timed Out" message is caused by a firewall blocking the connectivity. Before you can ping, you'll need to ensure that the target machine has a green status indicator. If this is not the case, search our knowledge base for the color indicator you see (i.e., yellow, cyan, etc).
If you can ping a host but not open it in a browser, then I suspect that your browser settings have been compromised. Check for any proxy settings that may have been configured by malware. Furthermore, try using a different browser.
-w timeout Specifying a timeout value when executing the ping command adjusts the amount of time, in milliseconds, that ping waits for each reply. If you don't use the -w option, the default timeout value of 4000 is used, which is 4 seconds.
You need to ensure that you have internet access and you are not stopped by any firewall or some other security feature from accessing that site. It may also be if you have pinged a wrong IP or if the address is not being resolved by your DNS. 2. The pinged site is not responding to your requests.
Some hosts have a firewall that block the ICMP (http://ca.wikipedia.org/wiki/Internet_Control_Message_Protocol) packets like ping. You can use traceroute (cmd line tool or online webs like http://ping.eu/traceroute/) or tcptraceroute (http://linux.die.net/man/1/tcptraceroute).
Some routers also have a firewall that block ICMP. You can detect this by doing ping google.com. It that fails, then it's your local router that's problematic not the remote host.
hope it can help you
169
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
