perryjay
One of the Ten
Premium
join:2002-01-25
Daytona Beach, FL
| Email problem
Are the email servers down again? I recently set my sister up for DSL. She has received email since then but for the last couple of days she is getting an error message saying socket error 10060 and error # 0x800ccc0e. I have also set her up with gmail and it is working fine.
--
Can I post now? |
|
NormanS
Premium,MVM
join:2001-02-14
San Jose, CA
 ·Pacific Bell - SBC
| said by perryjay  :...getting an error message saying socket error 10060 and error # 0x800ccc0e. There must be more context to that error message. At the least, a server name?
Those errors could be related to an incorrect server name, firewall issues with the ports, or AV scanning of email. Among other things. More details of the error (like the complete, unabridged verbose message) could help to narrow down a cause, and find a solution.
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum |
|
graysonf
Premium,MVM
join:1999-07-16
Fort Lauderdale, FL | reply to perryjay
Is she using mail.bellsouth.net for both incoming and outgoing servers? |
|
steveatl
join:2007-07-06
Decatur, GA | reply to perryjay
Haven't noticed any problems myself. |
|
NetFixer
Snarl for the camera please
Premium
join:2004-06-24
Murfreesboro, TN
 ·Vonage
 ·Cingular Wireless
·AT&T CallVantage
·AT&T Southeast
 ·Comcast
