- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Allow ESET Cloud Domains in Nighthawk R8000
Looking for some help from the Community. I do some IT work for my Chiropractor, they have a Nighthawk R8000 router. I recently had them purchase ESET EndPoint Protection for their Antivirus and such. It appears that the router is preventing access for the Cloud Portal to manage the devices.
How would I update the router settings for these ports/URLs.
Thanks in advance..
These prerequisites must be met for ECA to work correctly:
These domains and ports must be allowed in your network firewall for ECA to work correctly:
eba.eset.com | TCP/443 | ESET Business Account |
identity.eset.com | TCP/443 | ESET Identity Server |
eca.eset.com | TCP/443 | ESET Cloud Administrator |
eu01.eca.eset.com | TCP/443 | ESET Cloud Administrator Web Console Location: Europe |
us01.eca.eset.com | TCP/443 | ESET Cloud Administrator Web Console Location: USA |
*.a.ecaserver.eset.com | TCP/443 | Connection between the Agent and ECA |
edf.eset.com | TCP/443 | ECA Live Installer |
repository.eset.com | TCP/80 | ECA Live Installer. Repository required for deployment. |
epns.eset.com | TCP/8883 | Connection for EPNS service (Wake-up Call, Single sign-on, License sync between ECA and EBA) |
ECA Remote Deployment Tool:
TCP | 139 | Target port from the point of view of ECA | Using the share ADMIN$ |
TCP | 445 | Target port from the point of view of ECA | Direct access to shared resources using TCP/IP during remote installation (an alternative to TCP 139) |
UDP | 137 | Target port from the point of view of ECA | Name resolution during remote install |
UDP | 138 | Target port from the point of view of ECA | Browse during remote install |
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Re: Allow ESET Cloud Domains in Nighthawk R8000
Well, most firewalls are typically IP based anyway, only proxy-like stuff can block domain URLs. Here we face simple consumer router, which does per se allow any outgoing connections. So why bother?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Re: Allow ESET Cloud Domains in Nighthawk R8000
@schumaku wrote:Well, most firewalls are typically IP based anyway, only proxy-like stuff can block domain URLs. Here we face simple consumer router, which does per se allow any outgoing connections. So why bother?
____________________________________________________________________________
Great answer!!
Spot on, - problem solved...
English is not my native tongue so i may have misunderstood something here but i do get a feeling that something aint working for him and thats why he bothered to wrote here in the first place
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
User | Count |
---|---|
43 | |
20 | |
15 | |
10 | |
9 |