Waiting forever for certain websites

I have recently found that I cannot access certain websites anymore. Every time I try my IE8 shows a 'Waiting for [WEBSITE]...' message and the progress indicator crawls slowly across to ~50% where it just stops. After a long while (>15 minutes) I get a message saying:

- Internet Explorer cannot display the webpage
-
- What you can try:
- [Diagnose Connection Problems]

Using ping works fine, using network diagnostics (as suggested above) works fine, both tell me that there is no problem and I've run McAfee anti-virus scan in full - it says I'm clean! I've even tried clearing the computer of old s/w, defragging and setting the virtual memory to maximum. Also I've tried clearing out all the temp internet pages and cookies. And I've even reloaded Java completely (as suggested by another help site) - no effect!

I have two PC's (WinXP & Vista) running through an AOL Broadband wireless router, both are using direct connections, and both show the same symptoms. This has only started happening in the last couple of weeks, everything was fine before and I haven't done anything major to the system for a long, long while.

The majority of websites I've tried are working OK, just a select few have this problem although I can't see any common denominator between them. The one I use most which fails is www.ancestry.co.uk btw.

I have tried other browsers (Firefox, Opera & Chrome) and I've got exactly the same results so it's not an IE problem. I even loaded the latest AOL Browser - same.

BUT, when I checked with friends they had no problems connecting to the sites in question, so the sites are not down. And when I used my old AOL 9.0 account (gathering dust since I changed the old modem for the wireless router), I connected to the sites straight away, so I guess the DNS stuff must be OK. Weird!

 

Please try: http://66.43.22.71
Of which is the IP address (and same location) of that site

If this works, its one of only a few issues

