Closed Bug 1335 Opened 26 years ago Closed 26 years ago

Search problems against Exchange LDAP servers

Categories

(Directory :: PerLDAP, defect, P2)

All
Solaris

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: leif, Assigned: leif)

Details

A number of reports have come in re: weird search problems against an Exchange LDAP server. I don' tknow what is going on, and I need to get my hands on an Exchange server (and/or an NT 5 box with Active Directory). I'm attaching a couple of mail messages.
Thank you for responding so quickly. I am using the Netscape Directory SDK 3.0 for C Beta 1 which I downloaded from the Netscape web site: http://developer.netscape.com/. I am only using the SSL version because that is the only one that is available to me over the internet. The memory usage during the hanging search does not seem to go up. The exact search I use for persons with a phone number of 2000 is as follows: ldapsearch -b "o=Mitel" -h PC345 -s subtree "telephoneNumber = 2000" this search yields the following: dn: cn=JoeB,cn=Recipients,ou=PC345D,o=Mitel objectClass: organizationalPerson objectClass: person objectClass: Top rdn: JoeB cn: Joe Bofespon distinguishedName: cn=JoeB,cn=Recipients,ou=PC345D,o=Mitel rfc822Mailbox: JoeB@PC345D.Mitel.com mail: JoeB@PC345D.Mitel.com textEncodedORaddress: c=US;a= ;p=Mitel;o=PC345D;s=Bofespon;g=Joe; description: 6263263426337766 description: 62632633563 givenName: Joe uid: JoeB MAPI-Recipient: TRUE sn: Bofespon facsimileTelephoneNumber: 4003 telephoneNumber: 2000 I use an identical search for Joe using his givenName attribute. ldapsearch -b "o=Mitel" -h PC345 -s subtree "givenName=Joe" That search hangs. It seems if I search for pure numerical attributes such as description, telephoneNumber and facsimileTelephoneNumber I get results returned. However if I search for string type attributes, ldapsearch will hang and never return. I find this odd since all documentation I have read indicates that both telephoneNumber and givenName are stored as Unicode strings in the Exchange server. Does the fact that I am using the Netscape SDK with Exchange's LDAP directory have anything to do with this? The exact searches I've mentioned above work perfectly with version 1.0 of the Directory SDK. I hope I have provided you with useful information. Thanks in advance, Mich > ---------- > From: Leif Hedstrom[SMTP:leif@netscape.com] > Sent: Friday, September 18, 1998 2:58 AM > To: Kevin Tsurutome > Cc: Crichton, Michel; Fletcher Jones > Subject: Re: ldap with ssl version 3.0 > > > First, is your suffix really "" ? That won't work properly with new > Netscape > Directory servers for instance, since "" is a reserved suffix. In any > case, I > tried the command above (changing "-b" to use our suffix), and it > certainly > does return the entries I'd expect (I've tried the "ldapsearch" that > ships > with Netscape DS-3.1, and with DS-4.0, both worked fine). Also, you > can leave > out the -D and -w above, if you don't bind as a user, you are > anonymous by > default. > > Is your database very large? Could you possibly run into size limits? > I > assume you do have an an "eq" index on the givenName attribute? Is > there > anything in the error logs? Does the slapd process start using up a > lot of > CPU when the ldapsearch is running? > > Also, what exactly does this have to do with SSL? The call above > clearly > won't use SSL, since you haven't provided a cert DB file for the > client to > use. Perhaps you can explain your problem a little more in detail, and > hopefully we can figure out where's it's going wrong. > > -- leif > >
That attachment was sent by "Crichton, Michel" <michel_crichton@Mitel.COM>
Status: NEW → ASSIGNED
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
QA Contact: 3849
sent a request to michel_crichton@Mitel.COM to see if they can verify the fix.
received no response from originator of mailnote, asking Leif if he can verify.
Status: RESOLVED → VERIFIED
We believe this was solved with anothe bug fix, I have no way of verifying this, and I've not heard of any problems after the bug fix was done.
You need to log in before you can comment on or make changes to this bug.