Jump to content

GeorgeC

Members
 View Profile  See their activity

  • Posts

    24

  • Joined

  • Last visited

 Content Type 

Posts posted by GeorgeC

    Activate new clients

    in ESET PROTECT On-prem (Remote Management)

    Posted

    I have an ERA 6.4.295.0 installation and I am trying to activate 2 new computers. I have started with the first one. I installed the agent successfully because I can see the computer name in question under "Not activated Security Product" and all the computer details listed when I look for details. So I guess it is "reading" everything from the client.

    The problem is that the activate task is failing. Where can I see the cause of the fail? Is there a way to troubleshoot this?

    ERA is failing to connect to licencing server

    in ESET PROTECT On-prem (Remote Management)

    Posted

     

    When I ping it resolves the IP. But I am not getting a reply:

     

    [root@era ~]# ping edf.eset.com

    PING edf-pcs.cloudapp.net (137.135.12.16) 56(84) bytes of data.

     

    No the firewall doesn't block https.

     

    From the coloring of ssh client and root user my guess is that you are using virtual appliance?

    Did you install and configure apache proxy for clients?

     

    Check "How do I enable Apache HTTP proxy on my ERA Virtual Appliance after initial configuration?" on:

     

    hxxp://help.eset.com/era_deploy_va/62/en-US/index.html?va_faq.htm

     

     

    Correct. As I said earlier I am using a virtual appliance installed on a XenServer environment. 

    No I hadn't enabled Apache HTTP proxy on ERA VA but I did after your post!

    ERA is failing to connect to licencing server

    in ESET PROTECT On-prem (Remote Management)

    Posted

    For start I would try to ping edf.eset.com to check whether network access is available. Also SERVER's trace log /var/log/eset/RemoteAdministrator/Server/trace.log may contain more detailed information why license synchronization fails (search for errors).

     

    I cannot get a reply from edf.eset.com, not even from my desktop. It resolves its IP but I'm getting a time out error.

     

    Regarding the log error, I found this.

     

    2016-06-27 08:59:37 Error: LicenseModule [Thread 7fed5adea700]: LicenseModuleHelper: AssociateOrReassociateSeatIfNecessary:

    Transparent seat association for action 'LinkSeatPoolByKey' failed.

    2016-06-27 08:59:37 Error: LicenseModule [Thread 7fed5adea700]: AddPoolByLicenseKey: Failed to add pool by license key, because connection to the licensing server failed. Error: CEcpCommunicator: Failed to send XML request message, error=20003 (connection failure).

    2016-06-27 08:59:37 Error: ConsoleApiModule [Thread 7fed57be5700]: 13476 Error while processing AddPoolByLicenseKey 29789: AddPoolByLicenseKey:

    Failed to add pool by license key, because connection to the licensing server failed. Error: CEcpCommunicator: Failed to send XML request message, error=20003 (connection failure).

     

    It looks like communication error. Correct?

    ERA is failing to connect to licencing server

    in ESET PROTECT On-prem (Remote Management)

    Posted

    Hello to all.

    I just finished installing my ERA Server. I deployed a virtual appliance on a Xenserver.

    After the creation of the VA has finished I entered the web console and completed the ERA server appliance parameters.

    Didn't know where to start so I decided to first add a license in license management.

    So, when I add the license key after a few seconds I get the message that it failed to add the license because it failed to connect to the licensing server.

    I went to the VAs console and pinged with success the following: 

    register.eset.com 91.228.165.81

    register.eset.com 91.228.167.125

    h1-weblb01-v.eset.com 91.228.165.79

    h3-weblb01-v.eset.com 91.228.167.123

     

    Should I have to check anything else?

     

    Thank you in advance.

     

    Remote Admin 6 on a Linux 12.04 virtual machine

    in ESET PROTECT On-prem (Remote Management)

    Posted · Edited by GeorgeC

    If computers are in a domain, they should appear in ERA virtually automatically if you have AD/OD/LDAP configured properly in the Server tasks -> Static group synchronization.

    Otherwise you can take advantage of RD sensor which detects computers in its subnet and you can easily import computers from its report.

    I'd suggest you start off opening "C:\Documents and Settings\All Users\Application Data\ESET\RemoteAdministrator\Agent\EraAgentApplicationData\Logs\status.html" for possible errors. Then you can check agent trace log in the same folder which might shed more light.

    Hi there,

    So I must install RD sensor too?

    It is a Linux installation so the above file as you understand is not available...

    Remote Admin 6 on a Linux 12.04 virtual machine

    in ESET PROTECT On-prem (Remote Management)

    Posted

    You are correct. The path was wrong. OK, the agent is installed. So now, what?

    I have also installed Endpoint 6 to two computers only for testing purposes to see if they are going to connect with ERAC 6 etc.

    So I exported the peer agent certificate and I installed the agents in each one of them. The one is a XP machine and the other a Mac OSX 10.10.3.

    They don't appear in the remote admin only when I manually add them with their IP. Even then  the status, virus db status etc is unknown. So I assume they cannot connect to the server. What to check? How can I test if the agent on a PC or Mac is configured correctly?

     

    Do I need to do anything else on server side?

    Remote Admin 6 on a Linux 12.04 virtual machine

    in ESET PROTECT On-prem (Remote Management)

    Posted

    Hello there,

     

    I manged, after some problems, to deploy a Linux 12.04.5 on a Xen Server host. There, I installed the remote administrator with mySQL 5.5 and the Web Console.

     

    I am able to login to the remote admin through a web browser so I guess that's something... Since the documentation is a bit chaotic, I now try to install the agent on the server. I thing it is needed in order for the clients to communicate with the server.

    So I am using the script on the example on the on line help, 

    ./Agent-Linux-x86_64.sh \
    --skip-license \
    --cert-path=/home/agent.pfx \
    --cert-auth-path=/home/CA.der \
    --cert-password= \
    --hostname=10.1.179.36 \
    --port=2222

    I have changed the paths with mine but as far the password is concerned I haven't given any password to the certificates. When I go to peer certificates there are three: server, agent and agent for server for assisted installation. I haven't created them so there must be from default.

    So which password to use.... I put blank but I get an error:

    Checking certificate password ... failed

    : Error checking peer certificate password: NOT_REGULAR_FILE 

     

    Any help would be appreciated. 

×
×
  • Create New...