Temp files: Please run CCleaner
Hosts Files: Have a read HERE and install the updated host file
Internet Settings: Download and Run IE Reset (which can also effect other browsers on your system if its faulty
McAfee, or your firewall settings (personally I'd say McAfee though on this one) And uninstall it, and then run the removal tool

I expect CCleaner should fix it though, but if not try the rest.

 

IP Number

I'm afraid that using the IP number gave the same results as using the full URL. I did use CCleaner though, it didn't solve the problem though it did get rid of a lot of old junk I had lying around.

 

Can you post the results of Tracert...

Start->Run...->Cmd

Code:

tracert 66.43.22.71

 

No problem, looks interesting! I tried it a couple of times, same result each time.

---------------------------

C:\Documents and Settings\David>tracert 66.43.22.71

Tracing route to ancestry.co.uk [66.43.22.71]
over a maximum of 30 hops:

1 1 ms 4 ms 3 ms 192.168.1.1
2 * 29 ms 28 ms host-92-11-96-1.as43234.net [92.11.96.1]
3 27 ms 27 ms 27 ms 92.31.253.32
4 29 ms 31 ms 28 ms xe-11-2-0-scr001.log.as13285.net [78.144.2.3]
5 28 ms 31 ms 28 ms Opal-ge-2.2.0.mpr1.lhr3.above.net [213.161.78.21
3]
6 101 ms 101 ms 102 ms so-0-1-0.mpr2.dca2.us.above.net [64.125.27.165]

7 107 ms 102 ms 104 ms xe-0-3-0.cr2.dca2.us.above.net [64.125.29.25]
8 103 ms 150 ms 102 ms xe-0-1-0.er2.dca2.us.above.net [64.125.27.29]
9 103 ms 107 ms 104 ms xe-0-1-0.er2.iad10.us.above.net [64.125.31.210]

10 103 ms 102 ms 104 ms 64.125.12.82
11 104 ms 104 ms 104 ms te0-2-1-0.rar3.washington-dc.us.xo.net [207.88.1
2.205]
12 184 ms 183 ms 184 ms vb6.rar3.chicago-il.us.xo.net [207.88.12.33]
13 181 ms 187 ms 187 ms te-4-1-0.rar3.denver-co.us.xo.net [207.88.12.22]

14 183 ms 185 ms 187 ms ae0d0.mcr1.saltlake-ut.us.xo.net [216.156.0.2]
15 186 ms 186 ms 185 ms 67.110.119.70.ptr.us.xo.net [67.110.119.70]
16 186 ms 187 ms 181 ms 71.4.83.22.ptr.us.xo.net [71.4.83.22]
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

 

Same subnet as where mine times out (this does not indicate a fault). I find it curious why a .co.uk domain travells over the pond but whatever.

Can you post trace routes for other sites that are causing problems?

 

Tracert

This one always fails in IE, but the tracert always get through, I tried several times. More to follow...

-----

C:\Documents and Settings\David>tracert projectfiregun.com

Tracing route to projectfiregun.com [213.188.129.19]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 27 ms 26 ms 27 ms host-92-11-96-1.as43234.net [92.11.96.1]
3 28 ms 26 ms 27 ms 92.31.252.0
4 31 ms 29 ms 29 ms xe-10-2-0-scr002.log.as13285.net [78.144.2.129]

5 31 ms 30 ms 30 ms Opal-ge-2.2.0.mpr1.lhr2.above.net [213.161.78.20
9]
6 31 ms 31 ms 65 ms xe-1-1-0.mpr1.lhr1.uk.above.net [64.125.27.150]

7 32 ms 31 ms 30 ms ldn-b5-link.telia.net [213.248.104.37]
8 31 ms 30 ms 29 ms ldn-bb1-link.telia.net [80.91.252.205]
9 52 ms 52 ms 52 ms hbg-bb1-link.telia.net [80.91.254.216]
10 58 ms 58 ms 58 ms kbn-bb1-link.telia.net [80.91.254.1]
11 64 ms 64 ms 65 ms oso-b1-link.telia.net [80.91.250.138]
12 67 ms 66 ms 67 ms active24-111911-oso-b1.c.telia.net [213.248.97.1
14]
13 * * * Request timed out.
14 67 ms 65 ms 66 ms merkur.activeisp.com [213.188.129.19]

Trace complete.

 

This one always fails too.

-------------------------------------------------

C:\Documents and Settings\David>tracert levi-tarot.co.uk

Tracing route to levi-tarot.co.uk [66.43.57.122]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 27 ms 27 ms 27 ms host-92-11-96-1.as43234.net [92.11.96.1]
3 26 ms 39 ms 27 ms 92.31.253.32
4 45 ms 28 ms 28 ms xe-11-2-0-scr001.log.as13285.net [78.144.2.3]
5 30 ms 28 ms 29 ms xe-4-0-0-0.lon20.ip4.tinet.net [77.67.64.9]
6 119 ms 161 ms 119 ms xe-1-1-0.mtl10.ip4.tinet.net [89.149.184.74]
7 119 ms 119 ms 119 ms optimal-payments-gw.ip4.tinet.net [77.67.71.34]

8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

 

Tracert

This is another one which fails in IE, interestingly it stops both times at hop 12, but the actual name is different in the two cases. I have no idea whether that is significant.

-----------------

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\David>tracert support.ccbill.com

Tracing route to support.ccbill.com [64.38.240.40]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 27 ms 27 ms 27 ms host-92-11-96-1.as43234.net [92.11.96.1]
3 27 ms 26 ms 27 ms 92.31.253.32
4 28 ms 28 ms 28 ms xe-10-2-0-scr001.log.as13285.net [78.144.2.1]
5 28 ms 27 ms 28 ms xe-11-0-0-scr010.sov.as13285.net [78.144.0.226]

6 29 ms 29 ms 29 ms 1-2.r1.lo.hwng.net [195.66.224.227]
7 100 ms 99 ms 100 ms 1-1.r1.ny.hwng.net [69.16.191.49]
8 117 ms 123 ms 125 ms 3-1.r1.ch.hwng.net [69.16.191.41]
9 168 ms 175 ms 179 ms 1-1.r1.la.hwng.net [69.16.191.33]
10 182 ms 174 ms 175 ms 2-1.r2.ph.hwng.net [69.16.191.38]
11 174 ms 174 ms 173 ms 1-4.r1.ph.hwng.net [69.16.191.73]
12 188 ms 185 ms 203 ms wsip-70-166-196-178.ph.ph.cox.net [70.166.196.17
8]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

C:\Documents and Settings\David>tracert support.ccbill.com

Tracing route to support.ccbill.com [64.38.240.40]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * 27 ms 27 ms host-92-11-96-1.as43234.net [92.11.96.1]
3 27 ms 27 ms 27 ms 92.31.253.32
4 29 ms 28 ms 27 ms xe-10-2-0-scr001.log.as13285.net [78.144.2.1]
5 * 28 ms 28 ms xe-11-0-0-scr010.sov.as13285.net [78.144.0.226]

6 29 ms 29 ms 28 ms 1-2.r1.lo.hwng.net [195.66.224.227]
7 96 ms 95 ms 97 ms 1-1.r1.ny.hwng.net [69.16.191.49]
8 117 ms 116 ms 116 ms 3-1.r1.ch.hwng.net [69.16.191.41]
9 173 ms 174 ms 174 ms 1-1.r1.la.hwng.net [69.16.191.33]
10 175 ms 175 ms 174 ms 2-1.r2.ph.hwng.net [69.16.191.38]
11 175 ms 174 ms 174 ms 1-4.r1.ph.hwng.net [69.16.191.73]
12 191 ms 207 ms 207 ms 64.209.111.182
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

 

Since tracert levi-tarot.co.uk, seemed to be the worst affected, could you try Safe Mode with Networking (by pressing the F8 key at Windows startup)

I certainly agree with Arie, since another connection works without issue then it really means the current connection (at ISP) must be at fault.
But, just in case McAfee is causing the issue (who knows maybe a rule or something) Running Tracert in Safe Mode with networking will at least eliminate your computer all together.

Otherwise just contact your ISP and they will just test it from their end.

 

Isp

Thanks, that sounds reasonable, although it is worth mentioning that I changed from the modem to the wireless router over 6 months ago, and this timeout problem only started happening last week.

 

Yes well I decided to do my own traceRT on the above sites and got a similar occurrence "Request Timed Out" (on approx. around the same TTL value ~13)
Also with reasonably normal round-trip times in milliseconds (since I'm on the other side of the world that wasn't an issue)

The sites themselves loaded in the browser, unaware of any bad hops.

Anyway, this got me thinking 1. Is it normal 2. What I have in security/network 3. Why did it "Request Timed Out" so early?

So after a lot of searching around and reading others comments
And confirming my network and security and computer settings didn't seem to be the issue.
I'm starting to think that its reasonably normal! of some ISPs and possibly certain data being blocked or slowed or even the external site itself.

The traceRT command is not all that thorough in diagnosing the fault
Nor is NSlookup, or ping as well.
I wonder if there's a much better (free or trial) program I could use to fully confirm why the hops time out, and where, and if they have some type of common issue.

--
Anyway, if others want to tracert

ie tracert support.ccbill.com (being one of the addresses the OP had posted above)
And also confirm "Request Timed Out" on 13 or 14 area, that would be good.
Maybe everyone has this issue?

edit:
It was just after IP 70.1**.***.*** place as well

ie as above:

 

kimsland,

As arie posted the hops are timing out because they drop Ping requests, this is not unusual but tracert can often be used to diagnose faults nearer the computer. e.g. if my router was dropping pings (LAN side) then I'd know there was a problem, ISP's can also use this information to diagnose problems on their network.

 

I got the blinking cursor immediately, after the GET /index.html I got the following.

--------------------------------------

HTTP/1.0 302 Found
Location: https:///index.html
Server: BigIP
Connection: close
Content-Length: 0

Connection to host lost.

---------------------------------------

I'm wondering if maybe the connection isn't the problem, rather it is the actual display of the page, maybe some feature within the actual html is causing the browsers to hang. It is interesting that when I use the AOL 9.0 to access ancestry.co.uk and try to login, the https://secure.ancestry.co.uk/security/passwordlogin.aspx page suffers the same slowdown and failure that the browsers do with the main page. I've tried disabling javascript, no effect. Similarly I've tried disabling the firewall (temporarily!) again no change.

Does that sound feasible?

 

According to my provider Virginmedia, informed me that the cause was due to the Web page being over subscribed at that time. They also suggested that I contact the Web site provider and complain.

 

I knew it wasn't you and me

This is a website server issue. Their end.