Anyone else getting lots of "problem loading page" errors?

**Mitch G** · **12-15-06, 04:40 PM**

I've had lots of occasions where I get a problem loading page error because it can't find the shack. Sometimes a refresh will "fix" the problem, other times I can't get to the shack at all.

My belief is that this problem started around the time the site moved to a new server.

I'm using Firefox 1.<something>.

Mitch

**Sonnie** · **12-15-06, 05:01 PM**

Hmmm... that sounds strange indeed. First I've heard of it though.

You might try clearing your cache in FF... might also wanna download version 2.0.

We'll also see if anyone else is having an issue. Naturally I'm in and out constantly, back and forth between two computers daily, so I'd think the issue would occur for me, but that's not always the case.

**Mitch G** · **12-15-06, 06:07 PM**

Sonnie,

Yeah, I wanted to see if others were having the same problem.
I wouldn't be surprised if it was at my end.

Mitch

**Sonnie** · **12-15-06, 06:19 PM**

This reminds me I need to get your DVDs back to you.

**Otto** · **12-15-06, 09:16 PM**

Yeah, I've been having the same page loading problems over the last week or so. Once or twice a day, it just can't find the shack...

**Sonnie** · **12-15-06, 11:54 PM**

Seriously? I wonder what it could be?

**Danny** · **12-17-06, 09:22 PM**

I haven't had any problems yet. Thats weird

**Sonnie** · **12-18-06, 12:31 AM**

Yeah, none of our staff have said anything... a few have responded that things have been great since we switched to the new server.

Otto, I'm thinkin' maybe it's just a clearing the cache/temp files kinda thing. We haven't had any complaints other than these two here. If it were a server problem I would think we all would be experiencing it... or at least we would have quite a few with the same problem.

**Otto** · **12-18-06, 09:15 AM**

No problem. I'll clean up and see if it persists.

Have a good day.

**Fincave** · **12-18-06, 12:35 PM**

I have a problem with not finding 'The Shack' on the odd occasion, probably 1/20 attempts, hitting refresh always solves the problem. Am using Opera 8.? do clear the cache once every few days.

**Steve Williamson** · **12-19-06, 04:02 AM**

I use IE6 and it is getting worse, maybe every three goes it will not find the shack, tried clearing cache etc, I will try with FF next time IE fails.

**Sonnie** · **12-19-06, 09:55 AM**

I have no idea what could be happening. If it happens to everyone then it would generally indicate a forum/server issue, but when it only happens to a few, it is very difficult to pinpoint and would generally indicate a user side issue. It may be that you have to clear out cookies, temporary Internet files/cache, and history. I'm using three different computers daily for now (switching out laptops on two of these) and I haven't had the first issue of the Shack not being found. I access many different areas of the Shack daily and am in and out over a dozen times a day.... so you would think it would happen with me every now and then...

Either way, you guys please keep us posted if it continues or if it clears up and what you did to clear it up... so we all know. We are open to any ideas.

**Steve Williamson** · **12-19-06, 05:07 PM**

Tried again this morning when the email arrived, got the attached image, I would put it down to a dns propogation issue, does it happen in the states, or is it only overseas. The ping command shows a network issue rather than a cookie or cache problem.

**Sonnie** · **12-19-06, 09:49 PM**

Maybe if one of you get this again you can do a tracert instead of a ping. Then copy and paste it here so I can look at it and forward it to our network manager if need be. At least with a tracert we can see where the brick wall is.

DNS propagation has to do with your ISP updating their DNS cache. If you get through at some times, then their cache would be up to date. Generally that takes no more than 24 hours... 48 max with a few ISPs.

**Steve Williamson** · **12-24-06, 09:41 PM**

Tracert:

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

C:\Documents and Settings\Steve>tracert www.hometheatershack.com
Unable to resolve target system name www.hometheatershack.com.

C:\Documents and Settings\Steve>

5 minutes later, I can load the shack to post this mesage, go figure

**Sonnie** · **12-24-06, 10:16 PM**

Hmmm... it appears you are not even getting out your own back door on the trace.

For instance... the first thing I get on a trace route is my router IP address, then my modem IP address, then Centurytel (while here at home since they are my ISP), then it goes to ATT Worldnet Service IP address ... and on and on until it finally hits our IP address.

tracert www.hometheatershack.com

Tracing route to hometheatershack.com [72.52.145.5]
over a maximum of 30 hops:

1 24 ms 1 ms 1 ms 192.168.2.1
2 26 ms 1 ms 2 ms 192.168.1.1
3 25 ms 24 ms 24 ms dthnalcobr1.dthnalcoro1.centurytel.net [69.29.190.25]
4 25 ms 24 ms 24 ms ge-0-1-gw-rt.doth.centurytel.net [64.91.89.2]
5 105 ms 33 ms 32 ms 12.116.164.181
6 54 ms 56 ms 57 ms tbr1-p010403.attga.ip.att.net [12.123.20.194]
7 56 ms 57 ms 57 ms tbr2-cl1958.dtrmi.ip.att.net [12.122.10.197]
8 53 ms 52 ms 52 ms gar3-p390.dtrmi.ip.att.net [12.123.139.141]
9 56 ms 54 ms 54 ms 12.118.112.34
10 94 ms 54 ms 54 ms lw-core2-ge2.rtr.liquidweb.com [209.59.157.34]
11 59 ms 57 ms 55 ms lw-dc2-dist2-ge2.rtr.liquidweb.com [209.59.157.110]
12 56 ms 54 ms 57 ms host.hometheatershack.com [72.52.145.5]

