11-15-2011 12:31 PM
Recently upgraded ESAP to V1.8.0 so we could check ESET NOD32 Version 5.x. Check fails and says
ESET NOD32 Antivirus 126.96.36.199 does not comply with policy. Compliance requires real time protection enabled.'
So it recognizes the AV product but thinks that it does not have real time protection enabled. (Real time protection IS enabled. This is a default setting.)
Anyone else see this? I Suspect that this is a bug in ESAP. Working a ticket with JTAC but was hoping to see if anyone has the same problem.
11-16-2011 07:34 PM
Yes, you are on the right track. Please open a ticket with the JTAC to confirm if this is a BUG on the ESAP.
However, before opening the case with JTAC, please ensure to collect the below as the below will be needed by the JTAC.
- Dowload the "oesisdiagnose.exe" file attached to the case and copy the same to your "host checker" folder on the C
drive. The attached file is "OesisDiagnose.TXT" - Please rename is to "OesisDiagnose.exe" after download.
Normally, the location is the below:
C:\Documents and Settings\username\Application Data\Juniper Networks\Host Checker:
- Double click / execute the OesisDiagnose.exe file and it would give you a OesisDiagnose.log file.
- ESET NOD32 V5 installer file and the key if any.
- Screenshot of the ESET NOD32 V5 application showing all the detail of the software.
- Please also ensure to collect the client side logs from the computer for a failure session.
Please refer http://www.juniper.net/techpubs/software/ive/admin
Ensure to enable client side logging on the IVE under : Log/Monitoring - Client Settings - Settings - "Check / Enable" Host Checker
Hope the above helps you.
11-28-2011 10:58 PM
ESAP 1.8.1 is released: Could you please upgrade your ESAP and check if this resolves your issue?
Checksum : B5B9DE7F96846FB9721395EFCD6724E2
Supported Products List:
Please mark this post as 'accepted solution' if this answers your question that way it might help others as well, a kudo would be a bonus thanks
12-02-2011 10:21 AM
I am using ESAP V1.8.1 now and still have this issue:
'ESET NOD32 Antivirus 188.8.131.52 does not comply with policy'.
Any ideas when Juniper will resolve this issue?
01-03-2012 09:14 AM
Confirming this as a problem with ESAP 1.8.1 and NOD32 184.108.40.206 (latest versions as of this post).
Issue can be reproduced only if user is not an administrator on the local PC since Host Checker is unable to determine the real-time protection status (OESISDiagnose reports "FSRTP Status: UNKNOWN"). If user is an administrator, Host Checker passes without issue.
01-04-2012 06:40 AM
For ESET Smart Security 5.x , it has been requested by a customer and OPSWAT have informed us that they are attempting to validate and include support for it in ESAP 1.8.3 which is expected to be released in February 2012.
Until the support for ESET 5.x is added, as a workaround you can create your own custom Host Checker policy to detect the ESET application, please review http://kb.juniper.net/KB22348
To generate the Oesis diagnostic log file, you can also download the tool from the OPSWAT site:
* download the OESIS Diagnostic Tool (http://c3384790.r90.cf0.rackcdn.com/OESIS-Diagnose
* extract the files to the Host Checker directory (C:\Documents and Settings\<USER NAME>\Application Data\Juniper Networks\Host Checker for XP;
C:\Users\<USER NAME>\AppData\Roaming\Juniper Networks\Host Checker\ for Win7)
* run the OesisDiagnose executable.
This will generate a log file in the same directory.
01-04-2012 10:46 AM
Thanks for the info.
However, the information that I provided was for ESET NOD32 Anti-Virus 5.0.95 (not Smart Security), which is in the list of supported products since ESAP 1.8.0. It works fine, as long as you are logged into the local machine as an administrator.
01-05-2012 05:51 AM
Is the Juniper Installer Service (JIS) installed for the non-admin account? As it works for Admins it sounds like a permission problem and Host Checker has failed to install/access some components to detect the Real Time Protection.
If you uninstall Host Checker, install JIS as an admin and then connect does HC get re-installed and the HC policy pass?
See p.704 of the Admin Guide for details on JIS.
If it is still failing with JIS then client-side logs will need to be inspected to find out what is the problem, which would be better handled ina TAC case.