[root@hostname cucm]# net ads testjoin
kerberos_kinit_password hostname$@dc.COM failed: Client not found in Kerberos database
kerberos_kinit_password hostname$@dc.COM failed: Client not found in Kerberos database
Join to domain is not valid: Improperly formed account name
[root@hostname cucm]# wbinfo -t
checking the trust secret for domain dc via RPC calls failed
error code was NT_STATUS_DOMAIN_CONTROLLER_NOT_FOUND (0xc0000233)
failed to call wbcCheckTrustCredentials: WBC_ERR_AUTH_ERROR
Could not check secret
[root@hostname cucm]# net ads info
LDAP server: 10.1.1.6
LDAP server name: dc.domina.com
Realm: dc.COM
Bind Path: dc=dc,dc=COM
LDAP port: 389
Server time: Mon, 24 Apr 2017 15:37:58 EDT
KDC server: *.*.*.*
Server time offset: 0
[root@hostname cucm]# date
Mon Apr 24 15:38:05 EDT 2017
[root@hostname cucm]#


[root@hostname cucm]# net ads join -U adadmin
Enter adadmin's password:
Failed to join domain: failed to lookup DC info for domain 'dc.COM' over rpc: Access denied


Please help on this

What did you learn when you brought this error message

to the attention of the network admins?

Hi ,

Thanks for your reply.

We have already integrated with AD, unfortunately it has been disconnected.

So I try to re-join with AD.

Thanks

I fear I don't know enough about Kerberous to offer any technical suggestions. I just figured that, if it were in a Kerberos networked environment and was not connecting to Kerberos, the best persons to ask for help would be the network admins.

Good luck and thanks for the update. Let us know what the solution turns out to be; you might help someone else.

It's telling you that the domain dc.COM can't be found...you haven't configured something correctly, or something has changed. Not really another solution.

Also, have you done anything with samba here, or are you trying to? The samba tools don't always name things the way MS wants them....is your domain server an actual Windows server, or is it a Samba server acting as a DC? Check your kerberos settings:
...and examine the user principle name (UPN) in both the AD server and in LDAP. It should be servicePrincipleName+REALM, which is what's probably missing. Fix it in LDAP, export your keytab, and try kerberos again: