you can ping a site and tracert it ..

[bypass]

how is it that you can ping a site and tracert it but it does not show up in your browser?

[eHostSpace]

If you are in Windows platform,

Start --> Run --> " ping [IP or Domain Name] "
Start --> Run --> " tracert [IP or Domain Name] "

[HarborNetworks]

Thats a very good question. I have seen it where I have done a nslookup on my machine and it have the correct IP, but still not load in the browser. I'm really not sure what causes this strange problem. I have seen where only my system can't access a page, while everyone else can. My system is resolving the correct ip but it just doesn't seem to want to load. THen at the same time I have had the problem where I can't resolve the ip of the site and can't load it while others cant. My guess is it's a problem with the route to that system temporarily. Anyone else notice this?

I do know that one time I had this problem, but it was because I spelled the domain wrong in the httpd.conf file .

[trifexx]

Maybe because the HTTP server is/was currently down?
Or they had masquerading IPs and port 80 was forwarded to the wrong or currently unavailable machine?
There are a lot of reasons why this would happen

[matt2kjones]

all a ping does is send a few packets of data to a server, which sends it back

if you get a reply, u know the server responded.

if u ping a domain name, it simple shows that the domain resolves to an ip, then, the ip is sent packets which are then returned.

Ping does not show you that the webserver is working, or ftp server, etc etc, it just mearly shows that it replies to the packets sent using a ping

[northwind]

Well, its already been said but its most probably that the web server (Probably Apache for Linux Users) crashed, or is being rebooted.

Usually it shouldn't take long to be booted back up.