On Fri, Nov 08, 2002 at 12:30:40AM -0500, Igor Brezac wrote:
> It looks like you are hitting ldap_timeout, default is 5 seconds. You
> might fix the problem if you increase the value of this parameter.
You're always right Igor!, It was an indexing problem. We have 6500
users into our LDAP users d
On Thu, 7 Nov 2002, Felix Cuello wrote:
> On Thu, Nov 07, 2002 at 11:20:22AM -0500, Kervin L. Pierre wrote:
> > Try running ethereal and listening to the ldap traffic when the bad
> > logins occur. Or running OpenLDAP with extra logging.
>
>
> Sorry for the long post, but... do you think that thi
On Thu, Nov 07, 2002 at 11:20:22AM -0500, Kervin L. Pierre wrote:
> Try running ethereal and listening to the ldap traffic when the bad
> logins occur. Or running OpenLDAP with extra logging.
Sorry for the long post, but... do you think that this could be the
problem?, How can I solve that?
S
saslauthd+ldap is very reliable for me. I had this one issue which seem
ed to occur when I restarted OpenLDAP, but I think that's been fixed in CVS.
Maybe you should upgrade LDAP to 2.1.x series?
Try running ethereal and listening to the ldap traffic when the bad
logins occur. Or running Ope
Hello!
I'm actually working with Cyrus 2.1.9 and sasl2.1.9 and sometimes
(solved the entrophy problem) my POP server sometimes returns
incrrect username or password. It could be because I'm using ldap
beta support of saslauthd?. I'm working with LDAP 2.0.23.
Thanks a lot!
Felix
