Sometimes cannot access HTGuide at work

[purplepeople]

Hi all,

At work, I can always access HTGuide on the first try. And viewing pages seems to be no problem. Even posting is okay for a while. Then, for seemingly no reason, I cannot access it. IE6 will display the error page of death... with a message that the web site does not exist. Reloading doesn't matter. Typing in the address won't do it. Restarting IE doesn't help. Even re-booting W2K does not work. Access is over the LAN and on SDSL. Very strange!

In comparison, at home, using an older Win98 running Mozilla on ADSL, I can always access HTGuide. There are no problems at all. None... very weird!

Anybody have any insights?

ensen.

[Burke Strickland]

Sounds like IE6 may be the "purple people eater" that old song was written about. :>) I'm glad you keep coming back despite those technical difficulties.

I occasionally get error pages when trying to access HT Guide, but since we migrated to the new software and server, usually hitting the "refresh" button takes care of it. I wonder if the firewall at your work location is intermittently blocking the site based on content filters or something like that.

You might want to send Kevin P, our technical guru for all things web and site related, a "heads up" private message just in case he doesn't see this thread right away (although he probably will -- he checks this area fairly frequently).

Good luck!

Burke

[George Bellefontaine]

Has your employer rigged something to stop employees from visiting certain internet sites during business hours ? Maybe this thing cuts in if too much time is spent at non-business sites. Probably a stupid guess, but you never know today. Have you tried using Netscape instead of IE6 ?

[purplepeople]

Okay... here I am at work. W2K with all the patches. IE6 with 128-bit and patched. Inoculate and Ad-Aware. There can't be a no-browse filter since I can see everything else in my Favorites list at any time.

The form for this post was opened in a new window from the HTG opening page. Reload works on the other window. I was able to surf the other threads that I've got an eye on, but didn't try to post. Yet, I expect it will stop working sometime during the day. Could your IP address be on our block list? Could the office IP address be on your block list?

It is 10:10AM local here right now. I will note the time this stops working and check back in when I get home.

ensen.

[purplepeople]

Okay.... I don't think it is with HTG. Around 3pm IE6 at work stopped loading up this site, but stranger still, it stopped loading up another fave around 11:30am. I will check with the IT guys on Monday about it. If you don't here from me, then consider it solved.

ensen.

[Lex]

I do sometimes have to press reload myself. But reliability is so strong now, it's almost like no problem at all. It happened to me today as a matter of fact, but a refresh, and it was off to the races. We had a problem early on with this server and a bad cord of all things on the hardware, but once I finally raised enough stink to get that fixed, we've really had no real problems.

Lex

[David Meek]

I've noticed that on occasion, I'll have to retry too. Both at home and at work. It doesn't happen often, maybe 2-3% of the time, but it does happen and it's been fairly consistent for about 3 weeks now. I thought it was just me. . . . :scratchhead:

[Aussie Geoff]

Kevin,

This has been happening to me to often at busy times. Sunday night was bad - I couldn't get at htguide for well over an hour!

I am wondering whether we are reaching some limit on the server of maximum users / threads etc. This is usually an easy tweek to fix.

Geoff

[George Bellefontaine]

I encountered a lot of problems before the changeover, but I haven't had a problem since. And I am using my D-Link Router , too.

[Gordon Moore]

I'm in David's camp....I'll get a 404 error and then alittle while later it comes back....happens pretty consistently in the evening.

[Kevin P]

Guys, next time you get a 404 or timeout accessing the site, go to a command prompt and run the following command:

tracert 64.27.11.233

This will trace the route from your PC to the site. Copy and post the results here. This will help us track down the problem. Also, if you can post the date and time of any errors, I can check the server logs.

Based on what I've read, it's probably a bottleneck at the provider.

[Aussie Geoff]

Kevin,

Here is a good example of the problem from Slovenia on Monday 7 September at 10:40pm local time = 4:40Pm USA Eastern Time. Note the many timeouts and then weird route chosen. All other sites seem to connect really well!

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

