Robindr 0 Posted November 21, 2018 Share Posted November 21, 2018 (edited) Goodmorning, Since yesterday my Endpoint Antivirus is giving the message "ESET LiveGrid not accessible" I haven't found any information regarding network related issues. Is there anything wrong ? Regards, Robin Also i am not able to update the software for 2 days now: Edited November 21, 2018 by Robindr Link to comment Share on other sites More sharing options...
Administrators Marcos 5,228 Posted November 21, 2018 Administrators Share Posted November 21, 2018 Please make sure that you have proxy server set up correctly in the advanced setup -> tools -> proxy server. If that's not an issue, check https://support.eset.com/kb332/ for a list of addresses and ports that need to be allowed on a firewall in order for Endpoint to work properly. Link to comment Share on other sites More sharing options...
Robindr 0 Posted November 21, 2018 Author Share Posted November 21, 2018 Hi Marcos, Both solutions I have double checked before I posted this message, Link to comment Share on other sites More sharing options...
TomTomTom 2 Posted November 30, 2018 Share Posted November 30, 2018 (edited) Hi there, I have the same problem on some (now 2) machines..... Checked everything. seems to be OK, but still the problem. On one machine (with internet connectivity) I disabled the firewall, then it worked. But the other one has no Internet connection, so disabling the firewall gave no solution. CU Edited November 30, 2018 by TomTomTom Link to comment Share on other sites More sharing options...
ESET Staff Gonzalo Alvarez 66 Posted November 30, 2018 ESET Staff Share Posted November 30, 2018 Hello @TomTomTom Please reset the firewall to default and be sure is on "Automatic mode", then restart the computer. Let us know if the issue was resolved or not. Link to comment Share on other sites More sharing options...
Steve Eckes 1 Posted November 30, 2018 Share Posted November 30, 2018 Hi, I have the same problem as of this morning. Over 300 machines in three locations. We have not made any changes to the network firewalls Link to comment Share on other sites More sharing options...
Administrators Marcos 5,228 Posted November 30, 2018 Administrators Share Posted November 30, 2018 Try temporarily changing logging verbosity to diagnostics and check the ESET Event log for more details about the error. Link to comment Share on other sites More sharing options...
Steve Eckes 1 Posted November 30, 2018 Share Posted November 30, 2018 We rebooted the ESMC server and the issue was resolved. In the client logs the problem seemed to start with the updated Detection Engine version 18466. After the server reboot the detection engine was updated to version 18468. At the same time the problem resolved itself. Don't know if the two events are related. I appreciate your quick response Marcos. Link to comment Share on other sites More sharing options...
TomTomTom 2 Posted December 3, 2018 Share Posted December 3, 2018 This morming I had about 40 machines with the problem. For me also a reboot of the ESMC server solved the problem. Mysterious but not satisfying Link to comment Share on other sites More sharing options...
Administrators Marcos 5,228 Posted December 3, 2018 Administrators Share Posted December 3, 2018 The ESMC server has nothing to do with Endpoint's communication with LiveGrid servers and restarting the ESMC server cannot affect it in any way. I rather suspect that the server got into a state when it stopped accepting replication attempts from agents for some reason. Should you run into the issue again, check if a troublesome machine has recently connected to the ESMC server. Link to comment Share on other sites More sharing options...
TomTomTom 2 Posted December 3, 2018 Share Posted December 3, 2018 In the ESMC console the timestamp of last connection was minutes before. So I think they were still talking to the server, but receive not the newest modules. Link to comment Share on other sites More sharing options...
Administrators Marcos 5,228 Posted December 3, 2018 Administrators Share Posted December 3, 2018 You can temporarily set logging verbosity to diagnostic on the client and in case the issue returns, check the ESET event log for more details about the failure. Link to comment Share on other sites More sharing options...
IT-KAV 1 Posted December 3, 2018 Share Posted December 3, 2018 Hello, we had same problem since thursday-friday. Restarting Apache proxy service on ERA server solved issue. Link to comment Share on other sites More sharing options...
ESET Staff Gonzalo Alvarez 66 Posted December 3, 2018 ESET Staff Share Posted December 3, 2018 Hello,@TomTomTom and @IT-KAV As @Marcos pointed, what you do and mention is a "workaround" not the solution for the problem. In order to find the root of the problem and find a permanent solution, we need logs to investigate. Please increase the verbosity of the logs and wait for the issue to reappear, if need contact more speed or dedicated team I suggeest contact your local ESET support to open a ticket. Link to comment Share on other sites More sharing options...
Recommended Posts