| 9:13 am on Aug 7, 2010 (gmt 0)|
next time you experience this situation you should try a traceroute. (tracert on windows/dos)
| 5:07 pm on Aug 7, 2010 (gmt 0)|
Does this particular provider have a ddos filter on the server?
I've accidentally gotten myself banned from my own server, and that ended up being the culprit. Somehow, I clicked too fast and the server interpreted that as a threat for some reason.
If this is the case, whitelist your IP to prevent it from happening again.
| 7:04 pm on Aug 7, 2010 (gmt 0)|
My first stop is always Internet Destroyer. I have this problem on and off to this day with IE, and always have. It comes and goes. Something to do with corrupted TCP/IP DLL's used by IE. Do you have problems in FireFox as well? If so, yes, it's something in your connection.
| 8:24 pm on Aug 7, 2010 (gmt 0)|
Sometimes we shoot ourselves in the foot checking this, checking that, checking it too freakin' often in hopes of better this than last that...
I suspect fully 1/4 of all internet packet traffic these days is webmasters hoping for better results and one/half as se's and minions making dang sure site is there (under guise of "human" visitor) and the other half (yeah, I know my math is off) being, for the most part, human...
As to OP, does this occur in one browser only? Do others work? Does it come back after a restart (reboot)? Sometimes the problem is the desktop...
| 4:38 am on Aug 8, 2010 (gmt 0)|
Thanks for your help.
I tried a tracert, although I'm not sure what this tells me. It shows the route, then times out.
>>Does this particular provider have a ddos filter on the server
How would I tell?
Yes, I have problems on all browsers.
It doesn't necessarily come back after a re-boot. There doesn't appear to be any pattern to it.
| 6:51 am on Aug 8, 2010 (gmt 0)|
feeder, you need to look at the tracert output for each network hop your request makes, indicated by ip address. the ip where your packet times out may be where your problem lies.
| 6:13 pm on Aug 8, 2010 (gmt 0)|
|It shows the route, then times out. |
I have had this. My scenario was this: someone had a dedicated server hosted behind a roadrunner connection. My admin, using a different backbone, could get to the site fine, I could not. We both ran tracerts, his showed a specific path, mine always timed out at the point just before the server. The problem, then was there was "something up" with that router.
We reported it to support and they said "no problems" but as is often the case, after we complained it went away and never came back. Which tells us they did something, don't know what.
So see if you can get someone to run a parallel tracert from elsewhere, see if that tells you anything.
| 1:19 pm on Aug 10, 2010 (gmt 0)|
we had the same problem a few years ago, it went on for months and in the end we dropped the DNS server used by hosting firm and went with one outside the UK and have never had a problem since
| 3:18 pm on Aug 10, 2010 (gmt 0)|
Sometimes the simplest things can fix the issue- try rebooting your computer. If you have a cable/DSL router, reboot that as well.