Jump to content

mgfeal

Members
  • Posts

    12
  • Joined

  • Last visited

About mgfeal

  • Rank
    Newbie
    Newbie

Profile Information

  • Location
    Spain
  1. I'm checking and we haven't /var/cache/apache2 folder. Is it possible to install Apache in the appliance? Is this doc the correct steps? https://help.eset.com/protect_install/80/en-US/http_proxy_installation_linux.html
  2. Thanks. We have a problem: AiO appliance was installed by an old member of our team and we don't know if it was installed. How can we check it?
  3. Yes, we know hot to do it, but before we need to know if at server side, proxy will work only enabling it at Advanced configuration. Thanks!
  4. Hi, We have the following version of ESET PROTECT: ESET PROTECT (Server), Version 8.0 (8.0.2225.0) ESET PROTECT (Web Console), Version 8.0 (8.0.191.0) CentOS (64-bit), Version 7.8.2003 We want to use the proxy functionality to update the servers, which have no internet access. It is not clear to us how to configure it. Is activating it in 'Server Settings' - 'Advanced Settings' enough? Thanks!
  5. Hi, We are with more issues activating the devices. Checked that we can telnet to 443 port to edf.eset.com for example. But it's impossible to activate any device, new or reinstaled. What can we check? Thanks!
  6. Hi, We created an installer for all our new computers. It works ok installing agent and antivirus, but we can't activate them. Our management console appliance uses 8443 port and if we telnet it from the computers it works. It shows an error that they can't connect with the activation server and the ECP.20003 code. How can we fix it? The activation server is the appliance, or they need to connect to internet? Thanks!
  7. 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?
  8. 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: NodVerifyCertificateChain failed: NodVerifyTrustResult: 42, NVT_NotTrusted, X509ChainStatus: 0x10000, X509CSF_PartialChain 2020-10-27 13:34:50 Error: NetworkModule [Thread 27a0]: Receive: NodSslWriteEncryptedData: Incorrect/unknown certificate or key format., ResolvedIpAddress:172.20.5.204, ResolvedHostname:, ResolvedPort:2222 2020-10-27 13:34:50 Error: NetworkModule [Thread 27a0]: Protocol failure for session id 277, error:Receive: NodSslWriteEncryptedData: Incorrect/unknown certificate or key format. 2020-10-27 13:34:50 Error: CReplicationModule [Thread 36d8]: CReplicationManager: Replication (network) connection to 'host: "antivirus3.xxxx.yyyy" port: 2222' failed with: Receive: NodSslWriteEncryptedData: Incorrect/unknown certificate or key format. 172.20.xx.yy is the new server IP antivirus3.xxxx.yyyy is the new server DNS All certificates in the new server are autogenerated. In the old server all the certificates are yet autogenerated. This is our "Server configuration" with the autogenerated cert assigned: We don't understand in the KB that in the new server create a new policy with the Agent certificate. But this policy is for clients that appear in the new server, we haven't reached that yet. Many thanks!
  9. 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.
  10. 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) /etc/opt/eset/RemoteAdministrator/Server/StartupConfiguration.ini DatabaseType=MySqlOdbc DatabaseConnectionString=Driver=MySQL ODBC 5.3 Unicode Driver;Server=127.0.0.1;Port=3306;User=era;Password={ovhgUJ54};CharSet=utf8;NO_LOCALE=1;Database=era_db; /etc/odbcinst.ini [PostgreSQL] Description = ODBC for PostgreSQL Driver = /usr/lib/psqlodbc.so Setup = /usr/lib/libodbcpsqlS.so Driver64 = /usr/lib64/psqlodbc.so Setup64 = /usr/lib64/libodbcpsqlS.so FileUsage = 1 UsageCount = 2 [MySQL ODBC 8.0 Unicode Driver] Driver = /usr/lib64/libmyodbc8w.so UsageCount = 2 [MySQL ODBC 8.0 ANSI Driver] Driver = /usr/lib64/libmyodbc8a.so UsageCount = 2 This server has an old ESET version, but we need to access to it to migrate our agents and recover policies and more. We review this article: https://support.eset.com/en/kb6760-cannot-connect-to-the-web-console-after-linux-mysql-update-eset-remote-administrator-6x But it doesn't work. Our mysql-connector-odbc version is mysql-connector-odbc-8.0.21-1.el6.x86_64 MySQL version: mysql Ver 14.14 Distrib 5.6.49, for Linux (x86_64) CentOS version is CentOS release 6.10 (Final) Does anyone know how we can fix it? Thank you very much!
  11. 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. What would happen now? The new console has no registered agents. On the clients when the agent tries to connect, the new server has the same certificates, the same IP and the same DNS. Will the client log appear in the console as they connect? Reading the documentation (https://help.eset.com/esmc_deploy_va/72/en-US/va_upgrade_migrate.html) I think we are using "Migration and upgrade process (recommended way to upgrade)" and then the steps above "If the new ESMC VA has the same IP address" By doing the steps that I put in, can we expect the names of the teams to appear automatically in the new console? Thank you!
  12. 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 be against the new server. What will happen? Will they self-register on the new console? Or will we have to create an installer on the new server to manually launch on clients so that they connect to the new server and register? Many thanks!!
×
×
  • Create New...