I am assuming this was working as expected before. If it was, then it's better to think if there was a change. Otherwise you need set up the client to debug and reproduce the issue.
Without knowing your setup, it's a bit challenging to understand. My advice is that first, you make sure your clients are healthy (that they can talk to AD without issues).
First, inspect the output of this command:
sudo adinfo -y netstate
Make sure there are no issues with communications with DCs, that sites are properly populated as well as subnets.
Once you have cleared the issues yielded by adinfo, if the problem persists, then you need to look at the debug log.
Enabling Debugging with Centrify DirectControl
The key here is to monitor the [systemlog]/centrify.log file while you're trying to reproduce the issue.
The normal sequence is like this:
sudo /usr/share/centrifydc/bin/addebug clear
(will clear any previous debug log /var/log/centrifydc.log)
sudo /usr/share/centrifydc/bin/addebug on
(will turn debug ON) and watch for any errors.
[This is where you try to reproduce your issue]
Make sure /var/log/centrifydc.log is growing in size.
When you're done
sudo /usr/share/centrifydc/bin/addebug off
(turns OFF debug logging)