hmLoadTopic({
hmKeywords:"EPNS,Push Notification Service,Wake up",
hmTitle:"ESET Push Notification Service",
hmDescription:"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...",
hmPrevLink:"supported_products.html",
hmNextLink:"fs.html",
hmParentLink:"specifications.html",
hmBreadCrumbs:"<a href=\"specifications.html\">Specifications<\/a>",
hmTitlePath:"Specifications > ESET Push Notification Service",
hmHeader:"<h1 class=\"p_Heading1\"><span class=\"f_Heading1\">ESET Push Notification Service<\/span><\/h1>\n\r",
hmBody:"<p class=\"p_Normal\">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 On-Prem can send a (push) notification to a client immediately. This is useful when you do not want to wait for the <a href=\"agent_settings.html\" class=\"topiclink\">regular interval<\/a> when the ESET Management Agent connects to the ESET PROTECT Server. For example when you want a <a href=\"admin_ct.html\" class=\"topiclink\">Task<\/a> to be run immediately on client(s) or if you want a <a href=\"admin_pol.html\" class=\"topiclink\">Policy<\/a> to be applied right away.<\/p>\n\r<p class=\"p_Normal\">When the connection is broken, client tries to reconnect. The main reason for the permanent connection is to make clients available to receive messages.<\/p>\n\r<p class=\"p_Normal\">A Web Console user can send Wake-Up calls via EPNS between ESET PROTECT Server and ESET Management Agents. ESET PROTECT Server sends <span class=\"f_UI\">Wake on LAN<\/span> calls. You can set up multicast addresses for <span class=\"f_UI\">Wake on LAN<\/span> in <span class=\"f_UI\">More<\/span> &gt; <a href=\"admin_server_settings.html\" class=\"topiclink\">Settings<\/a>.<\/p>\n\r<h2 class=\"p_Heading2\" style=\"page-break-after: avoid;\"><span class=\"f_Heading2\">Connection details<\/span><\/h2>\n\r<p class=\"p_Normal\">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. Ensure your firewall allows the connection to the EPNS server (see the table below).<\/p>\n\r<div style=\"text-align: left; text-indent: 0; padding: 0 0 0 0; margin: 0 0 10px 0;\"><table class=\"Table_small_no_header\" style=\"width:100%;\">\n\r<tr class=\"Table_small_no_header\">\n\r<td class=\"Table_small_no_header\" style=\"width:256px;\"><p class=\"p_NormalTable\" style=\"page-break-inside: avoid; page-break-after: avoid;\"><span class=\"f_NormalTable\">Cryptographic security protol<\/span><\/p>\n\r<\/td>\n\r<td class=\"Table_small_no_header\" style=\"width:1143px;\"><p class=\"p_NormalTable\" style=\"page-break-inside: avoid; page-break-after: avoid;\"><span class=\"f_NormalTable\">TLS—The latest TLS version supported by the managed computer\'s operating system<\/span><\/p>\n\r<\/td>\n\r<\/tr>\n\r<tr class=\"Table_small_no_header\">\n\r<td class=\"Table_small_no_header\" style=\"width:256px; background-color:#F4F5F4;\"><p class=\"p_NormalTable\" style=\"page-break-inside: avoid; page-break-after: avoid;\"><span class=\"f_NormalTable\">Protocol<\/span><\/p>\n\r<\/td>\n\r<td class=\"Table_small_no_header\" style=\"width:1143px; background-color:#F4F5F4;\"><p class=\"p_NormalTable\" style=\"page-break-inside: avoid; page-break-after: avoid;\"><span class=\"f_NormalTable\">MQTT (machine-to-machine connectivity protocol)<\/span><\/p>\n\r<\/td>\n\r<\/tr>\n\r<tr class=\"Table_small_no_header\">\n\r<td class=\"Table_small_no_header\" style=\"width:256px;\"><p class=\"p_NormalTable\" style=\"page-break-inside: avoid; page-break-after: avoid;\"><span class=\"f_NormalTable\">Port<\/span><\/p>\n\r<\/td>\n\r<td class=\"Table_small_no_header\" style=\"width:1143px;\"><p class=\"p_NormalTable\" style=\"text-indent: 0; page-break-inside: avoid; page-break-after: avoid; padding-left: 13px; margin-left: 8px;\"><span class=\"f_NormalTable\" style=\"font-family: Arial,\'Lucida Sans Unicode\',\'Lucida Grande\',\'Lucida Sans\';display:inline-block;width:13px;margin-left:-13px\">&#8226;<\/span><span class=\"f_NormalTable\">primary: 8883<\/span><\/p>\n\r<p class=\"p_NormalTable\" style=\"text-indent: 0; page-break-inside: avoid; page-break-after: avoid; padding-left: 13px; margin-left: 8px;\"><span class=\"f_NormalTable\" style=\"font-family: Arial,\'Lucida Sans Unicode\',\'Lucida Grande\',\'Lucida Sans\';display:inline-block;width:13px;margin-left:-13px\">&#8226;<\/span><span class=\"f_NormalTable\">fallback: 443 and the proxy port set by the ESET Management Agent policy<\/span><\/p>\n\r<p class=\"p_NormalTable\" style=\"page-break-inside: avoid; page-break-after: avoid;\"><span class=\"f_NormalTable\">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.<\/span><\/p>\n\r<\/td>\n\r<\/tr>\n\r<tr class=\"Table_small_no_header\">\n\r<td class=\"Table_small_no_header\" style=\"width:256px; height:18px; background-color:#F4F5F4;\"><p class=\"p_NormalTable\" style=\"page-break-inside: avoid; page-break-after: avoid;\"><span class=\"f_NormalTable\">Host address<\/span><\/p>\n\r<\/td>\n\r<td class=\"Table_small_no_header\" style=\"width:1143px; height:18px; background-color:#F4F5F4;\"><p class=\"p_NormalTable\" style=\"page-break-inside: avoid; page-break-after: avoid;\"><span class=\"f_Path\">epns.eset.com<\/span><\/p>\n\r<\/td>\n\r<\/tr>\n\r<tr class=\"Table_small_no_header\">\n\r<td class=\"Table_small_no_header\" style=\"width:256px;\"><p class=\"p_NormalTable\" style=\"page-break-inside: avoid; page-break-after: avoid;\"><span class=\"f_NormalTable\">Proxy compatibility<\/span><\/p>\n\r<\/td>\n\r<td class=\"Table_small_no_header\" style=\"width:1143px;\"><p class=\"p_NormalTable\" style=\"page-break-inside: avoid; page-break-after: avoid;\"><span class=\"f_NormalTable\">If you use HTTP Proxy for forwarding communication, Wake-Up calls are also sent through HTTP Proxy. Authentication is not supported. Ensure 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.<\/span><\/p>\n\r<\/td>\n\r<\/tr>\n\r<\/table>\n\r<\/div>\n\r<h2 class=\"p_Heading2\" style=\"page-break-after: avoid;\"><span class=\"f_Heading2\">Troubleshooting<\/span><\/h2>\n\r<p class=\"p_NormalList\" style=\"text-indent: 0; page-break-inside: avoid; page-break-after: avoid; padding-left: 13px; margin-left: 19px;\"><span class=\"f_NormalList\" style=\"font-family: Arial,\'Lucida Sans Unicode\',\'Lucida Grande\',\'Lucida Sans\';display:inline-block;width:13px;margin-left:-13px\">&#8226;<\/span><span class=\"f_NormalList\">Ensure your firewall is set to allow the connection to EPNS (see the details above or the <a href=\"https:\/\/support.eset.com\/kb332#EPNS\" target=\"_blank\" onclick=\"return HMTrackTopiclink(this);\" class=\"weblink\">Knowledgebase article<\/a>).<\/span><\/p>\n\r<p class=\"p_Normal\" style=\"text-indent: 0; padding-left: 32px; margin-left: 0;\"><span class=\"f_NormalList\" style=\"font-family: Arial,\'Lucida Sans Unicode\',\'Lucida Grande\',\'Lucida Sans\';display:inline-block;width:13px;margin-left:-13px\">&#8226;<\/span>Ensure both Agent and Server can connect directly to the EPNS server on the ports 443 and 8883 (to verify the connection, use the <span class=\"f_CodeHighlighted\">telnet<\/span> command).<\/p>"
})
