plittlefield

After installing 4.0.85.0 I am experiencing an error when trying to view man pages in the terminal shell. plittlefield@paully-laptop ~ $ (paully-laptop) man wget error[3dba0000]: Cannot connect to /tmp/esets.sock: Permission denied error[3dc40000]: Cannot connect to /tmp/esets.sock: Permission denied man: command exited with status 159: (cd /usr/share/man && /usr/lib/man-db/zsoelim) | (cd /usr/share/man && /usr/lib/man-db/manconv -f UTF-8:ISO-8859-1 -t UTF-8//IGNORE) | (cd /usr/share/man && preconv -e UTF-8) | (cd /usr/share/man && tbl) | (cd /usr/share/man && nroff -mandoc -rLL=161n -rLT=161n -Tutf8) Ubuntu 18.04 ESET NOD32 Antivirus 4 Business Edition 64-bit 4.0.85.0 (changed from 4.0.87.0 following the 'web browser bug')

+1 I am uninstalling 4.87 now.

I have this error now on one of our Windows Server 2012 Standard computers with ESET File Security 6.5.12014.1 As you can see from the attached screenshot, the network ERA has pushed the Policy out to the Server. Interestingly enough, we have 3 other 2012 servers with the previous version ESET File Security 6.5.12014.0 which do not have this error!

I've got this on my Windows Server now when upgrading from 4.5 to 6.5... "ERA SoftwareInstallation: Installation need to allow reboot." ...so, what's the solution?

Thanks.

Yes! That worked and Agents on clients outside the company LAN can now see the server inside the LAN. Thanks!

Is it possible to export the Policies applied to one computer to another laptop outside of the company LAN? We have a laptop which has the incorrect Policy for the ERA Server IP Address and FQDN. How can we change the policy to that laptop?

Thanks. I have found 2 useful web pages from ESET on this very subject and will try today. https://support.eset.com/kb3304 https://support.eset.com/kb6130

Should an ERA Agent be able to communicate with the ERA Server when outside the office LAN?

...which it is failing on because it keeps changing the SEAT name... this is now up to DT13.domain.com-11

So, I reinstalled the ERA Agent from the .bat file and rebooted the desktop computer. DT13 is now showing up in ERA and is trying to Activate with a Licence...

I have checked the logs and these messages are shown... CReplicationModule 2017-Aug-04 11:58:50 CReplicationManager: Replication (network) connection to 'host: "eset1" port: 2222' failed with: Unable to resolve any endpoints.resolve: (0x2afc), The requested name is valid, but no data of the requested type was found. Scope Time Text Last replication 2017-Aug-04 11:58:50 Error: CReplicationManager: Replication (network) connection to 'host: "eset1" port: 2222' failed with: Unable to resolve any endpoints.resolve: (0x2afc), The requested name is valid, but no data of the requested type was found Peer certificate 2017-Aug-03 16:49:24 Error * Agent peer certificate with subject 'CN=Agent at *, C=US' issued by 'CN=Server Certification Authority, C=US' with serial number '01073d9ca96bea4874b2a3fXXXXXXXXXXX' is invalid now (NodVerifyTrustResult: 42, NVT_NotTrusted, X509ChainStatus: 0x10000, X509CSF_PartialChain) * Peer certificate may be valid but can not be verified on this machine * Check time validity and presence of issuing certification authority ...which is really strange because the other 45 computers are using the same ERA Certificate!

Out of the 45 computers managed with ERA 6.5 there is 1 computer that just refuses to complete. I have tried 3 different ways to install the software, different ways to register the licence and it does not complete properly. If I install the Agent on its own (windows .bat file), it shows in ERA. It will not install Endpoint via ERA push. If I install the Agent via the standalone installer, it does not show in ERA. It will not activate via ERA or Admin login. If I install the Agent and the Endpoint software via the all-in-one installer with Agent already installed, it fails to install. If I install the Agent and the Endpoint software via the all-in-one installer, it does not show up in ERA or Activate. I have tried using the ESET AV Remover, clearing the Windows Registry, resetting the winsock, testing DNS, powering off for 5 minutes and a complete fresh install of Agent and Endpoint using Windows 7 True Administrator. None of it works. I must stress that this problem is just with 1 computer (and it IS numbered 13!). Can anyone help? Thanks!

Thanks Martin, I have signed in from my work email and opened a Support Case. They have just replied and asked me for a screenshot... so fingers crossed. Regards, Paully

OK, thanks. Where do I find the agent.db file? (sorry, newbie alert! :-)