taylor.treece

I did check the logs on the server and did not notice anything about it being overloaded. I am able to ping the server from the agent machines. But I have noticed the above error message on all of the client machines' trace.log files about the timeout with the server connection. Do you have any suggestions on what specific to check? Or would you like me to attach any of the log files here? Also we were planning on upgrading our server to the following package: ESET FILE SECURITY FOR MICROSOFT WINDOWS SERVER; VERSION 7.0.12018.0 FOR WINDOWS (WINDOWS SERVER 2016, 2012 R2, 2012, 2008 R2, 2008), LANGUAGE EN_US Do you think that may help resolve the connection issues between the server and clients?

Good Morning, I have been trying to set up an automated Client Task within our ESET Remote Administrator portal to automatically update some of our machines with the new V7 of the ESET Endpoint: (ESET Endpoint Security; version 7.1.2045.5 for windows (Windows 10, 8, 7, Vista), language en_US) For some reason after setting the Client Tasks and trigger, the tasks never run or even attempt to run. They remain in the "Planned" status and never show up in any of the logs or reports as to starting/succeeding/failing. The scheduled time just comes and goes with nothing ever happening. After doing some research I found this previous thread: https://forum.eset.com/topic/9338-client-tasks-not-starting/ where it looked like someone was encountering the same problem that I was. After checking the logs on the client machine where this was supposed to happen I noticed the same errors occurring: CReplicationManager: Replication (network) connection to 'host: "my.eset.server.ip" port: 2222' failed with: The connection will be closed due to timeout Is this the reason that the Client Tasks are not running? How would I go about fixing this problem? Would I need to create a new installer and run it in repair mode on our ESET server machine? Thanks, Taylor Treece