Connecting with ldap 2.6 to w2k Active directory failed - Error 91

General Discussion about LDAP Administrator

Moderator: Support

Connecting with ldap 2.6 to w2k Active directory failed - Error 91

Postby Bastien » Wed Jun 20, 2007 12:49 pm

Hello,

i have installed a w2k server and xp client and connected both with a network crossover cable (the server/client is not connected to the Internet). The xp client is in the domain of the w2k servr. I run ldap browser with the w2k`s servername: bnserver.bndns.de entered in the ldap url, used port 389 without ssl and ldap v3. The Base DN remained empty and my user DN was administrator@bndns.de with my password all entered in the ldap browser.

Trying to connect to the AD i get the error 91: can`t connect to the ldap server??

Someone can help a desperated man?

cheers,

Bastien
Bastien
 
Posts: 7
Joined: Wed Jun 20, 2007 12:23 pm

Postby Support » Thu Jun 21, 2007 7:21 am

Error 91 means that the underlying LDAP API could not establish a TCP/IP connection to the host specified. This is a pure connectivity issue and it's not directly related to the product. Here is a troubleshooting checklist:

- Make sure there is no typo in your server profile settings. A typo in the host name field is the most common mistake.
- Make sure DNS works fine on the PC where you run LDAP Browser. Both direct (host name to IP address) and reverse (IP to host name) resolving should work for the host where your LDAP server resides. You can check DNS with help of 'nslookup' command line tool.
- Make sure the destination host is reachable via TCP\IP (use ping.exe)
- Make sure there is no firewall rules that block your workstation from accessing destination host:port. This can be done using 'telnet' application or special network tools
Last edited by Support on Wed Jun 27, 2007 9:11 am, edited 1 time in total.
Support
 
Posts: 896
Joined: Sun Aug 12, 2001 12:00 am

Postby Bastien » Tue Jun 26, 2007 9:23 am

- Make sure the destination host is reachable via TCP\IP (use ping.exe)


that worked fine

- Make sure DNS works fine on the PC where you run LDAP Browser. Both direct (host name to IP address) and reverse (IP to host name) resolving should work for the host where your LDAP server resides. You can check DNS with help of 'nslookup' command line tool.


that was the problem, the DNS did not work properly as i have had many errors in the event log file of my w2k active directory :-(
Bastien
 
Posts: 7
Joined: Wed Jun 20, 2007 12:23 pm


Return to General Discussion

Who is online

Users browsing this forum: No registered users and 1 guest

cron