Hi, Chetan C K wrote:
When searching the root domain naming context of Active Directory, you will probably get back a referral. You may not handle referrals correctly, or there is something wrong with your DNS setup.We have seen this too. In our case it works if the search is performed against a node of the AD domain for e.g. cn=users,dc=abc,dc=com It fails when the search base is "dc=abc,dc=com" with CONNECT_ERROR. The client is running on Solaris box.
It is possible that you have a DNS setup problem if the resolver library cannot resolve abc.com in your case. Active Directory likes returning referral including and LDAP URL that has a domainname instead of a hostname. If you use the DNS server of Windows 2000, then you would have A records for the abc.com in your DNS zone (of course, it is possible to set this up w/o the DNS server shipped with Windows 2000).
I hope this helps.
Bertold
Anyone seen this! Any help will be greatlt appreciated.Chet "Patrik Sj�gren" <[EMAIL PROTECTED]> wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]...Hi, I have written some code that binds to an LDAP server anonymously and serches the server for a list of all users. This code works fine on, e.g. IBM Directory server but fails when calling an AD. The bind is fine but the ldap_search_s() returns LDAP_CONNECT_ERROR nomatter what I do. Any ideas what could cause this problems would be greatly appreciated. Is there anything that has to be enabled within the AD to allow LDAP searches? Thanks/Patrik Sj�gren
