ESET Push Notification Service
ESET Push Notification Service (EPNS) serves for receiving messages from the ESET PROTECT Server, if the server has a notification for the client. The connection is running so that ESET PROTECT can send a (push) notification to a client immediately. When the connection is broken, client tries to reconnect. The main reason for the permanent connection is to make clients available to receive messages.
A Web Console user can send Wake-Up calls via EPNS between ESET PROTECT Server and ESET Management Agents. ESET PROTECT Server sends Wake on LAN calls. You can set up multicast addresses for Wake on LAN in More > Settings.
Connection details
To configure your local network to allow communication with EPNS, both the ESET Management Agent and the ESET PROTECT Server need to be able to connect to the EPNS server. If you cannot establish a connection with EPNS for your Agents, only Wake-Up calls are affected.
Cryptographic security protol |
TLS—The latest TLS version supported by the managed computer's operating system |
Protocol |
MQTT (machine-to-machine connectivity protocol) |
Port |
•primary: 8883 •fallback: 443 and the proxy port set by the ESET Management Agent policy Port 8883 is preferred, as it is an MQTT port. The 443 is only a fallback port and it is shared with other services. Also, a firewall can abort the connection on port 443 because of inactivity or maximum opened connections limit for the HTTP Proxy server. |
Host address |
epns.eset.com |
Proxy compatibility |
If you use HTTP Proxy for forwarding communication, Wake-Up calls are also sent through HTTP Proxy. Authentication is not supported. Make sure to configure HTTP Proxy in Agent policy on computers where you want to send the Wake-up calls. If HTTP Proxy is not working, Wake-up calls are sent directly. |
Troubleshooting
•Make sure your firewall is set to allow the connection to EPNS (see the details above or the Knowledgebase article).
•Make sure both Agent and Server can connect directly to the EPNS server on the ports 443 and 8883 (to verify the connection, use the telnet command).
•If you run the Virtual Appliance and you get the EPNS service servers are not accessible alert, follow the troubleshooting steps.