HP CIFS Server and Kerberos
94
ads_keytab_verify_ticket:
krb5_rd_req_return_keyblock_from_keytab(host/emonster.rose.hp.com@SNSLATC.HP.COM) failed:
Wrong principal in request
ads_keytab_verify_ticket:
krb5_rd_req_return_keyblock_from_keytab(host/emonster.rose.hp.com@SNSLATC.HP.COM) failed:
Wrong principal in request
ads_keytab_verify_ticket:
krb5_rd_req_return_keyblock_from_keytab(host/emonster.rose.hp.com@SNSLATC.HP.COM) failed:
Wrong principal in request
ads_keytab_verify_ticket: krb5_rd_req_return_keyblock_from_keytab(host/emonster.rose.hp.com@SNSLATC.HP.COM) failed:
Wrong principal in request
ads_keytab_verify_ticket: krb5_rd_req_return_keyblock_from_keytab succeeded for principal
cifs/emonster.rose.hp.com@SNSLATC.HP.COM
If you do not see the “keytab succeeded” log event, then it is likely that the service principal for the
user logon was not found in the keytab file. When CIFS/Samba is configured for keytab, a failed
keytab file search will be followed by a search in secrets.tdb for the valid service principal. The log
entry will display the keytab search followed by the secrets.tdb search. If the secrets.tdb search is
successful, then the log entries look like this:
[2008/10/28 10:33:17, 10] libads/kerberos_verify.c:ads_keytab_verify_ticket(111)
ads_keytab_verify_ticket:
krb5_rd_req_return_keyblock_from_keytab(host/emonster.rose.hp.com@SNSLATC.HP.COM) failed:
Wrong principal in request
[2008/10/28 10:33:17, 10] libads/kerberos_verify.c:ads_keytab_verify_ticket(111)
ads_keytab_verify_ticket:
krb5_rd_req_return_keyblock_from_keytab(host/emonster.rose.hp.com@SNSLATC.HP.COM) failed:
Wrong principal in request
[2008/10/28 10:33:17, 10] libads/kerberos_verify.c:ads_keytab_verify_ticket(111)
ads_keytab_verify_ticket:
krb5_rd_req_return_keyblock_from_keytab(host/emonster.rose.hp.com@SNSLATC.HP.COM) failed:
Wrong principal in request
[2008/10/28 10:33:17, 10] libads/kerberos_verify.c:ads_keytab_verify_ticket(111)
ads_keytab_verify_ticket:
krb5_rd_req_return_keyblock_from_keytab(host/emonster.rose.hp.com@SNSLATC.HP.COM) failed:
Wrong principal in request
[2008/10/28 10:33:17, 10] libads/kerberos_verify.c:ads_keytab_verify_ticket(111)
ads_keytab_verify_ticket:
krb5_rd_req_return_keyblock_from_keytab(host/emonster.rose.hp.com@SNSLATC.HP.COM) failed:
Wrong principal in request
[2008/10/28 10:33:17, 10] libads/kerberos_verify.c:ads_keytab_verify_ticket(111)
ads_keytab_verify_ticket:
krb5_rd_req_return_keyblock_from_keytab(host/emonster.rose.hp.com@SNSLATC.HP.COM) failed:
Wrong principal in request
[2008/10/28 10:33:17, 10] libads/kerberos_verify.c:ads_keytab_verify_ticket(111)
ads_keytab_verify_ticket:
krb5_rd_req_return_keyblock_from_keytab(host/emonster.rose.hp.com@SNSLATC.HP.COM) failed:
Wrong principal in request
[2008/10/28 10:33:17, 10] libads/kerberos_verify.c:ads_keytab_verify_ticket(111)
ads_keytab_verify_ticket:
krb5_rd_req_return_keyblock_from_keytab(cifs/emonster.rose.hp.com@SNSLATC.HP.COM) failed:
Decrypt integrity check failed
[2008/10/28 10:33:17, 3] libads/kerberos_verify.c:ads_keytab_verify_ticket(147)
ads_keytab_verify_ticket: krb5_rd_req failed for all 8 matched keytab principals
[2008/10/28 10:33:17, 10] libads/kerberos_verify.c:ads_secrets_verify_ticket(247)
ads_secrets_verify_ticket: enc type [18] failed to decrypt with error Bad encryption type
[2008/10/28 10:33:17, 10] libads/kerberos_verify.c:ads_secrets_verify_ticket(247)
ads_secrets_verify_ticket: enc type [17] failed to decrypt with error Bad encryption type
[2008/10/28 10:33:17, 10] libads/kerberos_verify.c:ads_secrets_verify_ticket(247)
ads_secrets_verify_ticket: enc type [16] failed to decrypt with error Bad encryption type
[2008/10/28 10:33:17, 10] libads/kerberos_verify.c:ads_secrets_verify_ticket(239)
ads_secrets_verify_ticket: enc type [23] decrypted message !