why does pinging foreign websites time out even though the website appears quickly? (timeout secs = 30)?
552679
Many servers have ping turned off in order to prevent DoS (Denial of Service) attacks.  Servers can be configured to not respond to ping requests. I get the same results that you do:\n\nping www.australia.gov.au\nPING www.australia.gov.au (210.50.147.98) 56(84) bytes of data.\n\n--- www.australia.gov.au ping statistics ---\n5 packets transmitted, 0 received, 100% packet loss, time 3999ms\n\n\nThe port that ping works on (port 7, echo) is not required for web traffic (port 80/443 for SSL).\n\nOn a linux system, this is accomplished with IPtable rules and you can reject or even drop packets based on routing rules.
668441
Its something to do with the proxy server. you have to get rid of it. for it to work.
468308
Tools---> Internet options ---> Clear History, cookies, and and delete files.  This is going to cause pages on the internet to load up slower, but that pesky website won't come up again.
818221
download mozilla firefox from www.firefox.com or www.download.com it will fix the problem for sure. If it doesnt then it  must be your internet connection blocking the website from being accessed.
1028495
it's  'server overload.'\n\nwait awhile and get back on-normally works fine.
1039496
If you are in a Windows operating system do the following.\n\nstart -> run -> cmd -> enter -> tracert -> type the domain name -> enter\n\nit'll then try to find the fastest route to the server. if it encounters and unusually long pings along the way then that tells you the problem is not with your server. If it timesout at your server though then... well it is your server.
605108
This problem could be due to one of two sources:\n\n1)The Yahoo! server is malfunctioning in some way.\n\n2)There may currently be a large number of people connected to your ISP, and this may slow down or distort your viewing of web pages, especially if you have a 56k connection.\n\nThe first cause is the more likely source though.
553538
Maybe the DHCP provided (if you get your DNS from DHCP) DNS Servers are not responding in time. I had my ISP change the primary and secondary DNS servers and my connection when to crap.  Through the VPN, you're probably using your company's DSN servers.\n\nCheck to make sure your primary and secondary DSN server respond.\n\nIn windows, open a command shell. Type "nslookup yahoo.com" and see if you get a response.
254630
Maybe you weren't connected to the internet at the time. Maybe the site was down for a few moments. Maybe the connection timed out. Maybe you accidentally misspelled the URL. Maybe a lot of things.\n\nAt the time of this writing, the site works fine for me, so keep trying! ; )
62448
one of the following ...\n1. may be the site itself is down.\n2. you have a firewall on your internet\n3. Try a different browser ( like firefox )
465217
Just because you can PING an IP address doesn't mean that there's a web server behind that address. There are plenty of addresses that will respond to PING but will not serve web pages.
403488
Your servlet could not establish a connection because it timed out.
920965
there is nothing you can do, it's a problem with the web server of the website not your computer. it could just be that the server is receiving too much traffic and can't cope.\n\ntry again later.
94219
Discrepancies in security settings can cause this.  If one computer has a firewall it may be preventing access to a certain site.  Same goes with differences in browser settings, anti-virus, etc.
277245
Hi, your school is likely using a proxy. This proxy is not allowing enough time for the page to get served.\n\nSee link below and then check your error log for similar entries.
966333
do you mean the disconnection timeout? if you do it right click your dialup icon / click properties / select options /  have a look at your redialling options.
963015
C:&#92;>ping yahoo.com  <--what you are pinging\n\nPinging yahoo.com [216.109.112.135] with 32 bytes of data: <--the address was found at 216.109.112.135, now let's start pinging\n\nReply from 216.109.112.135: bytes=32 time=17ms TTL=45  <--The website replied from that IP address.  You sent the site 32bytes of data to test with.  The reply took 17ms (milliseconds) to get back to you.  TTL isn't important here.\nReply from 216.109.112.135: bytes=32 time=18ms TTL=45\nReply from 216.109.112.135: bytes=32 time=19ms TTL=45\nReply from 216.109.112.135: bytes=32 time=18ms TTL=45\n\nPing statistics for 216.109.112.135:\n    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),  <-- you sent 4 packets and all were answered successfully.\nApproximate round trip times in milli-seconds:\n    Minimum = 17ms, Maximum = 19ms, Average = 18ms  <---self explanatory.\n\nIf you want to ping a site "forever", use:  ping whatever.com -t\n\n...where whatever.com is the real site you want to ping.