Trace complete.

**Steve Williamson** · **12-24-06, 11:08 PM**

I know, yet I can find every thing .

tracert www.google.com

Tracing route to www.l.google.com [66.102.7.147]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms shoreline-svr1.shorelinecomputersolutions.com.au
[192.168.0.1]
2 85 ms 79 ms 79 ms 139.134.98.179
3 77 ms 89 ms 89 ms 139.134.98.142
4 78 ms 89 ms 89 ms 139.134.50.5
5 78 ms 89 ms 89 ms GigabitEthernet2-2.cha36.Brisbane.telstra.net [1
39.130.3.253]
6 77 ms 89 ms 89 ms TenGigE0-8-0-7.cha-core4.Brisbane.telstra.net [2
03.50.50.1]
7 * 98 ms 109 ms TenGigabitEthernet0-8-0-0-1.ken-core4.Sydney.tel
stra.net [203.50.6.41]
8 97 ms 89 ms 99 ms Port-Channel1.pad-gw2.Sydney.telstra.net [203.50
.6.29]
9 87 ms 99 ms 99 ms 10GigabitEthernet1-0.sydp-core02.Sydney.reach.co
m [203.50.13.46]
10 97 ms 99 ms 89 ms i-9-0.sydp-core01.net.reach.com [202.84.221.89]

11 257 ms 259 ms 239 ms i-14-0.wil-core03.net.reach.com [202.84.143.246]

12 366 ms 409 ms 439 ms i-6-7.wil03.net.reach.com [202.84.251.230]
13 237 ms 239 ms 239 ms Google.peer.wil03.net.reach.com [134.159.62.26]

14 257 ms 249 ms 289 ms 216.239.43.144
15 257 ms 259 ms 259 ms 72.14.233.129
16 287 ms 259 ms 249 ms 72.14.233.131
17 267 ms 269 ms 269 ms 72.14.233.129
18 258 ms 259 ms 269 ms mc-in-f147.google.com [66.102.7.147]

Trace complete.

C:\Documents and Settings\Steve>

And this is yours now I can open the shack several minutes later

Tracing route to hometheatershack.com [72.52.145.5]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms shoreline-svr1.shorelinecomputersolutions.com.au
[192.168.0.1]
2 95 ms 89 ms 89 ms 139.134.98.179
3 88 ms 89 ms 79 ms 139.134.98.142
4 88 ms 89 ms 89 ms 139.134.50.5
5 88 ms 89 ms 89 ms GigabitEthernet2-2.cha36.Brisbane.telstra.net [1
39.130.3.253]
6 88 ms 89 ms 89 ms TenGigE0-8-0-7.cha-core4.Brisbane.telstra.net [2
03.50.50.1]
7 109 ms 109 ms 99 ms TenGigabitEthernet0-8-0-0-1.ken-core4.Sydney.tel
stra.net [203.50.6.41]
8 98 ms 99 ms 99 ms Port-Channel1.pad-gw2.Sydney.telstra.net [203.50
.6.29]
9 98 ms 99 ms 99 ms 10GigabitEthernet2-0.sydp-core02.Sydney.reach.co
m [203.50.13.50]
10 97 ms 99 ms 99 ms i-9-0.sydp-core01.net.reach.com [202.84.221.89]

11 258 ms 259 ms 259 ms i-0-0.wil-core03.net.reach.com [202.84.143.209]

12 257 ms 259 ms 249 ms i-6-7.wil03.net.reach.com [202.84.251.230]
13 327 ms 429 ms 409 ms ge2-8.br01.lax04.pccwbtn.net [63.218.51.77]
14 266 ms 279 ms 289 ms uunet.pos6-1.cr01.lax04.pccwbtn.net [63.218.51.5
0]
15 * 271 ms 269 ms 0.so-6-0-0.XT2.LAX7.ALTER.NET [152.63.112.154]
16 317 ms 309 ms 309 ms 0.so-3-0-0.XL2.CHI2.ALTER.NET [152.63.64.122]
17 317 ms 319 ms 309 ms POS7-0.GW9.CHI2.ALTER.NET [152.63.69.165]
18 327 ms 319 ms 309 ms liquidwebOC12-gw.customer.alter.net [65.207.234.
198]
19 317 ms 399 ms 409 ms lw-core1-ge2.rtr.liquidweb.com [209.59.157.30]
20 326 ms 319 ms 319 ms lw-dc2-dist2-ge1.rtr.liquidweb.com [209.59.157.1
06]
21 326 ms 329 ms 329 ms host.hometheatershack.com [72.52.145.5]

