Skip to main content

NightWatchman Enterprise

Communication ports

1E NightWatchman Agent and 1E WakeUp client

Note

For NightWatchman Enterprise 7.2.500 and later, the legacy 1E Agent has been split into 1E NightWatchman Agent and 1E WakeUp client module of the 1E Client.

Port

Traffic

Notes

Configurable

UDP 1776

Inbound and Outbound

Communication with 1E WakeUp client and magic packets.

TCP 80 (HTTP)

Outbound

Communication with the NightWatchman Web service.

TCP 80 (HTTP)

Outbound

Communication with the NightWatchman Management Center.

  • RPC/WMI with admin rights is required between 1E NightWatchman Agent (NWM) when using a remote NightWatchman.exe command-line

  • Incoming Internet Control Message protocol (ICMP) must be whitelisted on routers. It is used by the 1E WakeUp Server to discover 1E WakeUp clients.

The 1E WakeUp client and 1E NightWatchman Agent can each use both HTTP and HTTPS protocols, configurable during installation using command-line installer properties, and after installation by changing registry values. YOu can set values so tha tthe client agents communicate with the NightWatchman Management Center Web Service using the following protocols and security levels in the following order:

  1. HTTP.

  2. HTTPS without certificate.

  3. HTTPS using certificate subject match.

  4. HTTPS using certificate issuer match.

ActiveEfficiency

ActiveEfficiency is required only for the NightWatchman catalog update service, which is not used by NightWatchman 7.2.500 and later.

Port

Traffic

Notes

Configurable

TCP 135 (RPC)

Between NightWatchman and ActiveEfficiency servers

Communication with the queue managers. A dynamic port typically assigned by remote procedure calls (RPC) for handshaking with an independent client or with an RPC server for the message queuing server to determine the fixed ports.

TCP 1801 (MSMQ)

Between NightWatchman and ActiveEfficiency servers

Communication with the queue managers.

NightWatchman admin console

Port

Traffic

Notes

Configurable

TCP 8732 (SMB)

Outbound

Communication with the NightWatchman console service.

NightWatchman console service

Port

Traffic

Notes

Configurable

TCP 1443 (ADO .NET)

Outbound

Communication with the NightWatchman (AFR) database.

TCP 135 (RPC)

Outbound

Communication with the ActiveEfficiency server.

Import wizard

Port

Traffic

Notes

Configurable

TCP 1443 (ADO .NET)

Outbound

Communication with the NightWatchman (AFR) database.

Reporting console

Port

Traffic

Notes

Configurable

TCP 80 (HTTP)

Inbound

Communication with the NightWatchman Reporting Website.

TCP 1443 (ADO .NET)

Outbound

Communication with the NightWatchman (AFR) database.

NightWatchman AFWebService website

Port

Traffic

Notes

Configurable

TCP 80 (HTTP)

Inbound

Communication with the NightWatchman and WakeUp 1E WakeUp client and from WakeUp Server for registration, boundary maintenance and statistics reporting Communication with the database.

TCP 8732

Inbound

Communication with the Import wizard and NightWatchman Admin console.

TCP 8750

Inbound

Communication with Web WakeUp.

TCP 1443 (ADO .NET)

Outbound

Communication with the NightWatchman (AFR) database.

Web Wakeup

Port

Traffic

Notes

Configurable

TCP 8750

Outbound

Communication with the NightWatchman Web service.

WakeUp Server service

The WakeUp Server also has an installation of a WakeUp client and should therefore included their communications.

Port

Traffic

Notes

Configurable

TCP 443 (HTTPS)

Outbound

Communication with the NightWatchman Web service.

TCP 1777

Inbound

Communication with 1E WakeUp clients.

TCP 1776

Outbound

Communication with 1E WakeUp clients.

  • IPv4 network is necessary

  • RPC/WMI incoming from the NightWatchman Management Center Console service, any remote WakeUp Server consoles, any SCCM Console WakeUp extensions. Potentially used by custom WakeUp applications, however Web WakeUp is recommended instead for custom wakeup applications)

  • Internet Control Message protocol (ICMP) must be whitelisted on routers. It is used by the WakeUp server to discover 1E WakeUp clients (WakeUp).

Things to bear in mind
  • RPC/WMI incoming from the NightWatchman Management Center server and any remote consoles

  • Incoming Internet Control Message protocol (ICMP) must be whitelisted on routers. It is used by the WakeUp server to discover agents

  • Port 135 is a dynamic port typically assigned by remote procedure calls (RPC) for handshaking with an independent client or with an RPC server for the message queuing server to determine the fixed ports

  • IPv4 network is necessary.