Ports used

ESET PROTECT Server can be installed on the same computer as the database, ESET PROTECT Web Console and Apache HTTP Proxy. The diagram below shows the separated installation and the used ports:

ports_scheme

The tables below list all possible network communication ports used when ESET PROTECT and its components are installed in your infrastructure. Additional communication occurs via the native operating system processes (for example, NetBIOS over TCP/IP).

important

Important

For the proper function of the ESET PROTECT, other applications should not use any of the ports below.

Make sure to configure any firewall(s) within your network to allow communication via the ports listed below.

arrow_down_business Client (ESET Management Agent) or Apache HTTP Proxy machine

arrow_down_business ESET PROTECT Web Console machine (if not the same as ESET PROTECT Server machine)

arrow_down_business ESET PROTECT Server machine

arrow_down_business Rogue Detection (RD) Sensor

arrow_down_business ESET PROTECT MDC machine

arrow_down_business MDM managed device

* The GCM (Google Cloud Messaging)  service is deprecated and was removed as of April 11, 2019. It was replaced by FCM (Firebase Cloud Messaging). MDM v7 replaced the GCM service with the FCM service by this date, at which point you only need to allow communication for the FCM service.

The pre-defined ports 2222, 2223 can be changed if necessary.