2
I have a problem with some web sites where the first time I hit the site, the web browser says "connecting" and then it will time out. If I hit the site again, it will load just fine. If I browse around the site, it will work fine as long as I keep browsing, but if I wait a while, it will time out again. Qwest was no help with this - they sent me a new modem, which made no difference. Most sites work fine, but one of my favorite sites doesn't - it is a forum site, so I often will type a message and then have the site time out... seems like it only stays alive for a minute or so, and then my computer loses track of it.
I'm using Vista Home Premium, Qwest DSL with Actiontec PK5000. This problem also happens on my two XP Pro machines. It is completely repeatable with the sites listed below... all I have to do is wait one minute, then the site will time out again. If I hit the site on one computer, it will come back to life on all the machines in the house - two are on direct connections to the modem and one is on wireless. I have tried Firefox, IE, and Chrome. The problem is not browser related, computer related, or modem related - it has to be something in the network. Please help! So I can call Qwest and tell them what this is.
EDIT: tried the Google DNS and it didn't work
Try Wireshark. It tells you everything that happens on your network. It is a lot of data, but you can use filters to check for certain types of requests. – Eugene – 2010-02-12T19:24:45.397
Try Wireshark. It tells you everything that happens on your network. It is a lot of data, but you can use filters to check for certain types of requests.
You could also try a different ISP if available in your area (via cellphone maybe). This will help you determine if your ISP is messing you up. Or you could also try a different OS (get one if those live Linux discs and load from it). This might tell you if it's OS-specific, even though you used two different versions of Windows. – Eugene – 2010-02-12T19:30:04.820
Sorry for double-post. I am on an iPhone, don't know what happened. – Eugene – 2010-02-12T19:31:14.540
After over a month of having this problem... it suddenly went away. So maybe some automatic error tracking picked it up and they fixed it. I don't know. I hate it when that happens. – Jasmine – 2010-02-13T20:08:26.767