NFS Services Administrator's Guide

NIS+ Error Messages
Appendix A394
Unable to authenticate NIS+ client
This message is generated when a server attempts to execute the
callback procedure of a client and gets a status of RPC_AUTHERR from the
RPC clnt_call. This is usually caused by out-of-date authentication
information. Out-of-date authentication information can occur when the
system is using data from a cache that has not been updated, or when
there has been a recent change in the authentication information that
has not yet been propagated to this server. In most cases, this problem
should correct itself in a short period of time.
If this problem does not correct itself, it may indicate one of the following
problems:
• Corrupted /var/nis/NIS_SHARD_DIR_CACHE file. Kill
nis_cachemgr, remove this file, and restart nis_cachemgr.
• Corrupted /var/nis/NIS_COLD_START file. Remove the file and then
run nisinit to recreate it.
• Corrupted /etc/.rootkey file. Run keylogin -r.
This message is generated by the NIS+ error code constant
NIS_CLNTAUTH.
Unable to authenticate NIS+ server
In most cases this is a minor software error from which your system
should quickly recover without difficulty. It is generated when the server
gets a status of RPC_AUTHERR from the RPC clnt_call.
If this problem does not quickly clear itself, it may indicate a corrupted
/var/nis/NIS_COLD_START, /var/nis/NIS_SHARD_DIR_CACHE, or
/etc/.rootkey file.
This message is generated by the NIS+ error code constant
NIS_SRVAUTH.
Unable to bind to master server for name 'string-variable'
See “If NIS+ Cannot Find an Object” on page 316. This particular
message may be caused by adding a trailing dot to the server’s domain
name in the domainname command or the NIS_DOMAIN variable in the
/etc/rc.config.d/namesvrs file.