Conflict with ZoneAlarm

Yesterday I did a clean uninstall of ZoneAlarm Security Suite, followed by a new installation of it. While activating my settings for IM Security, I encountered a conflict with NOD32 which prevented me from blocking any of the covered IM applications. I do not use IM’s but I would prefer to lock them down anyway.

I find this a bit curious since I had those IM settings to block prior to the clean uninstall/install cycle with no conflict with NOD. The only difference being the order in which the applications had been installed. Previously, NOD was installed after ZoneAlarm.

The Internet Logs Ispconflict.txt clearly indicates the conflict to be with NOD32. I have implemented Blackspear’s extra settings for NOD by the way.

Any suggestions or insights would be most welcome.

 

Try repairing Winsock with this tool: Winsock XP Fix and then repair IMON

Let us know how you go...

Cheers

 

Took a quick look at the Winsock XP Fix link. For the record, I am not having connection problems. So before I go that route, I thought it might be helpful to post the contents of the Internet Logs Ispconflict.txt:

{28A4D8DA-E908-4C6F-A926-A66CC7AD3224}{28A4D8DA-E908-4C6F-A926-A66CC7AD3224} (NOD32)

I assume that NOD32 and ZA are fighting over that registry entry.

Just trying to avoid a bigger problem.

 

You should not see a bigger problem , you should see the problem fixed. I have seen several times where placing ZA on causes Winsock issues, and this tool fixes it.

Cheers

 

OK, I'll bite!

Thanks for the advice and I will post back here on the results.

Best regards,
RL

 

Looks like it worked like a charm!

I didn't even have to fix IMON, the Repair button was greyed out. So Winsock XP Fix did all the work.

I went into ZA and had no difficulties disabling all the IM Security settings.

Thanks very much. It is nice to know their are good people out there willing and able to help.

Best regards,
RL

 

My pleasure RL.

Cheers