| reply to perryjay
I don't normally use the AT&T/BellSouth email, but I just did a telnet mail.bellsouth.net 25 and a telnet mail.bellsouth.net 110 test and I did not have any problems connecting.
--
We can never have enough of nature.
We need to witness our own limits transgressed, and some life pasturing freely where we never wander.
Test your firewall. |
|
CraigLouisville
@bellsouth.net
| reply to perryjay
I have been having the same issue since yesterday. I'm using Outlook 2003, and it times out trying to connect to mail.bellsouth.net. Attempts to telnet on both ports 25 and 110 time out. tracert times out.
If you can reach it and I can't, then the problem is in the network, probably with their DNS, but who knows? This has happened before, and I've been able to fix it by resetting my DSL modem and getting a new IP address. No luck this time. |
|
CraigLouisville
@bellsouth.net
| reply to perryjay
OK, fourth reset of the DSL modem fixed the problem.
My theory is that sometimes, what with all the mergers and such, I get an IP address that some parts of the network don't know are inside, so it blocks port 25 access.
It's just a guess, but this has happened at least a half dozen times over the past couple of years, and restarting the DSL modem (from its menu) fixes it. |
|
NetFixer
Snarl for the camera please
Premium
join:2004-06-24
Murfreesboro, TN
·Vonage
·Cingular Wireless
·AT&T CallVantage
·AT&T Southeast
·Comcast
| said by CraigLouisville :
I'm using Outlook 2003, and it times out trying to connect to mail.bellsouth.net. Attempts to telnet on both ports 25 and 110 time out. tracert times out...
said by CraigLouisville :
OK, fourth reset of the DSL modem fixed the problem.
My theory is that sometimes, what with all the mergers and such, I get an IP address that some parts of the network don't know are inside, so it blocks port 25 access...
That might explain not connecting to port 25, but as far as I know you can connect to mail.bellsouth.net for POP3 access from any network that does not do its own external port 110 blocking (as some corporate firewalls do).
The next time your problem shows up try connecting to 204.127.217.17 and/or 207.115.11.17 to eliminate a DNS lookup problem (or just do a nslookup mail.bellsouth.net command).
--
We can never have enough of nature.
We need to witness our own limits transgressed, and some life pasturing freely where we never wander.
Test your firewall. |
|
CraigLouisville
@bellsouth.net
| It's happening again. nslookup gives the same ip addresses as in the previous message. no ping, no tracert, no telnet to port 25.
It does connect to port 110, but I never get an OK response or any response to any command, and the connection times out.
I have no problem connecting to other pop3 servers, both with email and telnet. |
|
ruraltn
join:2008-05-16
Loudon, TN | No problem here. Both send and receive are OK.
--
www.east-tennessee-land.com |
|
NetFixer
Snarl for the camera please
Premium
join:2004-06-24
Murfreesboro, TN
·Vonage
·Cingular Wireless
·AT&T CallVantage
·AT&T Southeast
·Comcast
edit:
May 24th, @07:35PM
| reply to CraigLouisville
said by CraigLouisville :
It's happening again. nslookup gives the same ip addresses as in the previous message. no ping, no tracert, no telnet to port 25.
It does connect to port 110, but I never get an OK response or any response to any command, and the connection times out.
I have no problem connecting to other pop3 servers, both with email and telnet.
I have no problems here using mail.bellsouth.net, 204.127.217.17, or 207.115.11.17:
When doing the traceroute, where does the trace seem to stop responding? Posting the results might help with the diagnosis. Trying both of the IP addresses might also provide a clue.
Here is a sample of a traceroute to mail.bellsouth.net from my location using my AT&T/BellSouth connection:
Here is a traceroute to mail.bellsouth.net using my Covad connection (interestingly, it takes two less hops than the AT&T/BellSouth connection):
Here is a load balanced traceroute to mail.bellsouth.net. It uses either the AT&T/BellSouth or Covad connection depending on the load balancing algorithms in my router (interestingly, it also shows two fewer hops than the native AT&T/BellSouth connection). I am not really sure how valid this traceroute is since it does generate a new ICMP connection for each hop, and a normal POP3 or SMTP session should only open one, so this actual route would probably not really be used for a real TCP connection.
The point I am making with the above traceroutes, is that no matter how I attempt to access mail.bellsouth.net, I am able to make the connection. If you can not do so, finding out where the connection is broken will be the first step needed to diagnose the problem.
--
History does not long entrust the care of freedom to the weak or the timid.
-- Dwight D. Eisenhower
Test your firewall.
Smell the flowers. |
|
CraigLouisville
@bellsouth.net
| reply to perryjay
I am also unable to bring up helpme.att.net. tracert for both fails after the same node:
14 40 ms 40 ms 39 ms axr01msy-so-1-2-0.bellsouth.net [65.83.236.43]
15 47 ms 46 ms 45 ms xer01dfw-pos-3-0.bellsouth.net [65.83.236.169]
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
I am not going to waste any more time with this. I use my Web host's mail, and I've discovered that their SMTP server will work on a different port just for ISPs that block 25. I won't be able to see any mail AT&T sends me to my @bellsouth.net account, but that's their problem. |
|
NetFixer
Snarl for the camera please
Premium
join:2004-06-24
Murfreesboro, TN
·Vonage
·Cingular Wireless
·AT&T CallVantage
·AT&T Southeast
·Comcast
| said by CraigLouisville :
I am also unable to bring up helpme.att.net. tracert for both fails after the same node:
...
I am not going to waste any more time with this...
Sounds like a good plan.
FYI: helpme.att.net does not respond to ICMP for me either, but it is accessible via an http request, so your failed traceroute to that server was likely not related to not being able to ping/traceroute/telnet to mail.bellsouth.net.
Pinging helpme.att.net [144.160.11.35] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)
Minimum = 0ms, Maximum = 0ms, Average = 0ms
--
History does not long entrust the care of freedom to the weak or the timid.
-- Dwight D. Eisenhower
Test your firewall.
Smell the flowers. |
|
CraigLouisville
@bellsouth.net
| reply to perryjay
I mentioned helpme.att.net because, while I have no problems loading my.att.net in the browser, I time out when I click on the support link to get to helpme.att.net. That's what leads me to believe the issues are related.
I think this is a problem somewhere in their network, but I can't see how I can convince a first line support person of this. It will be an uphill struggle to convince them that there is even a problem, much less that the problem can't be fixed by reformatting my computer. |
|
anonyjane
join:2008-02-10
Billingsley, AL
| If you are able to access the email account through webmail, then as far as AT&T support is concerned, there is no problem. If you cannot send/receive emails in webmail, then they will be able to troubleshoot. As far as Outlook goes, if your settings are correct and the problem persists, they consider it a Microsoft issue. |
|
