Possible conflict between NOD32 and ZAPRO

Hi all,

I used to run NOD32, before I moved over to Kaspersky around a year ago. I saw that NOD32 released a new version, and as my licence was due to expire, I thought I'd come back and use NOD32. I only moved away to try something different, but NOD32 always ran more smoothly for me, hence my return.

Unfortunately, since I installed it last night, I have had a problem.

My systems are Windows XP SP2, Zonealarm Pro 7 (latest version) and NOD32 v3 (latest version).

Several web sites (Hotmail, CIX, etc...) now seem to lose track of their login cookies, which results in either not being able to login, or being kicked out when I navigate within one of those sites.

When I disable HTTP checking within NOD32, then everything works fine. Just to say that everything was working fine before I installed NOD32 on three different machines, so the obvious common factor seems to be NOD32.

I would appreciate any light that can be shed regarding this issue. I have scoured the internet, and many links end-up at these forums, but the only conclusions I can draw is that there is a conflict between the two programs (some people seem to indicate issues, others don't appear to have any issues).

The only reason I am posting here is that the experience seems to be within these forums, so I'm sure this issue has already been discovered somewhere, and I'm hoping someone can push me in the best direction. Also, these issues have only arisen after installing the latest NOD32 on systems which have always used ZoneAlarm Pro.

Thanks in advance for anyone's assistance.

P.S. I have always blocked cookies within ZAPRO (and IE / FireFox), and then enabled them for specific sites.

 

Hello,
I use NOD32 v3.0.650 with ZAP 7.0.473 with only FW activated (and spy sites control) but no cookies filtering at ZAP level (only at IE7 or Firefox level).
NOD32 configuration is default one and an important point is active mode is not checked (web navigator under http checking)

Every thing is oK for me !
Regards

 

I encountered this problem with NOD v3 when it was first released last year and since then I posted extensively about this issue in this forum. This same problem involving blocked cookies from secure web sites happened on every one of my systems that had both NOD v3 and ZAP 7.x installed. Just like you explained I run ZAP and ZASS on different machines with the various ZA privacy settings enabled (mobile code control, cookie control, etc.). For those machines using both ZAP and NOD v3 the web sites requiring a secure login would not work properly and pages would become inactive while showing an error related to cookies being blocked.

Supposedly this conflict is related to the proxy based design of the NOD v3 real time scanning engine. Unfortunately I did not find nor was anyone able to provide a solution that solved this apparent conflict without disabling most of the ZAP privacy settings and/or most of NOD v3's web protection. The easiest thing for me to do was to simply use NOD v2.7.x which continues to work great along with ZAP and its enhanced privacy settings enabled. For the time being I have decided that as long as NODv2.7.x is supported by ESET with current signature database updates I will continue to use it.

 

Thanks for the replies Philippe_FR22 and SoCalReviews

This is the same conclusion I have arrived at based on the various posts regarding this matter and related issues. So, it looks like NOD32 v2.7.x...here I come

I'm not prepared to have to compromise my settings long-term, but I am prepared to wait and see what happens with NOD32 v3, especially as I know that I'm not alone. After all, NOD32 has always been top notch software!

Thanks again!

 

Using Nod32 ver 3 and ZAP 7.0.473 XP SP3.Using Blackspears settings. no issues here so far.

 

Thanks for the input but unless something major changed in the design of the very latest version of ZAP this particular conflict still exists between NOD v3.x and ZAP v7.0.x.

I spent months trying to find a solution or work around for this issue and determined that there was none. There is no question that the proxy based design of NOD v3 conflicts with the ZAP enhanced privacy settings. Certainly you can disable most of the ZAP privacy settings or disable some of the web based scanning in the NOD v3 advanced settings to make it work but that also lowers the overall system security.

Also realize that your system could only appear to be working fine since this particular conflict shows up only when you have many of the ZAP privacy settings enabled and it only effects the cookies on secure web sites that require you to login. The only real solution I know that eliminates this conflict completely is to use NOD v2.7.x which still is an excellent security program.