My Turn For Email Troubles

[savage3e]

I've seen a few posters having problems similar to mine, and have tried looking into their solutions with no luck. So I figured I'd post here and see if you guys could lend me a hand as well.

 

I'm currently pulling email from 7 different domains all hosted on Server39. 1 domain is accessed through Outlook Express; 1 domain is accessed through Mozilla; 1 domain is accessed through Thunderbird; and 4 domains are accessed through Outlook. Over the past week or so one specific domain (savagegames.org, which is one of 4 accessed through Outlook) has experienced more downtime than not. I can access the remaining 6 domain's email without difficulty but get frequent errors when attempting to access this domain's email.

 

>Error as follows:

Unable to connect to the server: (Account: 'SavageGames Mail', POP3 Server: 'mail.savagegames.org', Error Number: 0x800ccc0e).

 

I cannot ping any of these 7 domains locally, nor can I trace route to them. Ted's Webtools shows that each domain has the same statistics; irresolvable at 3 US NameServers and their related MX Servers. However, I can access all 7 domains from each of 5 machines on my local network via web browser, and can access webmail for all 7, including the domain that returns errors within Outlook.

 

I have made no changes to the domain in question since becoming a TCH customer in October of 2003 and have had no email problems until this past week. The domain is not due for renewal for nearly a year, and shows the proper name servers on file with the registrar (Network Solutions).

 

All that said, can you guys see any reason why this would be happening or any means of fixing this issue?

 

Thanks in advance.

[TCH-Bruce]

I just did a whois on this domain and noticed that your nameservers are entered in reverse. I would switch them around.

 

You say you can access the account with webmail so the problem is most likely not at the server but somewhere between you and the server.

 

Without being able to run a tracert you will not be able to determine where the bottleneck lies.

[savage3e]

I just did a whois on this domain and noticed that your nameservers are entered in reverse.  I would switch them around.

<{POST_SNAPBACK}>

Logging in to my Network Solutions Account Manager I see that all of my domains are set up with NS1.TOTALCHOICEHOSTING.COM as Name Server 1 and NS2.TOTALCHOICEHOSTING.COM as Name Server 2. Should these be switched, or is the whois reporting erroneously?

 

You say you can access the account with webmail so the problem is most likely not at the server but somewhere between you and the server.

 

Without being able to run a tracert you will not be able to determine where the bottleneck lies.

<{POST_SNAPBACK}>

That's what I was afraid of. Is it at least weird that only one account out of seven is having this issue?

[TCH-Bruce]

NS1 should be server 1 and NS2 should be server 2. Guess the whois just reported them out of order. This is how they are listed when I looked.

 

Name Server:NS2.TOTALCHOICEHOSTING.COM

Name Server:NS1.TOTALCHOICEHOSTING.COM

[savage3e]

Well, I guess that's not the problem then. Thanks.

[TweezerMan]

I cannot ping any of these 7 domains locally, nor can I trace route to them.

<{POST_SNAPBACK}>

I have no problem performing a ping or trace route to savagegames.org. Assuming it's not a temporary problem, it looks to me like something is blocking you from sending out ping or trace route packets, like a firewall on your PC, LAN, or perhaps your ISP.

[savage3e]

I have no problem performing a ping or trace route to savagegames.org.  Assuming it's not a temporary problem, it looks to me like something is blocking you from sending out ping or trace route packets, like a firewall on your PC, LAN, or perhaps your ISP.

<{POST_SNAPBACK}>

Looks like its something my ISP has recently put in place. I'm not sure what the benefit of such a thing would be, but at least there's one question answered.

 

Also, email from the troubled domain has begun flowing to my desktop again. I'm not sure what caused the problem in the first place, nor am I sure why its suddenly working again. Hopefully this won't continue for too much longer, since the "outages" are getting lengthier each day.

 

Thanks guys.

[TCH-Bruce]

Glad it's flowing again.