C:\Documents and Settings\CostelloGeoff>tracert 64.27.11.233

Tracing route to 64.27.11.233 over a maximum of 30 hops

1 * * * Request timed out.
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 2133 ms 3083 ms * IIX2-WARSSW02.highway.telekom.at [195.3.70.196]

6 * * * Request timed out.
7 * * * Request timed out.
8 460 ms 1061 ms 240 ms so-0-0-0.mp1.London2.Level3.net [212.187.128.61]

9 960 ms 851 ms 840 ms as-0-0.bbr2.Washington1.Level3.net [4.68.128.102]
10 1942 ms 1762 ms 1241 ms so-0-2-0.bbr2.LosAngeles1.Level3.net [64.159.0.246]
11 349 ms 690 ms 360 ms so-10-0.ipcolo2.LosAngeles1.Level3.net [4.68.113.162]
12 1261 ms 490 ms 1141 ms unknown.Level3.net [63.209.82.190]
13 359 ms 350 ms 389 ms htguide.com [64.27.11.233]

Trace complete.

Geoff

[Kevin P]

Geoff,

Post another tracert when HTGuide *is* working as well, so I can compare the traces. The timeouts in the middle could simply be routers not responding to the trace, or it could be an issue with your connection.

The fact that the last few hops responded (though with some awful delays), means the connection was working at least at that point in the trace. If subsequent traces are similar, I'd suspect an issue with your connection or routing in Slovenia and not with HTGuide.

[Aussie Geoff]

Kevin,

I have got this problem now all round the world, parts of the USA, parts of Canada, London and now Solvenia and through all different providers at different hotels - it is intermittend (comes and goes) but is real.

Here is a trace from Solvenia (same Hotel and provider) working well at 8.38am local time: (2:38 am Tuesday USA Easter Time)

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

C:\Documents and Settings\CostelloGeoff>tracert 64.27.11.233

Tracing route to htguide.com [64.27.11.233]
over a maximum of 30 hops:

1 198 ms 179 ms 190 ms max3.amis.net [212.18.32.103]
2 190 ms 179 ms 190 ms mb4-eth0-0.ipv4.amis.net [212.18.32.97]
3 180 ms 180 ms 189 ms mb3-ge-0-0-0-1.ipv4.amis.net [212.18.32.99]
4 180 ms 189 ms 190 ms 80.120.176.93
5 180 ms 199 ms 179 ms IIX2-WARSSW02.highway.telekom.at [195.3.70.196]
6 190 ms 190 ms 199 ms 212.73.202.1
7 220 ms 189 ms 180 ms so-4-0-0.mp1.Vienna1.Level3.net [4.68.112.77]
8 220 ms 200 ms 189 ms so-0-0-0.mp1.London2.Level3.net [212.187.128.61]
9 278 ms 280 ms 280 ms as-0-0.bbr2.Washington1.Level3.net [4.68.128.102]
10 * 350 ms 349 ms so-0-2-0.bbr2.LosAngeles1.Level3.net [64.159.0.246]
11 410 ms 340 ms 340 ms so-10-0.ipcolo2.LosAngeles1.Level3.net [4.68.113.162]
12 461 ms 348 ms 350 ms unknown.Level3.net [63.209.82.190]
13 440 ms 350 ms 350 ms htguide.com [64.27.11.233]

Trace complete.

Geoff

[Kevin P]

Just keep posting traces when you have issues from different locations. For each location, post a trace when it works and when it doesn't work. The non-working Slovenia trace shows the problem happening with the first few hops. If the problem were with HTG, its host, or one of the upstream providers, you'd see timeouts in hops 10-13.

As you can see, you're being routed through Slovenia, Austria, Vienna, London, Washington (USA), Los Angeles, and then to HTGuide (which is hosted in LA). When you had timeouts, they were happening in the Slovenia-London hops, not the US hops.

[purplepeople]

I whought I was all clear at the office and then today, another non-connection. Then it starts to work again this evening as I'm ready to leave.

How do you keep the DOS window open? I run the trace and it gives all these IP addresses, then shuts down before I can copy it.

