Mozilla Unable to connect to only 1 website

[DeFy]

Alright so I can connect to this and every other website fine, EXCEPT www.i-Zombie.net, which I need to connect to frequently because I'm the web developer on that site. I am able to connect every morning when I first log on to my PC for about 5 minutes, then it randomly comes up with the same error from that point until the next time 24 hours later where I'm allowed access for another 5 minutes. The error is: "The server at www.i-zombie.net is taking too long to respond." I've browsed the Mozilla Support Forums, cleared my Cache and Cookies, turned off my firewalls and AV software, allowed Firefox through all my firewalls, turned off http pipelining in my Firefox config, etc. I really have no idea what to do. This is even odder because I can connect for a few minutes, but then just randomly lose the ability to connect, and i contacted my host and they said that my IP was not on the blocked list so I am completely lost right now :facewall:.

 

[chapp]

Have you tried it in IE?

Try booting into safemode with networking and see if it still happens. If it doesn't, then you know its some 3rd party software causing the problem. If it works in safe mode, run msconfig and uncheck everything in the "startup" tab and reboot and try it again, if it works, then start checking one by one in the startup list until the issue happens again.

Also found this:

I often had issues with a certain site where I would always get the
"the server is taking too long to respond" problem. After searching the net for ages I couldn't find a solution that helped me.
I thought I would try to ping the website in question and I did receive all packages back but the response time was well over 100ms. It was actually closer to 150ms.
I thought there might be some timeout parameters in firefox so i took a look in about:config
I know the dangers if you mess about too much in there but I just wanted to take a look.
I typed in timeout and found a number of timeout paramaters and one jumped right out at me...

browser.urlbar.search.timeout

The value of this parameter was only 100, which is 100ms.
Since the ping test of the website I wanted to visited gave 150ms I decided to increase the value of browser.urlbar.search.timeout

I gave it a value of 250ms and until this day I have had no trouble with the website not loading.

Might not be the case for you, but it helped me so maybe its worth a shot
-------------------------------------------

Of course, there's always the possiblity that the site is having problems as well. And since you're the web dev, you should be able to fix it.

 

[DeFy]

K i tried in Opera and IE, still nothing.

Why can I connect for about 5 minutes and then just drop? That doesn't make sense...

I can also connect through proxies fine.
And I've traced the route to the server from my cmd, and nothing is above 60ms

 

[chapp]

Try the safe mode troubleshooting I posted.

 

[DeFy]

Alright booted into safe mode with networking, still get the same error.

 

[chapp]

If you have the problem with multiple browsers WHILE in safe mode... then the issue is with your site...

 

[DeFy]

Well I contacted support on the host and they said apparently it's a problem with my ISP blocking the site, which makes no sense because they've never done that before...

 

[Ric]

Sounds like a DNS resolve issue.

Call your ISP and tell them you're not getting the service you're paying for.

 

[DeFy]

Any ways to fix that on my end? What is my ISP gonna do to help this problem...

 

[chapp]

Contact your ISP tech support and pray you get a cool person who will escalate the ticket to a higher tier support dept and explain the issue to them.

 

[KMod]

Long shot, but have you tried power cycling your router/modem?

 

[iWhiskey]

Try using a different DNS.

Google's DNS servers are:

8.8.8.8
8.8.4.4

You will need to change this on your router/modem (if applicable) and on your operating system.