Opensuse nis server setup

Select Allow Changes to Passwords to allow users in your network both local users and those managed through the NIS server to change their passwords on the NIS server with the command yppasswd. Leave this dialog with Next or click Other Global Settings to make additional settings. In addition, passwords can be merged here.

Click OK to confirm your settings and return to the previous screen. If no slave servers exist, this configuration step is skipped. Continue to the dialog for the database configuration.

The default settings are usually adequate. Leave this dialog with Next. Check which maps should be available and click Next to continue. Determine which hosts are allowed to query the NIS server. You can add, edit, or delete hosts by clicking the appropriate button. Specify from which networks requests can be sent to the NIS server. Normally, this is your internal network. In this case, there should be the following two entries:. The first entry enables connections from your own host, which is the NIS server.

Normally, this is your internal network. In this case, there should be the following two entries:. The first entry enables connections from your own host, which is the NIS server. The second one allows all hosts to send requests to the server. To configure additional NIS slave servers in your network, proceed as follows:. Adapt the firewall settings with Open Ports in Firewall.

Enter the hosts that are allowed to query the NIS server. Specify all networks from which requests can be sent to the NIS server. If it applies to all networks, use the following configuration:. The second one allows all hosts with access to the same network to send requests to the server. Enter the NIS domain. Enter your NIS servers and separate their addresses by spaces. Depending on the size of your local network, this may be a time-consuming process. Broadcast asks for a NIS server in the local network after the specified servers fail to respond.

Depending on your local installation, you may also want to activate the automounter. Originally Posted by Knurpht. I'm writing right now. Have a little patience, I'm copying the situation from my server and clients. Maybe better in a couple of posts.

This provides the Yast2 configuration module for the NIS server. This provides the Yast2 configuration module for the NFS server.

These two actions will pull in more packages, when needed. Accept that. NIS Configuration Start Yast2, if it was already open, restart it to load the newly installed module s. Now the users existing on the server can login on the client.

If you have any questions, don't hesitate. When I restart, I see "nisuser" which I've defined on the server. That's creating a path problem. Just keep this in mind: if you enable all, and it does not work, you can always boot into runlevel 3, by entering "init 3" on the options line, login as root, start Yast in the console and disable the NIS client until you got it sorted. It's working perfectly. Excellent howto.