Norton Internet Security 2005 [NIS 2005] and 0x8004210A

[Steve]

Since Symantec does not want to post this, I am. My system has been
getting the POP3 timeout error 0x8004210A for the last three days. This
has completely stopped email on every one of my accounts.
Incommunicado. Caput.

THERE IS A SOLUTION:

If you are getting this error and similar time-out errors on POP3
accounts, here is the resolution that Symantec proposes.

Go to NIS 2005 Personal Firewall and click on the configure button.

Go to the Programs Tab.

Look for Microsoft Outlook and Microsoft Outlook Express in the scroll
box at the bottom of this dialogue.

Change Internet Access Column to "Permit" and Category to "General."

Restart Outlook.

I hope this spares people the agravation I endured to find this out.
If the problem occurs again, I will try to let you know.

 

[doco]

Thanks - this indeed is a life saver. Norton is usually a great product
until you have a problem. They are IMPOSSIBLE to contact - virtually no
product support. That is unless you pay the REDICULOUS price of $29.95 (3/4
the cost of the software) per incident.

For this reason alone when my license runs out I am going elsewhere for my
needs!

 

[Steve]

Thanks - this indeed is a life saver. Norton is usually a great product
until you have a problem. They are IMPOSSIBLE to contact - virtually no
product support. That is unless you pay the REDICULOUS price of $29.95 (3/4
the cost of the software) per incident.

For this reason alone when my license runs out I am going elsewhere for my
needs!

 

[Steve]

Here it is January 11, a little more than one month after I spent three
days trying to find the solution to this problem and once again it
rears its ugly head.

I am, once again, getting the 0x8004210a error message on all my
accounts, even though I check the settings I outlined in my earlier
note and they are all "properly set" according to Symantec.

Here is what probably happened. Either Symantec updated their software
OR the dumb Microsoft "Networking Wizard" that activated my Windows
Firewall screwed up the settings. Crap.

Shame on Symantec for not resolving this pronto.

Shame on Microsoft for hosing other peoples' products.

 

[aluckyguess]

I hate norton

Here it is January 11, a little more than one month after I spent three
days trying to find the solution to this problem and once again it
rears its ugly head.

I am, once again, getting the 0x8004210a error message on all my
accounts, even though I check the settings I outlined in my earlier
note and they are all "properly set" according to Symantec.

Here is what probably happened. Either Symantec updated their software
OR the dumb Microsoft "Networking Wizard" that activated my Windows
Firewall screwed up the settings. Crap.

Shame on Symantec for not resolving this pronto.

Shame on Microsoft for hosing other peoples' products.

 

[Steve]

I downloaded updates shortly after my last post and the problem
disappeared again! It seems that this problem was fixed by Symantec and
I applaud them for so doing!

Communicating with Symantec is still a significant issue. "The
electronic wall" between users of software and companies must come down
sooner or later. The "we are so big we don't need to care" attitude is
pretty bad all around.

I like the products [generally], but do not like the lack of personal
responsiveness.