06-21-2010 03:07 AM - edited 03-15-2019 11:19 PM
Hi,
We have a CUCM 7.1 cluster & Unity Connection 7.1 both integrated with Microsoft AD. All is working fine & has been for several years........but i just noticed something recently when i forced a manual sync.
It comes up with error "Failed to Connect to ldap://<IP ADDRESS>:389" and also "Update Successful". The IP address in the error message is the IP of the redundant AD server. This same error appears on CUCM & Unity Connection when forcing a manual sync.
So my question is.....is this normal behaviour? Will it only connect to the primary AD server unless it is unreachable?
I can ping both AD servers from CUCM Publisher
T.I.A
Russell
06-21-2010 05:53 AM
Maybe port 389 was disabled on the redundant AD?
You may test the port connectivity by using telnet from Windows command prompt.
telnet ip_address 389
Michael
06-21-2010 08:43 AM
Thanks Michael......shouldn't have believed client's assumption that there was nothing wrong with the AD server without first checking it myself
Reboot of AD server fixed issue
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: