Cannot communicate with NISBIND. NIS Client access is disabled. Set NIS_CLIENT_ACCESS = 1 in the nfs.cfg and restart NIS Services.
Action:
In nfs.cfg, the configuration file, set NIS_CLIENT_ACCESS = 1 and restart NIS Services.
Default domain is not set. Run ypset <domainname> or specify the values of NIS_DOMAIN and NIS_SERVER parameters in the file sys:\\etc\\nfs.cfg and restart NIS services.
Action:
Make sure that the NISBIND is bound to the NIS server for some domain. You can verify this by executing ypset (which displays default domain binding) and ypwhich (which displays the NIS Server binding).
Failed to get the record for user x. Verify if the user x exists in eDirectory. (The name should be a Fully Qualified Name, e.g. ’.user.domain_U.novell’ or the Common Name e.g. ’user’)
Action:
Make sure that the user specified exists, or specify an existing and valid username.
User x does not belong to any NIS domain.
Action:
Make sure that the user specified belongs to at least one NIS domain.
RPC failure. Password daemon is not running.
Action:
If the master is a NetWare server, then nisswdd.nlm (passwd daemon) should be running there. If it is a UNIX or Linux machine, then passwd daemon is (usually) rpc.yppasswdd. Check if it is loaded.
User record was not found on the remote server.
Action:
Make sure that the user specified exists on the Master NIS server.
Password does not match the user password on master server.
Action:
Specify the password that matches the user password on the master server.