| 1:53 pm on Jun 4, 2010 (gmt 0)|
If you open a command prompt on your computer, you can try the command ping www.example.com where www.example.com is replaced by your website name. If there is a response, there is a connection possible between your computer and the server with your website running on it. Sometimes a firewall between your computer and server blocks ping requests, so the absence of a response is no indication yet that the communication is blocked. Look at the IP address which the ping command uses. This IP address should match the IP address used by your webserver. If you see a different IP address than you expect, a DNS configuration problem may exist.
The second step is to use tracert www.example.com to see the path the packets are travelling between your computer and the website server. The tracert command displays a list of router hops between your computer and the webserver. As with ping these requests may be blocked by firewalls somewhere halfway.
The third step is to use telnet www.example.com 80 to see if your site is responding on port 80. The telnet command is not installed by default on newer Windows installations, so this command may not be available to you. With the above parameters, telnet tries to connect directly with the HTTP port of your webserver. If the connection times out, somewhere between your computer and the webserver the traffic is blocked. If you get a connection within a few seconds, the server is reachable and the problem is probably not at your ISP but somewhere in the webserver or on your local computer.
| 6:03 pm on Jun 4, 2010 (gmt 0)|
Step one: reboot any routers or modems connecting you to the Internet. Step two: lammert's suggestions.
| 10:47 am on Jun 5, 2010 (gmt 0)|
Is it the only site not showing? What kind of error message do you get? Anything in the log files of your computer? Do you have more computers in your network, a laptop maybe and does it show on those?
Is your local hosts file changed somehow? This file translates the hostname (www.example.com) to a real ip number and is used before any DNS query.
| 11:56 am on Jun 5, 2010 (gmt 0)|
The problem happened with every computer I tried in my local network no matter the router's IP because I have dynamic IP and did a router restart several times. However, if I tried with another internet connection and the same computers, then I could see the website.
Anyways, the problem got solved next day but I did not have to do anything to solve it.
According to my hosting provider it might be related to a ban by my internet provider after having get the 2000 limit of accesses into the website in less than 24 hours. Would that make sense?
Thanks for your suggestions.
| 12:33 pm on Jun 5, 2010 (gmt 0)|
You have two connections with different isp companies?
| 1:51 pm on Jun 5, 2010 (gmt 0)|
| 2:08 pm on Jun 5, 2010 (gmt 0)|
The website you are accessing is located on one of those isps? Is it possible you consumed your bandwidth for a 24 hr period? Scratching head... if the router wasn't the problem then I'm not sure (other than a short time blacklist) what might be the problem!
| 2:51 pm on Jun 5, 2010 (gmt 0)|
Is it possible you consumed your bandwidth for a 24 hr period?
I do not think I have that kind of bandwith limit set by the website host for a 24 hours period. I might have been banned though by the ISP for accessing too many times in 24 hours to the same URL.
| 3:00 pm on Jun 5, 2010 (gmt 0)|
I am not aware of ISPs banning users from visiting a site more than a fixed number of times per day. If my ISP would have implemented it I would have been banned from WebmasterWorld long ago. If you think something like that happened, contacting your ISP and asking for an explanation would be the first thing to do.
| 3:24 pm on Jun 5, 2010 (gmt 0)|
I would not have thought that either. It is just that I was told that by the hosting provider. And after that, the explanation seemed to make sense. So I wrote an email to my ISP but they have not replied yet.
| 4:45 pm on Jun 5, 2010 (gmt 0)|
What did ping and tracert give you?
| 10:12 am on Jun 6, 2010 (gmt 0)|
What I remember,
ping did work just a few times, whiles tracert gave something that I do not remember.
I know there were 18 lines or so and the last few lines were just filled with dots.
| 7:05 pm on Jun 6, 2010 (gmt 0)|
|...I know there were 18 lines or so and the last few lines were just filled with dots. |
Okay . . . you might want to run it again and pay a little closer attention. :-) Those last dots? They mean your request is going through several servers and routers, then getting to one and stopping or timing out.
What you should get is a final connection and tracert exits. The dots mean for whatever reason, your request is getting to some device, most likely a router, and waiting . . . and waiting . . . . and waiting.
I have had this before, my request was getting right up to the router **just before** the target server and timing out. I could only find this out by working with a wise admin who was doing the same thing and we compared the last steps of our "route to the server."
Which may open one more question: is this a satellite connection? Mine was absolutely aweful and often had these types of problems because it's a proxy connection.
The problem is going to be some router or firewall configuration that you may or may not be able to fix on your end, sorry I can't point you to the fix-it button . . . there isn't one, if it's a similar problem.
| 10:42 pm on Jun 6, 2010 (gmt 0)|
Thanks, anyways, the problem got solved. I guess it had to do with the 24 hours bandwith limit because I did not have to do anything to get it solved.