The "Troubleshooting FatChatter" thread

[DaFace]

I put this in the tickets forum since it's relatively obscure and can allow people having trouble reaching FatChatter to help troubleshoot. Here's the mirrored important contents of the FatChatter thread:

Originally Posted by DaFace

I sent Phil a message about this the other day, but I figured I'd point it out on here as well. For some reason, there's a weird DNS issue when trying to access this site on Cox in southern Kansas. Every time I try to access the site either at my parents' place or my brother's place, I get this error:

http://img213.imageshack.us/img213/1123/sshotek5.jpg

I can remote back to my home computer in Denver and access the site fine. Anyway, it's probably not a huge issue to spend a bunch of time troubleshooting, but realize that no one down here can get to the site right now.

Originally Posted by Phobia

Great.

I'm also wondering if Cox users can hit the site using direct IP. http://68.178.254.198/forum

Also, see if you can ping fatchatter.com - please share the IP it returns if different than 68.178.254.198.

The following is what godaddy suggested:
Thank you for contacting Hosting Support. Unfortunately I am unable to replicate this issue. When I visit your domain name I am able to successfully view your website. I have tested this with both Firefox and Internet Explorer. To further investigate this matter we ask that you provide the following information:


1. Your Location (City, State)
2. A trace route from the location that is having the issue to your server. Please provide these instructions to one of the users of your site that is experiencing this issue.

Windows:

From your Start Menu, go to ‘Programs,’ then to ‘Accessories.’
Click on ‘MS-DOS Prompt’ or ‘Command Prompt’ depending on your Operating System. A new window will pop up. The window will show something similar to this:

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

C:\WINDOWS>




At the prompt, type the following then hit Enter:

tracert [your server IP or domain name]



You will get back a long list of information then the command prompt again.

To copy the results:

Right click on the menu bar of this window.
Click on Edit: Select All.
Right click again and select Edit: Copy.

This will put the highlighted information into your Windows clipboard, allowing you to paste that into a text file to attach to your response, such as a Notepad or Wordpad .txt file


Macintosh OSX or Linux

You can use an application called Terminal to run a trace route. You should be able to locate Terminal in your hard drive in the Utilities folder, under Applications. Terminal uses a command-line interface. This means you'll be entering commands at a prompt rather than using the more familiar Aqua graphic interface.

Click on Applications: Utilities: Terminal.
At the prompt, type the following then hit Enter:

tracert [your server IP or domain name]


Highlight the contents of the Terminal window.
Click on the ‘Edit’ menu and select ‘Copy.’

You can then paste this information into a text file, which you would then attach to your response.

We understand that this is quite a few steps; however this will allow us to further research the problem you are experiencing. We appreciate your assistance in tracking down the source of this problem.

[Buck]

P.S. Phobia or DaFace, after reading all that I'm probably going to need someone to walk me through that shit while I do it.

[DaFace]

Originally Posted by BuckinKaeding

P.S. Phobia or DaFace, after reading all that I'm probably going to need someone to walk me through that shit while I do it.

Depending on when you do it, I may be on Yahoo, so just catch me on there. It's not as complicated as it looks.

[Buck]

Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\Matt>ping fatchatter.com

Pinging fatchatter.com [68.178.254.198] with 32 bytes of data:
Reply from 68.178.254.198: bytes=32 time=36ms TTL=53
Reply from 68.178.254.198: bytes=32 time=33ms TTL=53
Reply from 68.178.254.198: bytes=32 time=30ms TTL=53
Reply from 68.178.254.198: bytes=32 time=30ms TTL=53

Ping statistics for 68.178.254.198:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 30ms, Maximum = 36ms, Average = 32ms

C:\Users\Matt>tracert fatchatter.com

Tracing route to fatchatter.com [68.178.254.198]
over a maximum of 30 hops:

1 2 ms 2 ms 1 ms 192.168.1.1
2 10 ms 7 ms 7 ms ip68-6-144-1.sd.sd.cox.net [68.6.144.1]
3 14 ms 7 ms 7 ms elcnsysc01-gex0915.sd.sd.cox.net [68.6.10.142]
4 12 ms 7 ms 8 ms fed1dsrj02-ge500.0.rd.sd.cox.net [68.6.8.4]
5 19 ms 20 ms 21 ms paltbbrj02-ae0.0.r2.pt.cox.net [68.1.0.235]
6 25 ms 22 ms 26 ms ge-4-0-0.mpr2.sjc2.us.above.net [64.125.31.70]
7 24 ms 22 ms 20 ms so-1-0-0.mpr4.lax9.us.above.net [64.125.26.29]
8 35 ms 23 ms 36 ms so-0-0-0.mpr3.lax9.us.above.net [64.125.26.145]

9 30 ms 29 ms 68 ms xe-1-1-0.mpr3.phx2.us.above.net [64.125.28.69]
10 32 ms 31 ms 32 ms 64.124.196.38.allocated.above.net [64.124.196.38
]
11 36 ms 36 ms 35 ms ip-208-109-112-153.ip.secureserver.net [208.109.
112.153]
12 29 ms 29 ms 30 ms ip-208-109-112-142.ip.secureserver.net [208.109.
112.142]
13 33 ms 32 ms 32 ms ip-216-69-188-33.ip.secureserver.net [216.69.188
.33]
14 29 ms 31 ms 31 ms p3slh047.shr.phx3.secureserver.net [68.178.254.1
98]
15 32 ms 34 ms 38 ms p3slh047.shr.phx3.secureserver.net [68.178.254.1
98]

Trace complete.

C:\Users\Matt>