Networking

Due to the nature of how proxy servers can be implemented, some of which can be quite complex, you may need to consult your networking specialist to see if exceptions need to be added to enable Nomad’s peer-copy over HTTP or HTTPS.


The following are the ports used by Nomad client on clients and on Distribution Points. The table does not include Configuration Manager communications, which can be found here: https://docs.microsoft.com/en-us/sccm/core/plan-design/hierarchy/communications-between-endpoints.

PortsNotesConfigurable
UDP 1779


Default port Nomad uses for listening to elections to determine the master on a subnet, control traffic and for content transfer if you have Connectionless enabled.

A firewall exception must exist for this port. Nomad will create one automatically for Windows firewall, but not for other firewall software.

Yes, during installation.
TCP 80 (HTTP)

Used when the Nomad master requests LSZ files from Nomad running on the DP and when the Nomad master downloads content using Nomad as provider.

Communications depend on how the DP is configured. Configuration Manager is configured to use either HTTP or HTTPS.

If Nomad clients and ActiveEfficiency server are configured to use HTTP, Nomad clients using SSD register and query for content.

No, for communications with CM components. Nomad service on startup reads the configured ports from CM client registry and uses the same for LSZ generation.

Yes, for communications with ActiveEfficiency using Nomad's PlatformURL setting.

TCP 443 (HTTPS)

Used when the Nomad master requests LSZ files from Nomad running on the DP and when the Nomad master downloads content using Nomad as provider.

Communications depend on how the DP is configured. Configuration Manager is configured to use either HTTP or HTTPS.

If Nomad clients and ActiveEfficiency server are configured to use HTTPS, Nomad clients using SSD register and query for content.

No, for communications with CM components. Nomad service on startup reads the configured ports from CM client registry and uses the same for LSZ generation.

Yes, for communications with ActiveEfficiency using Nomad's PlatformURL setting.

TCP 5080 (HTTP)

Default HTTP port to use for peer copy. If you are using a custom port, ensure that all agents use the same custom port.

From Nomad 6.2, peer copy can be enabled over HTTP (default 5080) or HTTPS (default 5443). You can customize the ports for this feature in the host registry but a change to the default impacts Nomad's peer backup assistant which is used to capture user data on remote peers during OS deployments. 

 Yes, during installation.
TCP 5443 (HTTPS)

Default HTTPS port to use for peer copy. If you are using a custom port, ensure that all agents use the same custom port.

From Nomad 6.2, peer copy can be enabled over HTTP (default 5080) or HTTPS (default 5443). You can customize the ports for this feature in the host registry but a change to the default impacts Nomad's peer backup assistant which is used to capture user data on remote peers during OS deployments. 

 Yes, during installation.
TCP 139 (SMB)

Required only if SMB is enabled.

Used when Nomad master downloads content from DP and for peer-to-peer content transfer between the Nomad master and Nomad peers. Communications depend on how the DP is configured. That is HTTP, HTTPS, SMB or SMB over TCP. For Configuration Manager the default is HTTP or HTTPS.

Windows Firewall automatically adds the exception when you enable File and Print Sharing but you may have to do this manually if you are using a different firewall product.

No. SMB ports cannot be configured.
TCP 445 (SMB over TCP)

Required only if SMB is enabled.

Used when Nomad master downloads content from DP and for peer-to-peer content transfer between the Nomad master and Nomad peers. Communications depend on how the DP is configured. That is HTTP, HTTPS, SMB or SMB over TCP. For Configuration Manager the default is HTTP or HTTPS.

Windows Firewall automatically adds the exception when you enable File and Print Sharing but you may have to do this manually if you are using a different firewall product.

No. SMB ports cannot be configured.
TCP 137 (SMB)

Required only if SMB is enabled.

Used by SMB for data transfer and related communications. It is used to resolve NetBIOS names during a transfer. UDP NetBIOS name query packets are sent to this port.

Windows Firewall automatically adds the exception when you enable File and Print Sharing but you may have to do this manually if you are using a different firewall product.

 No. SMB ports cannot be configured.
TCP 139 (SMB)

Required only if SMB is enabled.

Used by SMB for data transfer and related communications. It is used to resolve NetBIOS names during a transfer. UDP NetBIOS datagram packets are exchanged this port.

Windows Firewall automatically adds the exception when you enable File and Print Sharing but you may have to do this manually if you are using a different firewall product.

 No. SMB ports cannot be configured.

Nomad can use ephemeral ports (not discussed here). Ephemeral or high ports can either be UDP or TCP depending on the protocols used and are used to send information out. In a typical client-server communication, these are ports opened by the client on its own machine in order to send something to the server and they are closed as soon as the transmission is done, hence the term ephemeral. From a security perspective, it is not an issue.

Most firewalls will allow outgoing communications by default so in all likelihood, you will not need to do any firewall configuration. However, if your firewall blocks these outbound communications, consult the documentation for your firewall on how to enable these types of communications.

Basic Nomad architecture


Basic Nomad architecture



PortsNotes
UDP 1779

Step 1

By default, Nomad uses UDP Port 1779 to communicate during the election process for determining the master on a subnet. The Nomad installer will automatically add NomadBranch.exe,NomadPackageLocator.exe and PackageStatusRequest.exe to the list of excepted programs in the native Windows Firewall.

The default value for the port may be changed at install time using the P2PPORT installer property or post-installation by changing the P2P_Port registry value. If you change the default port, you must ensure all Nomad clients communicate using the same port.

The Nomad port (by default UPD Port 1779) must be open on all wireless access points to facilitate Nomad peer-to-peer communications. Not all vendors enable this port by default, please refer to the specific device vendor's documentation for details on how to enable ports on each WAP device.
TCP 80 (HTTP)
TCP 443 (HTTPS)

Step 2

Nomad Master requests LSZ file from Nomad running on the DP.
TCP 80 (HTTP)
TCP 443 (HTTPS)
TCP 139 (SMB)
TCP 445 (SMB over TCP)

Step 3

Nomad Master downloads content using Nomad as provider. This communication depends on how the DP is configured. It may be one of the following:
  • HTTP
  • HTTPS
  • SMB
  • SMB over TCP

For Configuration Manager the default setting is HTTP or HTTPS.

TCP 139 (SMB)
TCP 445 (SMB over TCP)
UDP 1779 (used for connectionless P2P)
TCP 5080 (HTTP)
TCP 5443 (HTTPS)

Step 4

Local copies from the Nomad master. The recommended way to facilitate Nomad cache access is to enable Windows File and Print Sharing. If this is not feasible on your network environment you can configure Nomad to use different means to access network shares, see Peer access to the Nomad cache for more details on configuring this option.

Connections may use one of the following:
  • SMB
  • SMB over TCP
  • Connectionless P2P
  • HTTP
  • HTTPS




Nomad pre-caching architecture and ports

Nomad and 1E WakeUp integration architecture and ports


Nomad SSD architecture and ports