Re: RE: LDAP connections to the proper server, and unknown error??

[jmcmeek@xxxxxxxxxx]

I forgot one other thing I was going to say...

There was mention of LDAP_SERVER_DOWN errors.  Those could be from one of 
the following (among others)...

If the problem is because of how the client handles referrals (problem 
fixed by PTF), Active Directory closes the client connection after 
returning LDAP_PROTOCOL_ERROR.  Depending on the timing, the client may 
see the response message first and return protocol error, or it may see 
that the connection has been closed unexpectedly, and return 
LDAP_SERVER_DOWN.

Also related to referrals, is that Active directory returns referrals that 
use the domain name as the server name.  If you are not using one of the 
Windows 2000/2003 servers as your DNS on i5/OS, it is possible that your 
DNS is not resolving the domain name to one of the servers holding Active 
Directory for the domain.  Windows 2000 uses DNS to locate many resources 
for the domain.  For example, to find LDAP servers for the domain 
mycompany.com, the Windows client does a DNS query roughly equivalent to a 
lookup for ldap_.tcp_.mycompany.com (it actually uses DNS SRV records, and 
I probably have the string wrong, but hopefully you get the idea).  It 
does the same thing for other network services.

John McMeeking