1) Identify the ports needed to open:

In our CUST domain, the ports used for Active directory are published in this article: What firewall ports are used by Active Directory? However these ports assume that the RPC port has been configured to be static. In our CUST domain, it has been configured for TCP 1025. The default AD installation is to use TCP ports above 1023, but you can also set the static RPC TCP port by following these instructions: Active Directory Static RPC Port on each Domain controller.

The above chart assumes you have configured the static RPC port to TCP 1025 instead of the default ports TCP Greater than 1023.

2) Where to open the firewall.

- If this is for Hybrid cloud you will need to open up the ports on the Cloud firewall (Cloud GUI) as well as the firewall on the Ash01 (Standard Text through networking Team) side.

- If you have two networks in cloud (DMZ and Trust) you will want to open up the firewall for each network.

The Atempo backup software is VERY sensitive to DNS names as well as case.  In other works, it tends to be very compliant to what you would normally expect from a Linux server.  Therefore, there are (2) general scenarios where this problem manifests itself:

If the server name is not resolvable to the backup client, backup server and backup admin station - in this configuration, it is normal that the server will not be accessible via the Atempo console.  to resolve this typically you have to fix the DNS entries to match across all systems so that the name is resolvable to the right IP Address. 

If the backup client and backup server are not of the same version, connecting directly to the backup client for administration is usually not allowed - Currently, the only way to fix this is to upgrade the client to the latest version the backup server is running.  However, to work around this issue, you can manually enter in the inclusions into the interface or you can log into the GUI from the backup client (Windows only) and try to administer the settings from there.