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

It's not all over yet, but Hooray! I used the name of one of the boxes where 
part of the LDAP directory resides, and it got data for the ldapsearch command. 
 BUT it is only one of the relevant boxes. It's a distributed directory, so I 
don't want one box, I want to use the DNS name, "compxxx.com". Using that names 
frees you from depending on the uptime on the boxes or all their specific names 
and all that and frees one from other such changes. AND, "compxxx.com" WORKS 
already for the other systems here...

So while there is progress, on a first debug walk-through, I get the 
LDAP_PROTOCOL_ERROR (=2) returned for ldap_search() but then no error on 
ldap_search_st(). On the ldap_search_st() it returned an actual non-null 
pointer for the *result parameter. But then it gave me *NULL for the 
ldap_first_entry(). 

So I'll be doing two things: 
(1)Calling IBM again to try to get clarity on how the client side LDAP resolves 
these names, 
(2)Revisit the best corporate name with the MS guy here who's used the LDAP 
functionality over the local network, 
(3)Resolve why it's coughing up at the search. 

By the way, I don't know why, but using -v gave me one line of data back rather 
than the multiple screens without it.

This did it: 

ldapsearch -h BOXNAME -s base -b "DC=repsrv,DC=com" "objectclass=*"

Also, I've got to do a crash course in how the server handles this.. 

--Alan