View Single Post
  #4  
Old February 19th 06, 10:59 PM posted to microsoft.public.outlook
TufftyBob
external usenet poster
 
Posts: 9
Default continually getting send/receive errors using outlook 2002

Hi Brian,
Thanks for all your advice, including letting me know that it is my ISP who
is the server administrator.

I will try the links you provided and hope they shed some light on the true
meaning of those errors.

regards,

Tufftybob

"Brian Tillman" wrote:

TufftyBob wrote:

Does anyone know why I am continually getting send/receive errors
when trying to send an e-mail. I can receive e-mails from virtually
anybody that is not blocked by Norton Anti-Spam(Norton Internet
Security 2005). My account is a pop3 account with the 'Orange' mobile
phone network, therefore it has an ' address. I have
tried 'repairing' outlook from add/remove programs - this did not fix
the problem. Neither did uninstalling and re-installing (also from
add/remove programs) this time it only allowed me to send a test
e-mail to my ' address and one other already written, then I
got the error messages again, within less than 90 seconds!


Scanning incoming mail with a Symantec problem can lead to this.

The error messages are numbered as follows:

0x800CCC0F; 0x80042109; and 0x8004210B. The text which follows all
three error numbers says to contact my server administrator or ISP if
the problem continues. I am the only user of this computer, so ther
is no 'administrator to contact.


Sure there is. Your server administrator is your ISP. The errors you
describe are typical when add-in software, like a mail scanner or a
firewall, is interfering with the communications path between Outlook and
the server(s). These may give you insight:
http://www.google.com/search?q=0x800CCC0F
http://www.google.com/search?q=0x80042109
http://www.google.com/search?q=0x8004210B

I have tried (at the suggestion of someone who answered my query on
an aol message board) changing the outgoing server port number from
25 to 587 but this made no difference, (except to present me with yet
another error message) either so I changed it back to the default 25.
I have also tried 'test account settings' in tools, e-mail accounts,
view or change etc, which tells me that the sever has been found but
there has been or there was no response from it, or outlook is
waiting for a response.


Are you properly authenticating to your servers, both the POP and SMTP?

Could the sever in question be the 'Orange' sever or the AOL sever?


Whatever servers are named in your account settings.

I have contacted my ISP - AOL - who say that the problem must be with
the outlook software,


Of course they would.

but when I get these send/receive errors I
almost always can't send from my aol account either.


And what do they say when you tell them that you receive the same errors
from their software with no Outlook involved?

Norton Internet Security 2005 and Norton System Works Premier 2005 -
fully updated
AOL 9.0 for Broadband
Windows 'Defender' (Beta 2) - Fomerly Microsoft Anti Spyware, AOL
Spyware Protection, Adaware SE 1.06, Spyware Doctor 3.2, Spyware
Blaster 3.5.1, all fully updated, plus Free Internet Eraser 2.05 and
the latest free version of CCleaner.


Try disabling all AV and antispam software temporarily.

When this problem started I had also had Word 2002 as part of Works
Suite 2005 installed as well as Office XP sp3 with some optional
updates. Microsoft Anti Spyware - fully updated, was installed at the
time, not Windows Defender. At the time of this problem starting I
was also getting another error message when attempting to connect to
microsoft update: 0x800A1391, as well as not being able to log in to
the .net passport feature so I could not even ask for help via these
communities. The problem started with a vengeance a couple of weeks
ago and after some fiddling as well as contacting aol to no avail,
it seemed to 'fix itself', and then come back again about three
times. Now nothing seems to make any difference.


My experience with AOL, though some time ago, proved to me that AOL doesn't
play nice with any networking settings and really screwed my PC up.
--
Brian Tillman


Ads