This section has NIS Services FAQs for Native File Access for UNIX.
The Solaris NIS Clients to NetWare NIS Server has problems if the entry in the /etc/hosts file located in the Solaris client does not match the entry in etc/hosts file on NetWare or in DNS in a case-sensitive fashion.
To resolve this, modify the etc/hosts in the Solaris client to be in the same case as in etc/hosts on NetWare Server or in DNS.
The NISServ_Servername object holds the list of domains served by the NetWare NIS Server. It is created by the NISINST.NLM executed during the installation. For correct functionality of NIS Server, set the following parameters properly:
The schema might not be fully extended. This occurs when the NetWare 6 server is attached to a NetWare 5.1 tree.
Check ETC\SCHINST.LOG to view whether the schema is extended.
Nfsadmin might not be running.
Make sure that NFSADMIN is running on the target Server.
Make sure that ndsilib is running.
Check ETC\NIS.CFG to view whether the NisServer context and name are set properly.
Ensure that the NetWare server is set as the default NIS server of the UNIX system.
Use the UNIX command yppasswd for setting the NIS user password. The NISSWDD.NLM must be loaded on the NetWare server.
Execute ypset to set the default domain. The default domain must be the same as the UNIX client domain.
When an object is created on eDirectory replica 1 and before it replicates to all replica servers, another object with the same name is created from another replica, the name of one of the objects changes.
This ensures that the two objects have unique names. The name will be in the format number_n.
For example, the object name could be 0_2 or 0_3 with the NFAUUser appended as a suffix.
On viewing such objects, delete them.
You might be running makenis on a server with no DS replica and when the Master replica is down.
These messages are displayed erroneously.
You can view the list of domains served by the nisServer object in eDirectory in the following ways: