Well, the "
no access for 5 minutes"
thing sounds like Windows (you are using Windows, I assume?) caching a negative DNS request for the site (which would cause such symptoms, and 5 minutes is the Windows default time-to-live for such negative DNS responses), wherever that is coming from.
If that's really the case you should be able to immediately unhork this by running "
ipconfig /flushdns"
on the command line. Of course you'll then still have to figure out where that bogus DNS response is coming from ("
ipconfig /displaydns"
might help), but if you need a workaround it'll probably help to add the IP address of the site to your hosts file (i.e. "
C:\WINDOWS\system32\Drivers\etc\hosts"
) to make sure it always resolves to where it should...
Just a guess, though - then again, you shouldn't be able to ping the site either if the DNS entry is horked. Another cause could be if your provider has some kind of transparent proxy crap going on...
Of course Wireshark should be able to help pinpoint the problem, just make sure you run it before trying to connect to the site for the first time. Right-clicking on an entry and choosing "
Follow TCP stream"
is very useful in following an HTTP request, but make sure to clear the filter this sets afterwards or you'll be wondering where the rest of the capture went...
np: Cage - I Never Knew You (I Never Knew You)
____________________________
"
I'm not anti-anything, I'm anti-everything, it fits better."
- Sole
R.I.P. Robert Feldhoff (1962-2009)
[Last edited by Briareos at 11-25-2009 01:59 PM]