[Jwarne]

Hello,
Yesterday, one of my coworkers asked me to put a second existing account on her Outlook Client, so she could check the e-mail for both. When I helped her, the password for the second account was incorrect so it failed to connect. I deleted the second account from her client using Tools > Accounts. I did not touch her personal account, nor her properties and settings.

Since then, she has gotten the following error:

"The connection to the server has failed. Account: 'mail.setio.org' server
'mail.setio.org', Protocol SMTP, port 26, secure (SSL): No.socket error: 10060, Error Number: OX800ccc0e"

Immediately, I accessed the computer for our Director of Operations, who is able to receive mail, and ensured that their server settings were identical. Everything was the same, except for their account information (login, password, etc.). I did a google search for Error Number: 0x800CCC0E, but all the 'walkarounds' are for Microsoft Exchange Servers and SMTP Port 25. Our server is just a local wireless network and operates on Port 26. All the other computers that connect to that mail server use Port 26, so the Port shouldn't be an issue. The only thing that I can think of is that some other program might have started using that Port? Please let me know.

Can anyone suggest any troubleshooting?

[Advertisements]

Error code 0X800ccc0e is a failure to connect to a server. This is almost always caused by a temporary outage on the provider's end. Therefore a solution is to try again later. It can also be caused by firewall software.

[Neil Jones]

Error code 0X800ccc0e is a failure to connect to a server. This is almost always caused by a temporary outage on the provider's end. Therefore a solution is to try again later. It can also be caused by firewall software.

[Angela Chelson]

Hello,
Yesterday, one of my coworkers asked me to put a second existing account on her Outlook Client, so she could check the e-mail for both. When I helped her, the password for the second account was incorrect so it failed to connect. I deleted the second account from her client using Tools > Accounts. I did not touch her personal account, nor her properties and settings.

Since then, she has gotten the following error:

"The connection to the server has failed. Account: 'mail.setio.org' server
'mail.setio.org', Protocol SMTP, port 26, secure (SSL): No.socket error: 10060, Error Number: OX800ccc0e"

Immediately, I accessed the computer for our Director of Operations, who is able to receive mail, and ensured that their server settings were identical. Everything was the same, except for their account information (login, password, etc.). I did a google search for Error Number: 0x800CCC0E, but all the 'walkarounds' are for Microsoft Exchange Servers and SMTP Port 25. Our server is just a local wireless network and operates on Port 26. All the other computers that connect to that mail server use Port 26, so the Port shouldn't be an issue. The only thing that I can think of is that some other program might have started using that Port? Please let me know.

Can anyone suggest any troubleshooting?

Hello Jwarne,

This thread is pretty old, but there is far from any decent solution or reason for identifying your problem here. The Outlook error is very very general in nature. So many things can cause this to happen. The error basically means that your unable to connect to the outbound server address listed. Most of the time, this prevents you from reaching the incoming server address as well.

I had this happen not too long ago myself. I found out it wasn't my fault, it was because I was connected to the MSN network at the time. This error is very very rare though. I would suggest running through this site that has a step by step tutorial for fixing this. This is what I bookmarked when I fixed my Outlook Express email client when I was having the 0x800CCC0E similar problem.

Link to website:
0X800CCC0E Outlook Tutorial

To me it sounds like the ISP your co-worker is using may have begun to block standard port 25 to prevent spam. More and more ISP's even to this day are jumping on the band wagon, forcing you to use ports 26 or 587. I could be wrong and there could be other issues here at work. This is why I suggest a walk through like the example listed above. Good luck fixing it. If you still can't resolve it after going over the research, you can send me a PM or email me here: [email protected]

Regards,