Jump to content

mgfeal

Members
  • Content Count

    6
  • Joined

  • Last visited

Profile Information

  • Location
    Spain
  1. Ok, but how do you deploy it? The old servers uses this cert: Agent peer certificate with subject 'CN=Agent at *, C=US' issued by 'CN=Server Certification Authority, C=US' with serial number '0194xxxxxxxxxxxxx9301' We create a policy in the old server to only modify the "Servers to connect to ..." option with the new server DNS and port 2222. And the clients connect to the new one but show the errors that we put before. Maybe we need to export the Agent cert in the new server, import in the old server and apply to the same policy that modify the server?
  2. Hi, As we recovered our old server (problems with database connection) with 6.5 version, we installed a new one with the last version. So, now we are reading this KB: https://support.eset.com/en/kb6492-client-computer-migration-in-eset-remote-administrator-6x We created a new policy in the old server. Testing it we assigned to a desktop agent. This agent received the policy, but in trace.log we see a few errors, and the client not appear at the new console. 2020-10-27 13:34:50 Error: NetworkModule [Thread 27a0]: Verify user failed for all computers: 172.20.xx.yy: NodVerifyCe
  3. We changed StartupConfiguration.ini with Driver=MySQL ODBC 8.0 Unicode Driver; And now it works perfect!! Many thanks! Yes, it's and old server, but we need to redirect agents to the new one and copy all policies.
  4. Hi, We have a problem with our old ESET Remote Administration Server (appliance). When we try to login, we have this error: Login failed: Connection has failed with state 'Not connected' If we check /var/log/eset/RemoteAdministrator/Server/trace.log we can find these messages: Error: CDatabaseModule [Thread 7fd5c0fc1700]: Probing database connection failed. Next connection attempt will be in 10 seconds. 10 more attempts will be made. The database access layer reported: [unixODBC][Driver Manager]Data source name not found, and no default driver specified (0)
  5. Our ESET server has this IP: 172.10.0.100 (actualeset.domain.local) New ESET server now is 172.10.0.150 (neweset.domain.local) All agents are connecting to the actualeset.domain.local As now we can't access to 172.10.0.100 console (database access) we are thinking in that process: - Shutdown 172.10.0.100 (actualeset.domain.local) server. - Change IP for new ESET. Assign 172.10.0.100. Now actualeset.domain.local would go to 172.10.0.100 - As all agents are connecting to actualeset.domain.local in that step they would be connecting to the new console.
  6. Hi, We have and old ESET Administrator Appliance with all our desktops registered. Now we want to migrate to a new one appliance with the latest version. We installed the new appliance, installed the license and copy the certificates. All it's working perfect. Now we have a problem. We can't access to our old server, we have a problem with login (database connection). If we can't fix it, we are thinking another options. For example: - shutdown the old server. - Change the IP for the new one and put the same IP as the old server. The agents the next time they connect will
×
×
  • Create New...