1 of 1 people found this helpful
we have a similar problem at a customer. Did you find a solution for this?
I don't think it is landesk related because when I configure a LDAP connection and point it to a dc and not only to the domain it works. Maybe something is wrong with you second DC "CCS-DC2" or DNS.
By the way I opened a case with LANDesk support, maybe they know about the problem and have a final solution for this.
Hope it helps.
I've seen it before when the DC used by LANDesk doesn't have the dnsHostName property configured correctly in the AD. In your case the CCS-DC2. I've used the steps in this document to fix it:
When you connect directly to a DC it might work, but be careful, when you ever discontinue the use of that DC, all configured LDAP queries etc. connected to that group will be gone too.
Solved a big problem in our environment!