Windows 7 nis client

View all page feedback. In this article. Specifies the remote computer you want to administer. Specifies the user name of the user whose credentials are to be used. Specifies the password of the user specified using the -u option. If you specify the -u option but omit the -p option, you are prompted for the user's password.

Specifies general settings for Server for NFS. One of the following arguments is required: eventlog - Specifies that audited events will be recorded only in the Event Viewer application log. The default maximum size is 7 MB. Don't use all with any other event name. The Overflow Blog.

Podcast Helping communities build their own LTE networks. Podcast Making Agile work for data science. Featured on Meta. New post summary designs on greatest hits now, everywhere else eventually. Related 2. Hot Network Questions. Question feed. Server Fault works best with JavaScript enabled. Accept all cookies Customize settings. Yes No. Thank you! Any more feedback? The more you tell us the more we can help.

Can you help us improve? Resolved my issue. Clear instructions. Easy to follow. No jargon. Pictures helped. Didn't match my screen. Incorrect instructions. If your system is connected to the internet, an attacker could guess the NIS domain and request a list of all NIS users.

Even though their passwords are stored in encrypted format, it is still possible for obvious or dictionary word passwords to be discovered by a brute-force attack on the password encryption. For this reason, it is wise to limit the addresses of clients that connect to the server to only those Unix systems that are really clients.

To set this up, the steps to follow are:. It is a good idea to at only clients on your own network to connect, and deny all others. An even more secure alternative would be to allow only those systems that you know are NIS clients, assuming they have fixed IP addresses and do not change often. Even if you restrict access to only trusted client systems, users who can login to those systems via SSH or telnet may still be able to get a list of all NIS users and their encrypted passwords.

To prevent this, it is possible to configure the server to only allow clients using trusted ports to access certain tables or fields within tables. Because on Unix systems only the root user can create TCP or UDP sockets with port numbers below , these low ports are considered trusted and safe from use by regular users.

It is also possible to prevent certain clients from accessing some NIS tables, but still allow them access to others. For example, you might want to give all client systems access to the Host addresses table, but only a trusted few the rights to the Unix users table.

The most useful use of the Client map restrictions table is to add a row for all clients on the passwd. Then add another row for the passwd. These will prevent non-root users from seeing encrypted password, while still allowing programs running as root such as the telnet or SSH server. If you are using the separate shadow table to store passwords and expiry information, the restriction should be on the shadow.

On many Linux distributions, a restriction like this exist by default. Slave NIS servers are used in a similar way to secondary DNS servers — they keep a copy of the tables held by the master server, and can be used by clients if the master fails or is slow to respond.

If you are using NIS on a very large network that has multiple LANs connected by slow links, it may also make sense to put a slave server on each LAN so that clients can use it instead of the master. On OpenLinux, there is no way to setup a slave server using Webmin due to the unique NIS configuration files used by the distribution. On all other versions of Linux, the steps to set up a system as a slave server:.

Make sure that the master server has the address of this slave entered into the Slave servers field on the server configuration form. It should also have the Push updates to slave servers? If not, you can use the yppush command to send the contents of an NIS table to a some or all slave servers. The module has a few configurable options that can be changed by clicking on the Module Config link in the top-left corner of the main page.