LDAP authentication randomly has issues after upgrading to Server 2008 R2 domain

Hello,

We have been running ejabberd for quite some time now with very few issues. Ever since we upgraded our domain from 2003 to 2008 R2, we have a strange problem. Sometimes a user cannot log in and has to keep trying over and over and it will eventually work. It really seems to hit remote users over the VPN more often, but it happens locally as well. Sometimes you just have to retry once, other times it can take many tries.

Any suggestions on where to look would be useful. I don't see any errors in the ejabberd.log file, but I do see these quite often:

=WARNING REPORT==== 2011-06-03 09:03:59 ===
W(<0.292.0>:eldap:589) : LDAP server closed the connection: dcserver:389
In State: active

Tamerz wrote: I do see these

Tamerz wrote:

I do see these quite often:

=WARNING REPORT==== 2011-06-03 09:03:59 ===
W(<0.292.0>:eldap:589) : LDAP server closed the connection: dcserver:389
In State: active

That report is logged when ejabberd notices that the TCP connection to the LDAP server gets closed.

Syndicate content