ensen.

[Kevin P]

If you're on W2K or XP, Start->Run and type cmd. This will bring up a command prompt window. Type the tracert command at the prompt in this window. It will stay open after it's complete.

If you're on 98/ME, Start->Run and type command to accomplish the same thing.

[purplepeople]

I couldn't get HTG this morning but the first try this afternoon was successful. Here's the trace log approx Thu 09 Sep 2004 17:25 PST


Tracing route to htguide.com [64.27.11.233]
over a maximum of 30 hops:

1 <10 ms <10 ms 10 ms 192.168.0.254
2 20 ms 30 ms 20 ms 65.39.153.209
3 30 ms 20 ms 20 ms metro-airport.universcoamericas.net [65.39.152.17]
4 30 ms 30 ms 60 ms boza-metro.universcoamericas.net [65.39.152.9]
5 30 ms 40 ms 40 ms 65.39.152.73
6 40 ms 30 ms 40 ms 65.39.152.42
7 30 ms 40 ms 30 ms universco-van-gw.peer1.net [64.69.65.141]
8 40 ms 41 ms 30 ms gig2-0.sea-gsr-a.peer1.net [64.69.67.130]
9 60 ms 60 ms 50 ms gig0-0.sj-gsr-a.peer1.net [64.69.67.138]
10 60 ms 50 ms 60 ms sntcca2lce1.wcg.net [198.32.176.139]
11 60 ms 60 ms 60 ms sntcca1wcx1-pos9-0.net [64.200.240.217]
12 60 ms 70 ms 70 ms anhmca1wcx3-pos3-0-oc192.wcg.net [64.200.240.109]
13 71 ms 70 ms 60 ms lsanca1wcx1-pos1-0-oc48.wcg.net [64.200.140.146]
14 70 ms 70 ms 60 ms lsanca9lca1-3-4.wcg.net [64.200.139.78]
15 60 ms 70 ms 60 ms htguide.com [64.27.11.233]

Trace complete.



ensen.

[Lex]

Guys, I'm sympathetic to all these issues. However, I also want to point out it is the World Wide Web, and it's success is dependent upon each and every node in your path. I gotta tell you, I have very little problems here in the US accessing HTG. It certainly seems strange that the problems don't hit me.
Lex

[purplepeople]

Here we are at home on ADSL service from theo phone company.

Thu 09 Sep 2004 at approx 23:09 PST.

Tracing route to htguide.com [64.27.11.233]
over a maximum of 30 hops:

1 13 ms 13 ms 13 ms d64-180-160-254.bchsia.telus.net [64.180.160.254]
2 12 ms 14 ms 13 ms 208.181.240.94
3 13 ms 14 ms 14 ms nwmrbc01gr01.bb.telus.com [154.11.4.98]
4 39 ms 38 ms 38 ms nwmrbc01br01.bb.telus.com [154.11.10.93]
5 37 ms 36 ms 38 ms sttlwa01gr02.bb.telus.com [209.53.75.178]
6 39 ms 38 ms 39 ms plalca01gr00.bb.telus.com [154.11.10.2]
7 40 ms 39 ms 39 ms XO.plalca01gr00.bb.telus.com [154.11.3.146]
8 40 ms 40 ms 40 ms p5-2-0.RAR2.SanJose-CA.us.xo.net [65.106.5.177]
9 48 ms 48 ms 47 ms p6-0-0.RAR1.LA-CA.us.xo.net [65.106.0.17]
10 48 ms 49 ms 47 ms p0-0-0.MAR1.LA-CA.us.xo.net [65.106.5.6]
11 45 ms 45 ms 46 ms p1-0.CHR1.LA-CA.us.xo.net [207.88.81.166]
12 46 ms 45 ms 46 ms 66.238.50.78.ptr.us.xo.net [66.238.50.78]
13 46 ms 45 ms 46 ms 64.0.144.6.ptr.us.xo.net [64.0.144.6]
14 46 ms 46 ms 46 ms htguide.com [64.27.11.233]

