Solaris DHCP Administration Guide

NIS+ Not Adequately Configured

After you successfully use NIS+ with DHCP, you might encounter errors if changes are made to NIS+ and introduce configuration problems. Use the following table to help you determine the cause of configuration problems.

Table 5–1 NIS+ Configuration Problems

Possible Problem 

Gather Information 

Solution 

Root object does not exist in the NIS+ domain.  

Enter the following command:  

/usr/lib/nis/nisstat

This command displays statistics for the domain. If the root object does not exist, no statistics are returned.

Set up the NIS+ domain using the Solaris Naming Setup and Configuration Guide.

NIS+ is not used for passwd and publickey information.

Enter the following command to view the name service switch configuration file:  

cat /etc/nsswitch.conf

Check the passwd and publickey entries for the “nisplus” keyword.

Refer to the Solaris Naming Setup and Configuration Guide for information about configuring the name service switch.

The domain name is empty. 

Enter the following command:  

domainname

If the command lists an empty string, no domain name has been set for the domain. 

Use local files for your data store, or set up an NIS+ domain for your network. Refer to Solaris Naming Setup and Configuration Guide.

The NIS_COLD_START file does not exist.

Enter the following command on the server system to determine if the file exists:  

cat /var/nis/NIS_COLD_START

Use local files for your data store, or create an NIS+ client. Refer to Solaris Naming Setup and Configuration Guide.