1E 8.1 (on-premises)

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 MODULE.NOMAD.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:

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 Nomad cache for more details on configuring this option.

Connections may use one of the following:

N/A

Step 1

Choose a package and run the Nomad pre-caching wizard, selecting the target device collection. This step does not require any port configuration but the Nomad Configuration Manager console extensions must be installed in the Configuration Manager Console.

TCP 80 (HTTP)

TCP 443 (HTTPS)

Step 2

The Nomad pre-caching wizard stores the target device and package information in Tachyon.

TCP 80 (HTTP)

TCP 443 (HTTPS)

Step 3

The Nomad clients, where the pre-cache feature has been enabled, poll Tachyon every 24 hours to see if they need to pre-cache some content. This takes the form of pre-caching notifications that tell the Nomad clients they need to process a download job to fetch the specified content.

TCP 80 (HTTP)

TCP 443 (HTTPS)

Step 4

The Nomad clients, with pre-caching notifications, contact the Management Point to locate the Distribution Point that holds the content. This may use HTTP or HTTPS depending on how the Management Point is configured.

TCP 80 (HTTP)

TCP 443 (HTTPS)

TCP 139 (SMB)

TCP 445 (SMB over TCP)

Step 5

A Nomad Master election takes place and the elected master processes the job by downloading the pre-cache content using Nomad as provider. This is then distributed locally to the Nomad peers that also require the pre-cached content. This communication depends on how the DP is configured. It may be one of the following:

For Configuration Manager the default setting is either HTTP or HTTPS.

TCP 80 (HTTP)

TCP 443 (HTTPS)

Step 1

Nomad systems on the branch site register in Content Distribution the content they hold in their shares

TCP 80 (HTTP)

TCP 443 (HTTPS)

Step 2

Nomad Masters get information on which Nomad systems hold specific content

TCP 80 (HTTP)

TCP 443 (HTTPS)

TCP 139 (SMB)

TCP 445 (SMB over TCP)

Step 3

Nomad Master fetches a package from the registered Nomad share on a neighboring subnet