Jump to content

Teun Althuizen

Members
  • Content Count

    7
  • Joined

  • Last visited

Profile Information

  • Location
    Netherlands

Recent Profile Visitors

430 profile views
  1. The agent never connected to the ERA server, so there isn't any successfull connection to the ERA server. After some research I've found some error in the trace.log from the Agent on the ERA server. 2016-11-24 10:52:44 Error: CAgentSecurityModule [Thread 7fb906bfd700]: Certificated user verification failed with: NodVerifyCertificateChain failed: NodVerifyTrustResult: 6, NVT_NotTrustedRoot, X509ChainStatus: 0x10000, X509CSF_PartialChain 2016-11-24 10:52:44 Error: NetworkModule [Thread 7fb904dfa700]: Verify user failed for all computers: 127.0.0.1: NodVerifyCertificateChain failed: NodVeri
  2. After a reinstall this is the error shown in the trace.log Besides this the status.html is showing an error in the peer certificate. (Before the reinstall this was ok) 2016-11-23 12:36:01 Error: CAgentSecurityModule [Thread 27d4]: Certificated user verification failed with: NodVerifyCertificateChain failed: NodVerifyTrustResult: 6, NVT_NotTrustedRoot, X509ChainStatus: 0x10000, X509CSF_PartialChain 2016-11-23 12:36:01 Error: NetworkModule [Thread 331c]: Verify user failed for all computers: 10.31.1.250: NodVerifyCertificateChain failed: NodVerifyTrustResult: 6, NVT_NotTrustedRoot, X509ChainSt
  3. Servers trace.log isn't showing any error's, only 1 waring: 2016-11-23 10:04:52 Warning: CDatabaseModule [Thread 7f1b67bf6700]: Dependability checks of underlaying layer failed with: The underlying unixodbc implementation has not support for multithreading. I've tried to create a new agent certificate, after this the following error appear in the trace.log. 2016-11-23 10:20:20 Error: CServerSecurityModule [Thread 7f1b47fff700]: ParsePkcs12: Could not verify password (invalid password or corrupted pkcs12 structure) 2016-11-23 10:20:20 Error: ConsoleApiModule [Thread 7f1aabfdf700]: 45 Err
  4. Nothing has changed at the server or client certificates. The only thing that changed is the IP-address off the ERA-server. Previously this was a static lease configured in the firewall as of now this ip-address is configure on the ERA-server itself.
  5. Thanks, that worked! I've change the port because we had some issues with the era agents. The eraserver is running version 6.4.304 with the agent 6.4.293 on CentOS 6.8 All of a suddon the aren't connection anymore. Nmap show's port 2222 is open on the server. The trace.log from the client shows the following: 2016-11-22 16:22:38 Error: CAgentSecurityModule [Thread 1d48]: Certificated user verification failed with: NodVerifyCertificateChain failed: NodVerifyTrustResult: 6, NVT_NotTrustedRoot, X509ChainStatus: 0x10000, X509CSF_PartialChain 2016-11-22 16:22:38 Error: NetworkModule [Th
  6. I can actually acces the loginscreen, after trying to login the errror "Login failed: Connection has failed with state 'Not connected'" displays. In the EraWebServerConfig.properties file the 2223 port is specified. The only thing I've change is the Webconsole port to port 2222. See Figure 1-5 at this page hxxp://support.eset.com/kb3701/ Could is be that this specific setting is configured in another file? After a reboot the first error specified is this one: 2016-11-22 14:18:39 Error: NetworkModule [Thread 7fb91fb8f700]: bind: Address already in use
  7. I've change the 2223 port in de ERA webconsole. After this change I'm not able to login anymore. The Eset Remote appliance is installed on a CentOS 6.8 machine. Is there a way to change the port back to port 2223? I've search in some config files, but a can't find it.
×
×
  • Create New...