While using HA mode in an Active Directory-based environment, the connection to AD DC might fail when the master goes down. The hostname of the slave and master are identical in this scenario. The slave appliance cannot join the domain configuration. The error "Cannot connect to domain controller right now" might be shown.
This article provides instructions on how to work around such a problem.
The Hostname of the Master device is synced to the Slave device during HA initiation. As a result, the Domain Controller would not allow joining two devices with the same hostname. However, the Directory Services configuration can be changed after the initial HA sync.
- On the device that is currently showing, "Cannot connect to domain controller right now", please proceed with the Join Domain
- Enter your Domain and for the Kerio Control Server Name, enter a different hostname than the default, i.e. control2.
Check both Kerio Control installations (Master and Slave) to confirm the domain is joined.