Has anyone seen issues with the Norton version 188.8.131.52 failing AV checks? Currently running 8.2R9 with ESAP 3.1.5.
Same. We have a couple of users that just reported issues with Norton version 184.108.40.206 failing AV checks. We're on ESAP 3.1.9.
Same with HostChecker 220.127.116.11981. I've also posted the problem at https://community.norton.com/en/comment/7838231#comment-7838231, and a reply points out that the Norton executable filename has been changed to "nortonsecurity.exe" as of 18.104.22.168 (23-Jan-2018). So PulseSecure likely needs to update HostChecker to allow for this change in the Norton executable filename.
Can anyone from PulseSecure tell us when this change will be made, and in what version of HostChecker?
I'm also having this isssue as well and would appreciate Pulse Secure's help on this issue.
When will this be fixed? This is creating a serious hardship for users of the Network Connect VPN solution.
Do the Pulse Secure people check these forums? This issue is really annoying. Host Checke is asking me to install Microsoft Windows Security!!! I have Norton, and I should be able to access my employer's VPN. Here is what someone from Norton posted in their forums:
"Jan 23rd was the date that version 22.214.171.124 was released. Your Host Checker needs to be updated to accept the new version. I seem to remember that the Host Checker needs to be updated every time that Norton comes out with a new patch. There is an Announcement pinned to the top of this Board which describes the new things that were updated. Perhaps that description will be enough for the Host Checker to update it's program.
The change that may be bothering the Host Checker is now the main Norton .exe is now called nortonsecurity.exe. The HostChecker now needs to look for that to see that the program is running. I would say that is what needs to be changed. Previously, I believe it was called something like nis.exe for Norton Internet Security program"
The Pulse Secure Host Checker uses ESAP packages to detect Anti-virus products and their status. These are built using OPSWAT SDKs so whenever a product fails to be detected correctly we need to obtain the ESAP diagnostic file via a Pulse Secure Support case (kb.pulsesecure.net/articles/Pulse_Secure_Article/KB28146/) and report any errors to OPSWAT who then create the fixes in their SDKs which are then picked up by us to create a new ESAP package.
There are two current Problem Reports (PR) open for Host Checker failing to detect Norton Security suite v126.96.36.199 in the v4 SDKs (PRS-361134 and PRS-361149) which are both waiting on OPSWAT to come up with a fix.
Any recent new information or interesting developments regarding this? Several users having the same problem here.
We've tested ESAP file 3.2.2 and it appears to have fixed this issue. I'm being told by Pulse support that file 3.2.3 is their supported fix and that is should be out this week.
Thanks, valcon5 - just what we've been waiting to hear.
I'll include this in the cross-posting on the Norton Community site (https://community.norton.com/en/forums/pulsesecure-hostchecker-ignores-norton-under-win10)