A List of Default Neverfail Heartbeat Ports

Follow

Summary

This Knowledgebase article provides information about the default ports used by Neverfail Heartbeat.


More Information

This knowledgebase article applies to the Neverfail Heartbeat base product. Please refer to Knowledgebase article #280 - 'Neverfail Heartbeat Management Client, Firewalls, and Exchange' for information about Firewall issues as well.

For any installation of Neverfail Heartbeat, the following ports must be set to allow both Incoming and Outgoing traffic. The ports used will depend on the version of Neverfail Heartbeat installed.

Pre-V4.1

Channel: 8000
Client: 2267

V4.1 through V5.1.1

Channel: 57348
Client: 52267

Version 5.2.0 on

Channel: 57348
Client: 52267

SCOPE Data Collector Service v4.3.4 and Earlier: 41000, 61000

Bandwidth Measurement: 61000

Communication between Primary and Secondary: 41000

SCOPE Data Collector Service v5.0.8 and Later

Bandwidth Measurement: 61000

Communication between Primary and Secondary: 62000

Note: The Channel ports above are the ports from the Primary server. The Secondary server connects to the Primary through the channel using random ports on its side.

These ports can be blocked by default on any Firewall present on the system, or in the case of a WAN, on the network firewall. Therefore, they must be enabled.

Network applications that use these ports can also cause problems. Inability to establish channel communication or sudden channel disconnects are often a sign that another application is attempting to use one of these ports.

If a conflict exists, the ports can be changed following the procedure below:

  1. Shut down Neverfail Heartbeat using the Management Client, or stop the service via the Service Control Manager.
  2. Launch the Configure Server wizard and change the appropriate port number.
  3. Click Apply .
  4. Close the wizard and restart the service on both servers.

Checking the port:

If you suspect another application or service is attempting to use a Neverfail Heartbeat port, perform the following procedure to identify if a running application is using the port:

  1. Shutdown Neverfail Heartbeat before using this procedure.
  2. E.g. to identify if a running application is using port 57348

  3. Open a command window and run the following from the command line.

c:\>netstat -ano | findstr 57348

TCP 192.168.16.3:57348 192.168.16.4:57348 ESTABLISHED 1748
TCP 192.168.17.1:57348 192.168.17.3:57348 ESTABLISHED 1748

Note: The number in the last column is the Process Identifier (PID). This number can then be used to search the running process task list.

C:\>tasklist /fi "PID eq 1748"

Image Name PID Session Name Session# Mem Usage
========= === ========== ====== =========
$ProcessClashingWithNFHB$.exe 1748 Console 0 62,920 K

If you find a process is using the NFHB port, you will need to configure a different port number.


Applies To

All Versions


Related Information

Knowledgebase article #830 - How to Change the Data Replication Port
Knowledgebase article #831 - How to Change the Client Connection Port

KBID-206

0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.