On Windows 2008R2, here are the steps. This needs done on each DC I
As administrator in CMD on a DC:
connect to server DCNAME
set MaxConnIdleTime to TIMEVALUE (we used 3600 seconds)
Hope that helps!
On Tue, Dec 11, 2012 at 9:10 AM, Matthew M. DeLoera <mdeloera(a)exacq.com>wrote:
AD has an inactivity/idle default timeout of 900 seconds. I suspect
can google to find the setting name, and where it's stored, in your AD
Hope that helps.
On Dec 10, 2012, at 8:35 PM, Bryce Powell wrote:
Having done some more research, it appears that Active Directory also has
some settings that could result in disconnected connections. I experimented
with idle-timeout set to 30 seconds for the LDAP databases, but this seemed
to exacerbate the frequency of the errors. The behaviour exhibits as ‘dead’
connections, and LDAP does not appear to attempt to re-establish these
connections. Using the CentOS distro of OpenLDAP 2.4.23
Here are the slapd.conf settings:
uri "ldap://IP1/ ldap://IP2/ ldap://3/ ldap://IPn/"
uri "ldap://IP11/ ldap://IP12/ ldap://13/ ldap://IP1n/
I have some rewrite rules for bindDN, searchEntryDN, searchAttrDN,
matchedDN, but I don’t believe these settings are relevant to the issue at
Essentially I want the connections to be re-established without generating