Creating Additional Client Machines
Repeat the preceding client-initiation procedure on as many machines as you like. To initiate clients for another domain, repeat the procedure but change the domain and master server names appropriately.
The sample NIS+ domain described in this chapter assumes that you will initialize four clients in the doc.com. domain. You are then going to configure two of the clients as non-root NIS+ servers and a third client as a root replica of the root master server of the doc.com. domain.
Note - You always have to make a system into a client of the parent domain before you can make the same system a server of any type.
Initializing NIS+ Client Users
After a machine has become an NIS+ client, the users of that machine must add themselves to the NIS+ domain. Adding a user to the domain means changing the Secure RPC password to that user's login password. What actually happens is that the user's password and the Secure RPC password are bound together. This procedure uses the nisclient script.
Prerequisites to Running nisclient
Before you can use the nisclient script to initialize a user:
The domain must have already been configured and its master server must be running.
The master server of the domain's tables must be populated. (At a minimum, the hosts table must have an entry for the new client machine.)
You must have initialized a client machine in the domain.
You must be logged in as a user on the client machine. In this example, the user is named user1.
Optionally, if using DES authentication, the client machine must use the same Diffie-Hellman key configuration as that used on the master server.
Information You Need
You need:
A user's login name (user1 in this example)
The default Secure RPC password (nisplus in this example)
The login password of the user who will become the NIS+ client
How to Initialize an NIS+ User
To become an NIS+ client, enter the following nisclient command while logged in as the user.
user1prompt% nisclient -u At the prompt below, type the network password (also known as the Secure-RPC password) that you obtained either from your administrator or from running the nispopulate script. Please enter the Secure-RPC password for user1:
Enter the Secure RPC password, which is nisplus in this case.
The password does not echo on the screen.
Please enter the login password for user1:
Type the user's login password and press Return.
The password does not echo on the screen.
Your network password has been changed to your login one. Your network and login passwords are now the same
This user is now an NIS+ client. You need to have all users make themselves NIS+ clients.
Setting Up NIS+ Servers
Now that the client machines have been initialized, you can change any of them to NIS+ servers of the following types:
To be root replicas--to contain copies of the NIS+ tables that reside on the root master server
To be master servers of subdomains of the root domain
To be replicas of master servers of subdomains of the root domain
Note - You can have only one NIS+ master root server. Root NIS+ servers are a special type of NIS+ server. This section does not describe how to configure a root master server; see "Setting Up NIS+ Root Servers" for more information.
You can configure servers any of these different ways:
Without NIS compatibility
With NIS compatibility
With NIS compatibility and DNS forwarding--you only need to set DNS forwarding if you are going to have SunOS 4.x clients in your NIS+ namespace.
Servers and their replicas should have the same NIS-compatibility settings. If they do not have the same settings, a client that needs NIS compatibility set to receive network information may not be able to receive it if either the server or replica it needs is unavailable.
This example shows the machine client1 being changed to a server. This procedure uses the NIS+ rpc.nisd command instead of an NIS+ script.
Prerequisites to Running rpc.nisd
Before you can run rpc.nisd:
The domain must have already been configured and its master server must be running.
The master server of the domain's tables must be populated. (At a minimum, the hosts table must have an entry for the new client machine.)
You must have initialized the client machine in the domain.
You must be logged in as root on the client machine. In this example, the client machine is named client1.
Optionally, if using DES authentication, the client machine must use the same Diffie-Hellman key configuration as that used on the master server.