How it works

On start up, the Nomad service starts the HTTP server logs a list of URLs it listens to.

When any Nomad client wants to download content, it does an election and identifies a machine which has content in its cache (the Master machine). During the elections, the protocols supported by a client are not shared. Based on the local client's configuration, it chooses the protocol to use for downloading content from master. Our example below illustrates the the connection to PC1 machine using HTTPS protocol.

When a Nomad client is configured to use multiple protocols, the order of preference is HTTPS, HTTP followed by SMB. When files are downloaded, the logging is prefixed P2P_http to differentiate it from a SMB download. Both HTTP and HTTPS will use the same prefix.

Common error conditions

HTTP/HTTPS specific failures are most likely to occur when connecting to master. Common errors you will encounter are:

Raising a support ticket

When you raise a support case with us for P2P HTTP/HTTPS file transfer issues, remember to attach the necessary log files and identify the Package ID, Deployment date and time for it.

  • C:\ProgramData\1E\NomadBranch\Logs\NomadBranch.log 
  • C:\Windows\CCM\Logs\CAS.log
  • C:\Windows\CCM\Logs\CTM.log