xyz 0 Posted October 8, 2015 Share Posted October 8, 2015 Hello All, After terrible experience with many errors and problems in ESET Remote Administrator Server version 6.1 we have got version 6.2.171.0 finally. It looks like it work like a charm. Everything seems to be working: Remote Agent install with no errors (from live agent installer) Remote install of ESET Endpoint Antivirus clients working (We've got some problems with activation, but new task "Activate product" solves the issue ) Workstation are updates with virus database successfully No errors in ERAC - just perfect but... on all workstation we can see one, the same error. On C:\ProgramData\ESET\RemoteAdministrator\Agent\EraAgentApplicationData\Logs\last-error.html we have line with: " CUpdatesModule 2015-Oct-08 09:44:13 PerformUpdate: Module update failed with error: Proxy server requires authentication. (error code 8194) " Every set of proxy setting at Agent, and Clients policy are the same. We set "proxy requires authentication" at policy, we set username and valid password. But above error always appear. Agent version - 6.2.190.0 Have You got aby idea what should we wrong ? Link to comment Share on other sites More sharing options...
Administrators Marcos 5,257 Posted October 8, 2015 Administrators Share Posted October 8, 2015 Is agent configured to connect through an existing proxy server or through Apache HTTP Proxy that you installed with ERA v6? Link to comment Share on other sites More sharing options...
xyz 0 Posted October 8, 2015 Author Share Posted October 8, 2015 Agent is connected through an existing proxy server (ISA Server). It is configured to use this proxy in agent policy. Link to comment Share on other sites More sharing options...
Administrators Marcos 5,257 Posted October 8, 2015 Administrators Share Posted October 8, 2015 Does Endpoint successfully download updates through the same proxy while authenticating using the same U/P? Link to comment Share on other sites More sharing options...
xyz 0 Posted October 8, 2015 Author Share Posted October 8, 2015 Yes, of course. Now i see on ISA Server monitoring that agent i trying to connect via port “80” and as “anonymous” user to hxxp://update.eset.com/eset_upd/era6/update.ver. They did not take policy settings of username, password and port. Other settings (connection time interval for example) are successfully implement. Link to comment Share on other sites More sharing options...
Recommended Posts