Changes

Jump to: navigation, search

OPS335 NIS Lab

108 bytes added, 05:14, 12 July 2016
m
Switching section headings over to 'investigation' format.
==NIS (Network Information Services)==
* An NIS server is used to synchronize system files and other information between machines in an NIS domain.
* In this lab you will set a Fedora VM as both an NFS and NIS server. You will then use and share user information (names, groups, and passwords) with your other VM's to serve as your NFS and NIS clients.{{Admon/important|Prerequisites|Before you begin make sure all your machines are up to date (dnf update).Ensure both host and VM's have firewalls set up according to prior labs and all labs have been completed. Ensure that your NFS server is running on VM2 and exporting the '/home' directory. }}
===PART AINVESTIGATION 1: Setting up your SETTING UP YOUR NIS Server=SERVER ==
*Install the NIS server and client onto your VM 2.
yum install ypserv ypbind
*Log out of '''VM2''', but leave it running
===Part BINVESTIGATION 2: Client Configuration=CLIENT CONFIGURATION ==
*Log into both '''vm2''' and '''vm3''' as '''nis-user'''. Note how they require different passwords on different machines.
*Ensure ypbind will start at boot and restart the vm.
*Log into vm3 as '''nis-user'''. You should now be able to use the password stored on '''vm2'''.
*Back on '''vm2''' change the password for '''nis-user''' and rebuild the maps. Try to log into '''vm3''' as '''nis-user''' with the old password; it should now require the changed password.
===Part CINVESTIGATION 3: Adding the other VM's=ADDING THE OTHER VMS ==
*When you have successfully made this change on '''vm3''', repeat these steps so that '''vm1''' will also use NIS for user identification from files located on '''vm2'''.
**Warning: When configuring the location of the NIS server to bind to, use the ip address instead of the hostname. When the machine is booting, you have no guarantee that '''named''' starts before '''ypbind'''.
932
edits

Navigation menu