This Knowledgebase article provides firewall configuration requirements for Neverfail Continuity Engine.
When firewalls are used to protect networks, you must configure them to allow traffic to pass through specific ports for Neverfail Engine installation and management. If using Windows Firewall, Engine Management Service can automatically configure the necessary ports for traffic. In the event that other than Windows Firewall is being used, configure the following specific ports to allow traffic to pass through:
- Ports 9727 and 9728 for managing Neverfail Engine from the Engine Management Service
- Port 52267 for the Client Connection port
- Port 57348 for the Default Channel port
Important: When installing on Windows Server 2008 R2, Microsoft Windows may change the connection type from a Private network to an Unidentified network after you have configured the firewall port to allow channel communications resulting in the previously configured firewall changes to be reset for the new network type (Unidentified).
The firewall rules must be recreated to allow traffic to pass through for the Client Connection port and the Default Channel port. Neverfail recommends that the firewall be configured to allow the Client to connect to the Client Connection port by process, nfgui.exe, rather than by a specific port. To enable Channel communications between servers, change the Network List Manager Policy so that the Neverfail Channel network is identified as a Private Network, and not the default Unidentified Network, and configure the firewall to allow traffic to pass through on Port 57348, the Default Channel port.
Neverfail Continuity Engine v8.0 and Later
KBID-2979