Cannot determine realm for host Cause: Kerberos cannot determine the realm name for the host.Solution: Make sure that there is a default realm name, or that the domain name mappings are set up in the Kerberos configuration file ( section.Credentials cache I/O operation failed XXXCause: Kerberos had a problem writing to the system's credentials cache (.Field is too long for this implementation Cause: The message size that was being sent by a Kerberized application was too long.Illegal cross-realm ticket Cause: The ticket sent did not have the correct cross-realms.The realms might not have the correct trust relationships set up.Solution: Make sure that the realms you are using have the correct trust relationships.Improper format of Kerberos configuration file Cause: The Kerberos configuration file has invalid entries.
Can't open/find Kerberos configuration file Cause: The Kerberos configuration file ( and readable by everyone else.Solution: Make sure that the server you are communicating with is in the same realm as the client, or that the realm configurations are correct.Client or server has a null key Cause: The principal has a null key.Authentication negotiation has failed, which is required for encryption. Cause: Authentication could not be negotiated with the server.Solution: Start authentication debugging by invoking the command and look at the debug messages for further clues. Bad krb5 admin server hostname while initializing kadmin interface Cause: An invalid host name is configured for (1) man page.
Client did not supply required checksum--connection rejected Cause: Authentication with checksum was not negotiated with the client.