Ping request timeout, although the web browser runs on the same computer

I am currently on the World Wide Web, as evidenced by the publication on StackOverflow. However, if I try to ping stackoverflow.com from the command line, ping will time out. What do I need 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), 

Edit, try 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. 

He Request timed out. fully up to 30 jumps.

Edit, try ping google.com

Same result. :-)

+5
source share
1 answer

Some hosts have an ICMP blocking firewall ( http://ca.wikipedia.org/wiki/Internet_Control_Message_Protocol ), such as ping. You can use traceroute (cmd command-line tool or online networks like http://ping.eu/traceroute/ ) or tcptraceroute ( http://linux.die.net/man/1/tcptraceroute ).

Some routers also have a firewall that blocks ICMP. You can discover this by doing ping google.com . This fails, then this is your local router, which is problematic for the non-remote host.

hope this helps you

+3
source

All Articles