Outlook Send/Rx error w. NOD32

Hi,
Hope someone has some ideas on this one.

I've got Outlook 2002 SP3 and ZoneAlarm Pro running on XP Pro SP2. Everything's got the latest patches I can find.

In Outlook when I hit Seed/Rx, Outlook can't connect sometimes and I get an error. I'd copy the error in but it's behaving as I write this but it didn't twice in the last 15 mins.

I can connect every time if I disable NOD32 (v2) but then there's no AV protection....

Any ideas anyone? Help appreciated!

 

watch this > https://www.wilderssecurity.com/showpost.php?p=450639&postcount=40

ignore step3...

 

Thanks gnervt,

Q: won't this get lost again when PC is rebooted?

My Imon > Setup > Misc tab set exactly per the link.
Did step 1 & 2, clicked OK to repair.
Got a message saying "changes made, reboot needed to take effect".
Rebooted, got the problem again 1st go!
Then closed NOD32, ran the Send/Rx again, no problem, it connected fine.
Restarted NOD32, ran the Send/Rx again, no problem, it connected fine.

Could it be order ZoneAlarm & NOD32 start in? I see them shuffle around in the system tray each reboot....

PS: Here's the error:
Task '{emailaccountname} - Sending and Receiving' reported error (0x8004210A) : 'The operation timed out waiting for a response from the receiving (POP) server. If you continue to receive this message, contact your server administrator or Internet service provider (ISP).'

 

You could try to set a longer time-out setting in Outlook. Go to your POP account settings, it should be under advanced or something

 

Thanks SSK,
Timeouts under tools> email accounts>view/change> more settings>adv. tab are set to one minute.

Another info byte & symptom:
I have three email accounts set to send/Rx together. Sometimes all three blast through in a second or two, other times one or two work & the others dont.

 

I would tend to see how things now run for the next day or so, given that you have used the "Repair" feature within Nod32 the problem may now be fixed.

Let us know how you go...

Cheers

 

Blackspear,
Got it right back on reboot after the repair.
Left it alone for a while ~5 mins just now, then it worked again.

Does the ZoneAlarm/NOD startup idea lead anywhere useful?

Thanks for the help....

 

Hmmm, I had some problems like yours (different Firewall though), but solved them by setting time-out to 2min 30 or so. Could you try that and see if it helps?

 

Unfortunately, no, not at all, I have run Nod32 and ZoneAlarm for 3 years on my 2 home PC's, and have set it up on hundreds and hundreds of PC's without an issue...

Hang in there we will get to the bottom of it. Try SSK's suggestion.

Cheers