Jared Fowkes

We have an ESET network profile for our company with a single activator: "Windows profile: Domain". Users in branch offices get this profile correctly. However, remote employees, who are connected to company-provided gateways, do not - even though Windows shows that the connection profile is indeed "Domain". This was verified by running `Get-NetConnectionProfile`. The only thing that seems to link the affected systems is that they are on remote gateways in their home instead of a branch office. The DNS, hostname, and connection profiles are otherwise identical. Expected: Company network profile be applied by ESET. Actual: Public network profile is applied by ESET.

I was able to get the agent to install by forwarding all ports to it, but would like to know which ports need to be forwarded. Before I was forwarding 2222-2223 TCP and UDP, but apparently that's not enough.

The agent it installed on Centos 7.7 and is version 7.1.503.0. It was installed from the RPM presented on the ESET downloads page. The error occurs during configuration, when running the agent-linux-x68_64.sh command. $sudo bash agent-linux-x86_64.sh --hostname=redacted.domain.com --port=2222 --webconsole-port=2223 --webconsole-user=redactedUsername --webconsole-password=redactedPassword Do you accept the license? [y/N]: y Product improvement program Participating in product improvement program includes sending crash reports and anonymous telemetry data such as OS version and type, ESET product version and other product-specific information to ESET when enabled. Do you want to participate in the Product improvement program? [Y/n]: n Creating directories... Creating 'install' directory path: /opt/eset/RemoteAdministrator/Agent Creating 'config' directory path: /etc/opt/eset/RemoteAdministrator/Agent Creating 'data' directory path: /var/opt/eset/RemoteAdministrator/Agent Creating 'Pki Cache' directory path: /var/opt/eset/RemoteAdministrator/Agent/pki.eset.com/ Creating 'logs' directory path: /var/log/eset/RemoteAdministrator/Agent Creating 'libs' directory path: /opt/eset/RemoteAdministrator/Agent Directories created The archive will be extracted to: /opt/eset/RemoteAdministrator/Agent Extracting, please wait... Checking OpenSSL ... done [OpenSSL 1.0.2k-fips 26 Jan 2017] Checking installed version ... Status of current installation is: NEW New connection settings are 'hostname': 'redacted.domain.com', 'port': 2222 Getting certificate from server... It is not possible to connect to the ESET Security Management Center Server. Cleaning up setup directories

I'm trying to install the remote agent onto an AWS instance and am getting the following error: I have opened the firewall ports for TCP 2222 and 2223, and tested them using telnet as listed in a previous post (https://forum.eset.com/topic/15968-it-is-not-possible-to-connect-to-the-eset-remote-administrator-server/). Any help or advice is welcome and appreciated.