NFS Services Administrator's Guide

NIS+ Error Messages
Appendix A 391
• The client’s key pair has been changed and the client has not run
keylogin on the client system so that system is still sending the
client’s old secret key to the server, which is now using the client’s
new public key. Naturally, the two do not match. Run keylogin
again on both client and server.
• Network corruption of data. Try the command again. If that does not
work, investigate and correct any network problems. Then run
keylogin again on both server and client.
_svcauth_des: decryption failure for principal-name
_svcauth_des: encryption failure
DES decryption for some authentication data failed. Possible causes are
as follows:
• Corruption to a library function or argument.
• A problem with a DES encryption chip, if you are using one.
The severity of this message depends on what level of security you are
running. At a low security level, this message is primarily for your
information; at a higher level, you may have to call your HP support
contact for assistance. If the problem appears to be related to a DES
encryption chip, call your HP support contact.
_svcauth_des: invalid timestamp received from principal-name
The time stamp received from the client is corrupted, or the server is
trying to decrypt it using the wrong key. Possible causes are as follows:
• Congested network. Retry the command.
• Server cached out the entry for this client. Check the network load.
_svcauth_des: key_decrypt
sessionkey failed for principal-name
The keyserv process failed to decrypt the session key with the given
public key. Possible causes are as follows:
•The keyserv process is dead or not responding. Use ps -ef to check
whether the keyserv process is running on the keyserv host. If it is
not, then restart it and run keylogin.
• The server principal has not run keylogin. Run keylogin for the
server principal.