Host Checker and Norton Antivirus 2009

[meh_]

Hi,

We are running v6.3R3 and have Host Checker running checking for supported A/V applications. One of our users at home has the latest version of Norton's 2009 (v16.2.0.7). Host Checker is complaining this user does not comply with policy. Looking at the A/V list on Host Checker it states Norton v16.x which I assume means this user is covered.

Why is she being denied access? She claims virus definitions are up to date and that realtime protection is running. Perhaps this version is not supported?

Thanks

[PVP_]

Meh:

What is the version of ESAP Activated on the IVE?

Thanks.

[WindowsAdmin_]

We are having the same issues. We are running 6.3R1-2 with esap 1.4.5. Any one have a solution to the problem?

Thanks,

Jonathan

[meh_]

I didn't realise I was running ESAP 1.4.1. I've just updated to 1.4.5 and am waiting for the user to test and let me know how it goes. Keep you posted.

[WindowsAdmin_]

I just got esap 1.4.6 BETA. I will be testing it in the morning.

[meh_]

I've just had confirmation from the user that it still does not work. Reading the documentation for 1.4.5 it looks like it should be supported. So any assistance would be great. Thanks

[haas_]

I have been fighting the same issue with Norton 2009, Norton 360 and now AVG Free 8.5.

Currently running 6.2R4 ESAP 1.45 the current Juniper AV checker flat out sucks in my opinion. I have had to stop checking for antivirus because 1/2 of the stuff my people use "doesn't comply with the policy" however according to the docs it does. As well I have the new "updates" number instead of DAT file age. I have had to change it to 10 because people are constantly being to told their stuff is not up to day. Juniper I hope you are reading this!

Message Edited by haas on 03-11-2009 06:48 PM

[meh_]

The only thing I can think of doing temporarily until Juniper gets their act together, is put a Host Checker rule in place that checks for whatever process is used for the Norton 2009 realtime scanner, and ensure that process is running. Not great cause it won't check if the definitions are up to date, but maybe it's better than nothing at this stage.

I'm having to this for eTrust at the moment.

Message Edited by meh on 03-11-2009 07:57 PM

[WindowsAdmin_]

The Beta 1.4.6 did not fix the issue. The users are still gettting "Reason: 'Norton AntiVirus 16.5.0.134 does not comply with policy. Compliance requires real time protection enabled and latest virus definition files.'."

Thanks.

[haas_]

Thank you for the update! Hopefully when it goes out of BETA they will have it fixed as this is really poor.