pipboy3000 3 Posted October 12, 2015 Share Posted October 12, 2015 I see a lot of Mac OS clients (different versions) with this event warning in the Admin Console "Error updating Antivirus modules: Could not connect to server". It's worth to mention that not all Mac OS clients have been affected and the message can't be pin down to one specific version of OS. At the same time, all clients report up-to-date database files. Problem does not affect Windows based machines. ESET NOD32 4.1.97 Server 5.2.22 Any ideas? Link to comment Share on other sites More sharing options...
ESET Moderators TomasP 316 Posted October 13, 2015 ESET Moderators Share Posted October 13, 2015 Hello, I can see you are using rather old versions of the client and the server. I suggest upgrading to the latest versions which include various bugfixes and new features as well. Link to comment Share on other sites More sharing options...
pipboy3000 3 Posted October 13, 2015 Author Share Posted October 13, 2015 (edited) Updated to the latest version 5.2.26. I will clear the last warning tab and see if the message comes back. Edited October 13, 2015 by pipboy3000 Link to comment Share on other sites More sharing options...
ESET Moderators TomasP 316 Posted October 13, 2015 ESET Moderators Share Posted October 13, 2015 Yes, our licensing system has always worked this way. You only pay for a product, not a specific version. Once you buy a license for a product, you can use any of its versions, including future new releases. [previous message was edited, it originally asked whether the update is free] Link to comment Share on other sites More sharing options...
pipboy3000 3 Posted October 14, 2015 Author Share Posted October 14, 2015 OK, I've updated all to the latest version, but the problem keeps reoccurring. Any ideas? Link to comment Share on other sites More sharing options...
ESET Moderators TomasP 316 Posted October 14, 2015 ESET Moderators Share Posted October 14, 2015 By "all" do you mean all clients? What product and version are they on now? Is there any error on the clients themselves, or just in the console? Link to comment Share on other sites More sharing options...
Megachip 5 Posted January 5, 2016 Share Posted January 5, 2016 Have the same problem on a 5.0.2242 Client. Others working. Client is shown in RA, so if connection on port 2222 working, why client reports on 2221 "could not connect"? Link to comment Share on other sites More sharing options...
Recommended Posts