Starting around June 27th we started getting reports from users of Norton 360 users that they could not log into the VPN. They're all have version 126.96.36.199. It appears that this version is not being detected as a supported AV product by Host Checker. We're on ESAP 2.9.2. We've had a handfull of reports so far.
Is anyone else seeing this issue? If so, what ESAP are you using? Thanks!
I was able to successfully roll users back to 188.8.131.52 until the issue is resolved.
Here is a Norton post showing the download links for the various versions of 184.108.40.206: [url]https://community.norton.com/en/forums/227-download-links[/url]
You can reverse engineer these to the correct version of 220.127.116.11 by changing the URLs, for example: http://buy-download.norton.com/downloads/2015/22.7/N360/US/N360-ESD-18.104.22.168-EN.exe becomes http://buy-download.norton.com/downloads/2015/22.6/N360/US/N360-ESD-22.214.171.124-EN.exe
I recommend using the Norton Uninstall tool to wipe all traces of the software before installing the older version. After installing 22.6, there is a setting that prevents the software from automatically upgrading back to 22.7.
In terms of other options, just yesterday some of our users with McAfee are unable to get in, and we advised them to switch to the free version of Avira until we get the McAfee issue resolved.
Thanks for the info. We're a little leery of asking people to roll back a version. The update that proke detection coencided with the Symantec AV product vulnerability. Rolling people back may be exposing them to that issue.
Anyone from PulseSecure have an ETA on the next ESAP?
Upload the package on the appliance at the following location:
# Authentication-->>End-Point Security-->>Host Checker # Scroll down and click on choose file, under "Manage Endpoint Security Assessment Plug-In Versions". # Check "Set as active after upload" and click on Upload.