Description of problem: Whenever a connection times out with a T2 error, the 389 server will not accept any new connections. All existing connections function perfectly Version-Release number of selected component (if applicable): 389 1.2.7-5 from fc 14 directory How reproducible: 100% of the time a T2 message is logged Steps to Reproduce: 1. A host cause the 389 server to disconnect with a a T2 error 2. Try to reconnect from any host and it will be denied Actual results: Server disconnections connection with an error and does not allow any new connections to occur Expected results: Server drops the connection with an error but continues to allow new connections to be made Additional info:
*** This bug has been marked as a duplicate of bug 668619 ***