Haunt Forum banner

1 - 20 of 43 Posts

·
Premium Member
Joined
·
5,858 Posts
Ok, if one of these timeouts happens, could one of you do me a HUGE favor? Right when it happens do the following (for Windows users):

Tracert:
1) Click on Start then Run...
2) Type "cmd" and press enter
3) Type "tracert 69.16.212.167" and press enter
4) Right click on the window and click on Select All
5) Press enter to copy it into the clipboard
Then either send me a PM or an e-mail and paste the contents of that report into your message to me. That will help the tech support people diagnose what is going on.

I will attempt to do the same myself if I happen to be around when these timeouts happen. I'll pop into chat tonight to see if I can be there when this occurs.
 

·
Registered
Joined
·
5,423 Posts
I don't think it's just chat Z. I know there are times I just try to go to the forum and it acts all screwy and doesn't load like it should. It just happened to me without going to chat.
 

·
Registered
Joined
·
6,024 Posts
I this what the log should look like? This is now, with everything working fine, I just wanted to know if this is what you want:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Bob>tracert 69.16.212.167
Tracing route to 69.16.212.167 over a maximum of 30 hops
1 <1 ms 1 ms <1 ms homeportal.gateway.2wire.net [********]
2 13 ms 11 ms 13 ms adsl-76-213-207-254.dsl.mtry01.sbcglobal.net [**********]
3 11 ms 13 ms 12 ms dist1-vlan50.mtry01.pbi.net [216.102.186.187]
4 14 ms 11 ms 11 ms bb1-g8-0.mtry01.pbi.net [64.173.191.241]
5 11 ms 13 ms 11 ms bb2-g1-2.mtry01.pbi.net [151.164.188.154]
6 18 ms 19 ms 19 ms 151.164.92.177
7 18 ms 17 ms 19 ms ex1-p14-0.eqsjca.sbcglobal.net [151.164.41.10]
8 18 ms 17 ms 19 ms gar7-p390.sffca.ip.att.net [12.122.79.101]
9 68 ms 76 ms 68 ms 12.122.85.134
10 69 ms 70 ms 72 ms tbr1-cl1.cgcil.ip.att.net [12.122.10.5]
11 72 ms 72 ms 74 ms tbr2-cl22.cgcil.ip.att.net [12.122.9.134]
12 71 ms 72 ms 72 ms tbr2-cl18.dtrmi.ip.att.net [12.122.10.133]
13 70 ms 68 ms 66 ms gar3-p390.dtrmi.ip.att.net [12.123.139.141]
14 * * * Request timed out.
15 99 ms 92 ms 90 ms lw-core1-ge2.rtr.liquidweb.com [209.59.157.30]
16 636 ms 92 ms 92 ms lw-dc1-dist5-ge1.rtr.liquidweb.com [209.59.157.6
2]
17 89 ms 92 ms 90 ms 69.16.212.167
Trace complete.
C:\Documents and Settings\Bob>tracert 69.16.212.167
 

·
Premium Member
Joined
·
5,858 Posts
I this what the log should look like? This is now, with everything working fine, I just wanted to know if this is what you want:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Bob>tracert 69.16.212.167
Tracing route to 69.16.212.167 over a maximum of 30 hops
1 <1 ms 1 ms <1 ms homeportal.gateway.2wire.net [********]
2 13 ms 11 ms 13 ms adsl-76-213-207-254.dsl.mtry01.sbcglobal.net [**********]
3 11 ms 13 ms 12 ms dist1-vlan50.mtry01.pbi.net [216.102.186.187]
4 14 ms 11 ms 11 ms bb1-g8-0.mtry01.pbi.net [64.173.191.241]
5 11 ms 13 ms 11 ms bb2-g1-2.mtry01.pbi.net [151.164.188.154]
6 18 ms 19 ms 19 ms 151.164.92.177
7 18 ms 17 ms 19 ms ex1-p14-0.eqsjca.sbcglobal.net [151.164.41.10]
8 18 ms 17 ms 19 ms gar7-p390.sffca.ip.att.net [12.122.79.101]
9 68 ms 76 ms 68 ms 12.122.85.134
10 69 ms 70 ms 72 ms tbr1-cl1.cgcil.ip.att.net [12.122.10.5]
11 72 ms 72 ms 74 ms tbr2-cl22.cgcil.ip.att.net [12.122.9.134]
12 71 ms 72 ms 72 ms tbr2-cl18.dtrmi.ip.att.net [12.122.10.133]
13 70 ms 68 ms 66 ms gar3-p390.dtrmi.ip.att.net [12.123.139.141]
14 * * * Request timed out.
15 99 ms 92 ms 90 ms lw-core1-ge2.rtr.liquidweb.com [209.59.157.30]
16 636 ms 92 ms 92 ms lw-dc1-dist5-ge1.rtr.liquidweb.com [209.59.157.6
2]
17 89 ms 92 ms 90 ms 69.16.212.167
Trace complete.
C:\Documents and Settings\Bob>tracert 69.16.212.167
Yes, and if you encounter a time when the site is NOT responding, do the exact same thing and copy the output again. Thanks for doing that. Now I can show them a before and after comparison.