Trace complete.

C:\Documents and Settings\Steve>

**Sonnie** · **12-25-06, 11:02 AM**

But when you get this:

C:\Documents and Settings\Steve>tracert www.hometheatershack.com
Unable to resolve target system name www.hometheatershack.com.

I would think it means you are not even getting to your first stop:

1 <1 ms <1 ms <1 ms shoreline-svr1.shorelinecomputersolutions.com.au [192.168.0.1]

Otherwise we could see how far the trace route went and it would time out when it got to one of these:

18 327 ms 319 ms 309 ms liquidwebOC12-gw.customer.alter.net [65.207.234.198]
19 317 ms 399 ms 409 ms lw-core1-ge2.rtr.liquidweb.com [209.59.157.30]
20 326 ms 319 ms 319 ms lw-dc2-dist2-ge1.rtr.liquidweb.com [209.59.157.106]
21 326 ms 329 ms 329 ms host.hometheatershack.com [72.52.145.5]

.... if it was the Shack that wasn't loading for you.

It could be a problem anywhere between you and the Shack...

**Steve Williamson** · **02-01-07, 07:35 AM**

Ok, my server died (used for internet proxy, email and file storage), managed to recover the emails and files (pain in the a## linux server) now use netgear router to route internet traffic and I can access the shack whenever I want, go figure. The problem was with the old server, I had no problems with any other site at all, only the shack.

**Sonnie** · **02-01-07, 12:48 PM**

Strange... but at least it's all working wonderfully now...

**bobgpsr** · **02-01-07, 07:34 PM**

Sometimes HTS is slow to first pop up during a new session. I use Mediacom at home for my ISP. Here is my tracert to HTS:

Tracing route to hometheatershack.com [72.52.145.5]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 8 ms 7 ms 10 ms 10.21.245.1
3 8 ms 11 ms 10 ms 12-215-16-129.client.mchsi.com [12.215.16.129]
4 13 ms 12 ms 15 ms 12-215-5-14.client.mchsi.com [12.215.5.14]
5 19 ms 18 ms 21 ms 12.122.99.74
6 20 ms 21 ms 22 ms tbr2-cl18.dtrmi.ip.att.net [12.122.10.133]
7 19 ms 19 ms 19 ms gar3-p390.dtrmi.ip.att.net [12.123.139.141]
8 29 ms 22 ms 21 ms 12.118.112.34
9 20 ms 21 ms 22 ms lw-core1-ge2.rtr.liquidweb.com [209.59.157.30]
10 21 ms 24 ms 22 ms lw-dc2-dist1-ge1.rtr.liquidweb.com [209.59.157.98]
11 20 ms 24 ms 20 ms host.hometheatershack.com [72.52.145.5]

Trace complete.

**Sonnie** · **02-01-07, 09:11 PM**

Wow... that pretty fast there Bob...

Here's mine:

Tracing route to hometheatershack.com [72.52.145.5]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.2.1
2 1 ms 1 ms 1 ms 192.168.1.1
3 25 ms 24 ms 24 ms 75-120-97-1.dyn.centurytel.net [75.120.97.1]
4 24 ms 24 ms 24 ms GE-0-0-0-0-j1-rt.doth.centurytel.net [64.91.89.9]
5 58 ms 57 ms 57 ms 12.116.164.181
6 65 ms 67 ms 64 ms tbr1-p010403.attga.ip.att.net [12.123.20.194]
7 69 ms 67 ms 67 ms tbr2-cl1958.dtrmi.ip.att.net [12.122.10.197]
8 61 ms 62 ms 62 ms gar3-p390.dtrmi.ip.att.net [12.123.139.141]
9 65 ms 64 ms 64 ms 12.118.112.34
10 65 ms 64 ms 64 ms lw-core2-ge2.rtr.liquidweb.com [209.59.157.34]
11 66 ms 67 ms 64 ms lw-dc2-dist2-ge2.rtr.liquidweb.com [209.59.157.110]
12 70 ms 67 ms 70 ms host.hometheatershack.com [72.52.145.5]

Trace complete.

**Jerm357** · **05-25-08, 11:36 PM**

I have this problem but have been living with it for a long time. Its just some times I try to come here and the site wont load and I have to surff around the web some where else for like 5 min and try again and it usually works. This has been going on for some time now.

**Sonnie** · **07-13-08, 12:23 AM**

It is most likely not the Shack's server that is causing the problem... otherwise we would be dozens of complaints and if it were that bad, we probably would never keep anyone around because the same thing would be happening to every person that visited.

If you think about it, it only makes sense that if it were the Shack's server that everyone would be effected the same... even me.

As explained about, it is generally somewhere between the end user and the Shack's server where the problem lies. Most likely if you visited another site that followed the same traceroute as that of the Shack, you would experience problems with them as well, because you are crossing over the same hop that is causing the problem.

If you are still experiencing the problem you might try running "tracert www.hometheatershack.com" from your command prompt and it may tell you wherein lies the problem.

Advertisement