View Single Post
  #3  
Old June 28th 07, 06:52 PM posted to microsoft.public.windows.inetexplorer.ie6_outlookexpress
Dr. Shrinker
external usenet poster
 
Posts: 4
Default Can't send: error message 0x800CCC6F


Thanks for your input. You're right, I spent another 20 minutes with a
clueless tech this morning (trying to get me to re-enter all my OE settings
AGAIN). Of course, "level 2" techs are only available 9:00 to 5:00 and I have
to have a job to pay for that expensive cable internet service...


"N. Miller" wrote:

On Thu, 28 Jun 2007 00:24:00 -0700, Dr. Shrinker wrote:

"N. Miller" wrote:


On Wed, 27 Jun 2007 22:08:03 -0700, Dr. Shrinker wrote:


Just today I am unable to connect to my SMTP server to send email. POP works
fine. The server works if I access it through my ISP's webmail service.

Here's what happened: I had to take my system apart a couple days ago
(carpet installed) and, when I reconnected everything today, the first thing
that happened was AVG antivirus downloaded a HUGE update. I then went to send
an email and got the message:
An unknown error has occurred. Account: 'chrisnsue', Server:
'smtp.west.cox.net', Protocol: SMTP, Server Response: '554
fed1rmimpo02.cox.net bizsmtp connection refused from 68.5.17.118', Port: 25,
Secure(SSL): No, Server Error: 554, Error Number: 0x800CCC6F

Here's what I've tried: Doublechecked all my account names are accurate and
have the right server names entered. Uninstalled and reinstalled AVG, this
time without the email scanner. Turned firewall off. Uninstalled and
reinstalled OE6. Turned firewall back on. Nothing changes. The error comes
IMMEDIATELY on clicking "send," so it's not like I'm having trouble finding
the server.

Google and microsoft.com have been no help whatsoever. This error code is so
ambiguous that I haven't found any useful articles anywhere. Any ideas?

"fed1rmimpo02.cox.net bizsmtp connection refused from 68.5.17.118" is hardly
"ambiguous"; in fact, it is quite clear. What isn't clear is why this is
happening. I have been assured by Cox gurus that they don't, and won't ever,
consider requiring SMTP AUTH like other providers. But I have received spam
from Cox 'smarthosts', the MTAs which relay for Cox customers. I have to
wonder why they are refusing connections from there own customer IP
addresses. Assuming [68.5.17.118] that is your Cox assigned IP address.

This is not so much an MSFT issue as a Cox issue. You will need to take this
up with Cox support.


I've already spent a great deal of time on the phone with Cox. They say that,
because I can connect via Webmail, it's not a server issue; it's an OE issue.
The "tech" was completely perplexed by this error message.


Cox tech support is clearly incompetent. Web access to email is not the same
thing as client access to the message submission server. If MSOE was
reporting, "Server not found", that would be an MSOE issue. But MSOE is able
to find the server, and to attempt a connection to the server; it is the Cox
mail server refusing to accept the connection. As I stated, the only
question is, "Why?" Only Cox can answer that.

Maybe you can check with them he

http://www.dslreports.com/forum/coxhsi

I know that there is a Cox technician who reads the forum...

--
Norman
~Shine, bright morning light,
~now in the air the spring is coming.
~Sweet, blowing wind,
~singing down the hills and valleys.

Ads