LDAP Directory Error

[phamvinhdat]

I just set up Windows 2003 domain controller to use for LDAP Directory with CUCM 8.5, but I am running into error:

Error while Connecting to ldap://xxx.xxx.xxx.xxx:389, null

What should I checked for from either CUCM or Windows 2003? I try to look into real time log but could not find anything on this error.

Thanks.

Dat Pham

[Jonathan Schulenberg]

If the Windows 2003 server is a Global Catalog server the port would be 3268, not 389. Have you checked this?

[phamvinhdat]

I tried with the default Users OU and it is working ok, but not the newly created OU. I also have tried port 3268, and it still the same issue. I will have to try some different OU and see how that goes.

Thanks.

Dat Pham

[Jonathan Schulenberg · Accepted solution]

Two thoughts:

1. What are you using for a Search Base string? The default Users container violates a LDAP rule because you address it using CN= while a normal OU container would be OU=
   Examples:
   • CN=Users,DC=domain,DC=com
   • OU=People,DC=domain,DC=com
2. If you use another LDAP tool such as AD Explorer and connect with the same user credentials CUCM has, are you able to read user objects and attributes in the new OU you created? Perhaps the inherited permissions are denying access to the new container.

[phamvinhdat]

Jonathan,

Thanks for the pointer, LDAP Directory is working good now.

Dat

[asandborgh]

5 points Jonathan.  Logging in via AD Explorer also helped clarify what the distinguished name and search base should be in exact format since I could see them in the actual AD.

Thanks!!!

[Tyler Durden]

Ad Explorer was the only way I could find out how to get the LDAP working with my CUCM!

Thanks, great thread!!