ESET Remote Administrator and Licence Renewal

firewall

(Andrew) #1

NethServer Version: 7.6.1810
Module: Firewall I think

Hi All,

I am having an issue when trying to renew ESET licenses using the Eset remote Administrator. The renewal says it fails to contact the server. I have done following to try and solve the problem:

  1. Switched off the Web Filter - Did not let the connection through
  2. Switch off Block Access to web sites using ip addresses - Did not solve the problem.
  3. Put eset.com in the global whilelist (as recommended by Eset) - Did not solve the issue
  4. Created a host for eset and placed it in the Host without Proxy List - did not solve the problem.

Has anybody got other suggestions?

Thanks
Andrew


(Michael Kicks) #2


This worked for Anydesk. Maybe it’ll help for ESET also.


(Andrew) #3

Hi Michael,

Thanks for the suggestion. I tried it and added the following to the Domains without Proxy:
h1-edfspy02-v.eset.com
91.228.165.74
h1-edfspy02-v.eset.com
91.228.167.40
h1-arse01-v.eset.com
91.228.166.104
h1-arse02-v.eset.com
91.228.166.71
h3-arse01-v.eset.com
91.228.167.64
h3-arse02-v.eset.com
91.228.167.81
h5-arse01-v.eset.com
38.90.226.16
h5-arse02-v.eset.com
38.90.226.17
edf.eset.com
edfpcs.trafficmanager.net
edf.eset.com
bal-edf-pcs-app-vmss-01.westus.cloudapp.azure.com
13.64.117.133
edfpcs.trafficmanager.net
bal-edf-pcs-app-vmss-02.westus.cloudapp.azure.com
repository.eset.com
edf.eset.com
edfpcs.trafficmanager.net
edf.eset.com
edfpcs.trafficmanager.net
bal-edf-pcs-app-vmss-01.westus.cloudapp.azure.com
edfpcs.trafficmanager.net
bal-edf-pcs-app-vmss-02.westus.cloudapp.azure.com
edfpcs.trafficmanager.net
register.eset.com
h1-weblb01-v.eset.com
h3-weblb01-v.eset.com
iploc.eset.com
pki.eset.com
versioncheck.eset.com

This is pretty much every address I could get my hands on from the ESET site.

When I bypass the entire proxy and connect direct to the net, the license loads fine.

Thanks again.
Andrew


(Michael Kicks) #4

For whom may concern…


(Andrew) #5

Thanks for everyone’s responses. I have managed to solve it and here is the process:

  1. Create a host entry in the firewall for the server that cannot connect to the ESET network.
  2. Create a Filter in the Proxy content Filter and allow access to everything.
  3. Create a profile in Proxy content Filter linking the host server (1) and the allow all (2).

This allows access to the eset servers for licensing etc.
Hope this helps the next person that has an issue.

Andrew