I'm aware the site acts screwy too. I've brought it up a few times now to no avail. Hopefully if we can get it logged as specified above, we can get my host company to fix it.
 

·
Registered
Joined
·
1,949 Posts
I don't know which hosting plan you use. But the issues people are describing, reminds me of either another service or site on a shared server peaking some seriously heavy usage, or even a DOS attack.

Then again, Liquidweb may just be having uptime issues with their hardware and are playing dumb :D
 

·
Premium Member
Joined
·
5,858 Posts
I use the icestorm network and have been doing so for the past 6 years now with no real problems before this. They've recently grown their company and I'm starting to feel like in doing so, they've lost something of their (formerly) great tech support in the process. In "the old days" this problem would have been gone in no more than a day.
 

·
Premium Member
Joined
·
5,858 Posts
I just had the site hang as I was posting the above post. I ran a tracert and I wound up having it timeout on the request at our server. Ran it again after my post went through and it went through just fine. Sent the info along to tech support. Hope they can do something with it.
 

·
Registered
Joined
·
4,949 Posts
Well this news makes me feel better I thought it was the new computer. Damn Vista crap
 

·
Registered
Joined
·
1,317 Posts
Discussion Starter #13
I just had the site hang as I was posting the above post. I ran a tracert and I wound up having it timeout on the request at our server. Ran it again after my post went through and it went through just fine. Sent the info along to tech support. Hope they can do something with it.
The same thing happened to me last nite. I tried to get you the tracert thing but mine was timing out also.
 

·
Premium Member
Joined
·
5,858 Posts
The same thing happened to me last nite. I tried to get you the tracert thing but mine was timing out also.
Well, that's the info we want! They need to know if its their server that's timing out or one of the other ones along the way to get there. If you run another one, let it time out and do it's thing and send me along the data.

Thanks guys! :)
 

·
Registered
Joined
·
1,317 Posts
Discussion Starter #18
Microsoft Windows [Version 6.0.6000]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\Stephie>tracert 69.16.212.167

Tracing route to 69.16.212.167 over a maximum of 30 hops

1 1 ms 2 ms 1 ms 192.168.1.1
2 11 ms 11 ms 11 ms WS-ESR1-72-49-80-1.fuse.net [72.49.80.1]
3 12 ms 12 ms 12 ms ws-osr1-g3-1.10.zoomtown.com [216.68.212.2]
4 29 ms 11 ms 11 ms sw2-g3-15.core.fuse.net [216.68.212.7]
5 12 ms 12 ms 12 ms core4-g2-0.core.fuse.net [216.68.7.16]
6 18 ms 18 ms 18 ms ge-5-1.hsa2.Cincinnati1.Level3.net [4.78.218.9]

7 18 ms 18 ms 18 ms so-5-0-0.mp1.Cincinnati1.Level3.net [4.68.124.24
1]
8 18 ms 19 ms 18 ms ae-0-0.bbr1.Chicago1.Level3.net [64.159.1.33]
9 159 ms 27 ms 218 ms ae-12-51.car2.Chicago1.Level3.net [4.68.101.3]
10 26 ms 27 ms 25 ms WBS-CONNECT.car2.Chicago1.Level3.net [4.71.182.1
4]
11 27 ms 27 ms 28 ms lw-core1-ge3.rtr.liquidweb.com [209.59.157.10]
12 28 ms 28 ms 57 ms lw-dc1-dist5-ge1.rtr.liquidweb.com [209.59.157.6
2]
13 27 ms 27 ms 27 ms 69.16.212.167

Trace complete.

C:\Users\Stephie>
 

·
Premium Member
Joined
·
5,858 Posts
Ok, at this point you guys don't need to run the traceroute any more. The host company is now aware of the fact the problem is on their end. I've requested to have our site moved to a different server to see if that helps any.
 
1 - 20 of 43 Posts
Top