Message -
From: Todd Bierbaum [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, May 21, 2004 10:35 AM
Subject: [IMail Forum] KillerLDAP and MS Active Directory
Has anyone had any experience using Killer LDAP to query Active
Directory? I want to provide a global address book to my
PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Todd Bierbaum
Sent: Friday, May 21, 2004 7:35 AM
To: [EMAIL PROTECTED]
Subject: [IMail Forum] KillerLDAP and MS Active Directory
Has anyone had any experience using Killer LDAP to query Active
Directory? I want to provide a global address book to my
.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Todd Bierbaum
Sent: Friday, May 21, 2004 7:35 AM
To: [EMAIL PROTECTED]
Subject: [IMail Forum] KillerLDAP and MS Active Directory
Has anyone had any experience using Killer LDAP to query Active
Directory? I want
Has anyone had any experience using Killer LDAP to query Active
Directory? I want to provide a global address book to my webmail
clients. In Outlook you can setup a Internet Directory Service Address
Book that will query AD and return all the users with valid e-mail
address in their account
Has anyone had luck using KillerLDAP with Active Directory's
LDAP? If so, did you have any issues, like 'error 32' which is
actually 'no such object(0x20)'
TIA,
Dave
we use it with success. sometimes though the ldap server kinda goes screwy (although I
don't think we get error 32).
however, stop/restart the ldap service and see if that helps
oh, also do an optimize ldap as well.
also, when we implemented, a couple years ago we had a problem with
)?
-Original Message-
From: Bob McGregor [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 01, 2003 3:48 PM
To: [EMAIL PROTECTED]
Subject: Re: [IMail Forum] KillerLDAP
we use it with success. sometimes though the ldap server kinda
goes screwy (although I don't think we get error 32
: [IMail Forum] KillerLDAP
we use it with success. sometimes though the ldap server kinda goes screwy (although I
don't think we get error 32).
however, stop/restart the ldap service and see if that helps
oh, also do an optimize ldap as well.
also, when we implemented, a couple years ago we had