Trace complete.



Notice that hops don't take longer than 50 ms while at the office, the hops were taking 60 or 70 ms after jump 9. I will do another trace at the office when it is not working... just have to remember to email the HTG IP. (Really, how can you trace an address that is only available in a post on site that cannot be accessed?)

ensen.

[Burke Strickland]

Plan Ahead :&gt

how can you trace an address that is only available in a post on site that cannot be accessed?

Since you know the problem is intermittent and recurring, why not copy the address to a Word document or jot it down on a sticky note to have it handy the next time the problem comes up again?

Burke

[purplepeople]

I finally wised up and sent myself an email with the IP address.

Anyway, this morning it wouldn't load up at the office so I ran the trace and it made it all the way. But a reload still wouldn't work. Here's a copy of that trace.

Approximately 11:29AM PST
Fri 10 Sep 2004

Tracing route to htguide.com [64.27.11.233]
over a maximum of 30 hops:

1 <10 ms <10 ms <10 ms 192.168.0.254
2 40 ms 30 ms 20 ms 65.39.153.209
3 30 ms 20 ms 30 ms metro-airport.universcoamericas.net [65.39.152.17]
4 30 ms 30 ms 30 ms boza-metro.universcoamericas.net [65.39.152.9]
5 30 ms 30 ms 40 ms 65.39.152.73
6 30 ms 30 ms 40 ms 65.39.152.42
7 30 ms 30 ms 40 ms universco-van-gw.peer1.net [64.69.65.141]
8 40 ms 40 ms 41 ms GIG2-0.sea-gsr-a.peer1.net [64.69.67.130]
9 60 ms 60 ms 60 ms GIG0-0.sj-gsr-a.peer1.net [64.69.67.138]
10 50 ms 60 ms 60 ms sntcca2lce1.wcg.net [198.32.176.139]
11 50 ms 60 ms 60 ms sntcca1wcx1-pos9-0.net [64.200.240.217]
12 60 ms 70 ms 70 ms anhmca1wcx3-pos3-0-oc192.wcg.net [64.200.240.109]
13 60 ms 70 ms 80 ms lsanca1wcx1-pos1-0-oc48.wcg.net [64.200.140.146]
14 60 ms 71 ms 70 ms lsanca9lca1-3-4.wcg.net [64.200.139.78]
15 60 ms 70 ms 101 ms htguide.com [64.27.11.233]

Trace complete.


Yet it is working right now 12:54PM. Here's the trace as of this moment.

Tracing route to htguide.com [64.27.11.233]
over a maximum of 30 hops:

1 <10 ms <10 ms <10 ms 192.168.0.254
2 20 ms 30 ms 50 ms 65.39.153.209
3 30 ms 40 ms 30 ms metro-airport.universcoamericas.net [65.39.152.17]
4 50 ms 30 ms 30 ms 65.39.152.30
5 30 ms 30 ms 50 ms 65.39.152.73
6 30 ms 30 ms 40 ms 65.39.152.42
7 30 ms 30 ms 41 ms universco-van-gw.peer1.net [64.69.65.141]
8 30 ms 40 ms 40 ms GIG2-0.sea-gsr-a.peer1.net [64.69.67.130]
9 50 ms 61 ms 60 ms GIG0-0.sj-gsr-a.peer1.net [64.69.67.138]
10 50 ms 60 ms 60 ms sntcca2lce1.wcg.net [198.32.176.139]
11 50 ms 50 ms 60 ms sntcca1wcx1-pos9-0.net [64.200.240.217]
12 60 ms 70 ms 60 ms anhmca1wcx3-pos3-0-oc192.wcg.net [64.200.240.109]
13 100 ms 60 ms 70 ms lsanca1wcx1-pos1-0-oc48.wcg.net [64.200.140.146]
14 70 ms 70 ms 70 ms lsanca9lca1-3-4.wcg.net [64.200.139.78]
15 60 ms 70 ms 90 ms htguide.com [64.27.11.233]

Trace complete.


ensen