Prerequisites
These prerequisites must be met for ESET PROTECT Cloud to work correctly:
These domains and ports must be allowed in your network firewall for ESET PROTECT Cloud to work correctly:
Domain |
Protocol |
Port |
Service/Component |
Description |
|---|---|---|---|---|
eba.eset.com |
TCP |
443 |
ESET Business Account |
|
msp.eset.com |
TCP |
443 |
ESET MSP Administrator |
|
identity.eset.com |
TCP |
443 |
ESET Identity Server |
|
protect.eset.com |
TCP |
443 |
ESET PROTECT Cloud |
|
eu02.protect.eset.com |
TCP |
443 |
ESET PROTECT Cloud Web Console |
Location: Europe |
us02.protect.eset.com |
TCP |
443 |
Location: USA |
|
jp02.protect.eset.com |
TCP |
443 |
Location: JAPAN |
|
*.a.ecaserver.eset.com |
TCP |
443 |
Connection between the Agent and ESET PROTECT Cloud |
|
edf.eset.com |
TCP |
443 |
Live Installer |
|
repository.eset.com |
TCP |
80 |
Repository required for deployment |
|
epns.eset.com |
TCP |
8883 |
Connection for EPNS service (Wake-Up calls) |
|
eu.mdm.eset.com (EUROPE) us.mdm.eset.com (USA) |
TCP |
443 |
Cloud MDM |
Enrollment |
checkin.eu.eset.com (EUROPE) checkin.us.eset.com (USA) checkin.jp.eset.com (JAPAN) |
TCP |
443 |
Check-in |
|
mdmcomm.eu.eset.com (EUROPE) mdmcomm.us.eset.com (USA) |
TCP |
443 |
Communication |
|
mdm.eset.com (GLOBAL) |
TCP |
443 |
Limited input device enrollment |
|
|
TCP |
139 |
ESET PROTECT Cloud Remote Deployment Tool (Target ports from the point of view of Remote Deployment Tool) |
Using the share ADMIN$ |
|
TCP |
445 |
Direct access to shared resources using TCP/IP during remote installation (an alternative to TCP 139) |
|
|
UDP |
137 |
Name resolution during remote install |
|
|
UDP |
138 |
Browse during remote install |