problem: adclient stayed in disconnected mode for a long period of time and never got back to connected mode even if there are valid and working domain controllers in the domain.
Cause: There are times when adclient fails to recover from disconnected mode because the background recovery thread is busy.
If a single task takes too much time could cause agebinding never gets a chance to recover. The cause of long running task observed could be <bg:MemberRefresh> <bg:krb5.conf> <bg:netstate>
Workaround: Currently the only workaround is restart centrifydc agent to free the stucked background thread.
Resolution: In release Suite 2017.2, we introduced two background threads responsible for performing different background tasks. This should prevent agebinding from not able to bring adclient back to connected mode.