MCSE Boot Camp Notes :

Networking Guide
Chapter 7, Configuring the Network Information Service (NIS)

Initializing a copy-only server

Initializing a copy-only server

The following steps explain how to initialize a copy-only NIS server.

  1. Log in as root and enter the following command to shut down the system:

    /etc/shutdown -g0 -y

    You see messages as the system services stop. Press <Enter> at the Safe to Power Off message.

  2. The following prompt appears:
       Type <Ctrl>D to proceed with normal startup,
       (or give root password for system maintenance)
    

  3. Type the root password, then press <Enter>.

  4. Enter either of the following commands at your operating system prompt:
    
    mkdev nis

    or

    /etc/yp/ypinit

    The functionality and the options for ypinit and mkdev nis are identical.

  5. NIS prompts you to choose the host type:
       You must specify whether this host is to be a master, slave server,
       copy-only server or NIS client. Please enter the server type:[mscCq]
    

    Enter c to indicate that you are setting up a copy-only server. If you want to stop the initialization, enter q.

  6. If you are initializing a copy-only server in Secure Mode, you see:
       Due to the restrictions of running NIS under the current security
       setting of this system, this server will accept, but not integrate
       sensitive maps received through NIS. Please refer to your Release
       and Installation Notes for further details.
    

    Hit return to continue.

  7. If NIS has been previously initialized on your system, you see the following:
       NIS has been initialized previously on this machine
       Please verify that you would like to re-initialize NIS
       Do you wish to re-initialize NIS? (y/n/q)
    
    Enter y to continue.

  8. You then see:
       The local host's domain name hasn't been set. Please set it.
       Please enter the domain name or q to quit:
    
    Enter the NIS domain name; you need an NIS domain name to retrieve data from an NIS database.

    You will be asked:

       Is "domainname" correct? [y/n/q]
    
    Enter y if correct. If you enter n, you will be asked to reenter the domain name. If you enter q, NIS initialization aborts.

  9. NIS prompts you to enter a host name. You see:
       You must specify a host name to act as the NIS master
       during map transfer [q to quit]:
    
    Enter the name of a master server with an up-to-date and stable database.

    You see this prompt:

       Installing the NIS database will require that you answer
       a few questions.  Questions will all be asked at the beginning
       of the procedure.
    

  10. If an NIS database already exists on your machine, you see:
       Can we destroy the existing /etc/yp/<domainname> and its contents?
       [y/n/q: n]
    
    If you see this message, enter y to continue, which tells NIS to rebuild the previous NIS database with current information.

    If you enter the default n or q, NIS initialization aborts, and you must manually remove the old NIS databases.

  11. (Skip this step if you are initializing a copy-only server in Secure Mode.)

    If the /etc/passwd.local file does not exist on the machine, you see the following message:

       NIS stores local logins in /etc/passwd.local, which currently
       doesn't exist on this machine. The /etc/passwd.local file must be
       created before continuing.
    

    Is it okay to copy /etc/passwd to /etc/passwd.local? [y/n/q: n]

    Enter y to continue. See ``About managing users'' for details on these files.

    If you enter the default n, you must manually create the /etc/passwd.local file, then start the initialization procedure again.

  12. (Skip this step if you are initializing a copy-only server in Secure Mode.)

    If the /etc/group.local file does not exist on your machine, you see:

       NIS stores local groups in /etc/group.local, which currently
       doesn't exist on this machine. The /etc/group.local file must be
       created before continuing.
    

    Is it okay to copy /etc/group to /etc/group.local? [y/n/q: n]

    Enter y to continue. See ``About managing users'' for details on these files.

    If you enter the default n, you must manually create the /etc/group.local file, then start the initialization procedure again.

  13. Next, verify that the YP_MAP_X_LATE file contains correct information. You see:
       The YP_MAP_X_LATE file contains the following:
      
      
       list of mapnames
    

    Is this correct? [y/n/q: n]

    If the list is not correct, enter the default n. Edit YP_MAP_X_LATE to contain the correct entries, and start the initialization procedure again. Refer to the ypmapxlate(NF) manual page for more information.

    If the list is correct, enter y to continue.

  14. You then see:
       You must specify whether ypbind is to be run with the secure
       option (-s), the ypset option (-ypset), allowing anyone to
       change your binding, or the ypsetme option (-ypsetme) which
       only allows requests with host-name's IP address
       to change host-name's binding, or with no options.
       Please see ypserv(NADM) for more information
       1) ypbind -s
       2) ypbind -ypset
       3) ypbind -ypsetme
       4) ypbind
       Please enter your choice (1-4,q):
    
    Enter the response appropriate to your security concerns.

    Option 1
    Recommended for most heterogeneous environments, where other versions of NIS are also in use.

    Option 2
    Recommended when the server is on a different subnet, and you want others to be able to change your bindings.

    Option 3
    Recommended when the server is on a different subnet, and only requests with host-name's IP address should be able to change your bindings.

    Option 4
    Recommended in an SCO NIS environment where the server is on the same subnet.
    For further information, consult the ypserv(NADM) manual page, which includes information about ypbind. See also ypset(NADM).

  15. When the initialization procedure is complete, you see a series of messages resembling the following display when initializing a copy-only server:
       There will be no further questions.  The remainder of the
       procedure should take a few minutes to set up the NIS server.
      
      
       

    The NIS maps will be transferred from master_server when server_name goes to run level 2.

  16. If NIS has been previously initialized on your system, you see:
       The backup directory /usr/lib/nisrt already exists
    

    Do you wish to continue with the SCO NIS Runtime System Initialization?

    Enter y to continue; NIS then backs up system passwd files. If you enter n or q, NIS installation aborts.

    You then see:

       Backing up system passwd files . . .
      
      
       

    server_name's NIS data base has been set up without any errors.

    Your copy-only server is now initialized.

  17. Shut the system down and reboot it by using the System Shutdown Manager as described in the SCO OpenServer Handbook. Remember to select Reboot after shutdown when using the manager. Enter <Ctrl>D when prompted to return to multiuser mode.

    The first time an NIS slave or copy-only server enters multiuser mode, its startup script calls ypxfr to transfer maps from the master server. Subsequent system startups do not transfer maps automatically.

Networking guide
Call : 800-519- 2267

MCSE CCNA Certification boot camp
Testimonials
 Join MCSE Boot Camp & CCNA Boot Camp Back to Back Certification Today.
MCSE Boot Camp links  MCSE Boot Camp 270  MCSE Boot Camp  290  MCSE Boot Camp  291  MCSE Boot Camp 293  MCSE Boot Camp  294  MCSE Boot Camp 298  MCSE Boot Camp 299  MCSE Boot Camp Security  MCSE Boot Camp 640-801  MCSE Boot Camp routing MCSE Boot Camp 811  MCSE Boot Camp 821  MCSE Boot Camp 831  MCSE Boot Camp Resources MCSE Boot Camp MCSE + CCNA  MCSE Boot Camp Training  MCSE Boot Camp Card pay  MCSE Boot Camp Papal  MCSE Boot Camp MCSE Notes  MCSE Boot Camp CCNA Notes    MCSE Boot Camp index MCSE Boot Camp main  MCSE Boot Camp root MCSE Boot Camp link  MCSE Boot Camp resources MCSE Boot Camp home    Ref1 Ref2
Microsoft MCSE Boot Camp
MCSE Boot Camp, MCSE Certification boot camp, MCSE Training boot camps, MCSE certification  boot camp training at California and Maryland USA. Also CCNA, CCNP, CISSP, Red Hat Linux Certification notes.

Vibrant boot camp offers MCSE, CCNA, CCNP Certification back to back

Vibrant offers MCSE certification training boot camp for $5400 all inclusive, instructor led at California and Baltimore.

Vibrant Bootcamp Participants come from All Around the World. Vibrant has trained students from more than 15 countries like USA, UK, (Scotland, Ireland, Wales), Switzerland, Germany, Australia, Canada, France, Holland, Japan, Belgium, Bahrain, New Zealand, Tanzania, Turkey, Kenya and more.

Preboot Sequence, Process Accounting, Publishing Resources, Publishing Software Packages, Redeploying Software, Refreshing Group Policy at Established Intervals, Remote Assistance, Remote Desktop for Administration, Removing a Service Pack or Hotfix, Removing or Disabling Software, Requesting Assistance, Reroute Requests with Redirects, Resolving Conflicts Between Group Policy Settings, Restoring Active Directory Directory Services, Restoring Files and Folders, Roaming User Profiles, Security, Setting Up and Managing Published Printers, Setting Up and Managing Published Shared Folders, Setting Up Auditing, Shared Folder Permissions, Slipstreaming Service Packs and Hotfixes, Software Deployment, Software Installation and Maintenance Technology, Software Update Services, Support_388945a0 account credentials instead of the users credentials to perform specific administrative, System Requirements, TABLE OF CONTENTS : Installing and Deploying Windows Server 2003, Taking Ownership, Terminal Server Role, Terminal Services Components, Terminal Services,  The Boot.ini File, The Deny Permission, The File Signature Verification Utility, The Logman Utility, MCSE Boot Camp Training get MCSE join MCSE Bootcamp, The Recovery Console, The relog Utility, MCSE Boot Camp Training get MCSE join MCSE Bootcamp, The Remote Desktop Connection Utility, The Remote Desktops Snap-In, The Session Manager, The Shutdown Event Tracker, The System Monitor, The typeperf Utility, The Windows Server 2003 Boot Process, Troubleshooting NTFS Permission Problems, Troubleshooting Terminal Services, Unattended Installation, Upgrading Software, Using a Saved File to Request Assistance, Using an Audit Policy, Using an Unattended Answer File, Using Configure Your Server Wizard and Add or Remove Programs to Install IIS, Using Driver Signing, Using E-Mail to Request Assistance, Using Event Viewer to View Security Logs, Using Event Viewer, Using Group Policy, Using Remote Installation Services, Using Scripting to Manage Website Content, Using Task Manager to Monitor Performance, Using the Recovery Console, Using the System Preparation Tool, Using User Profiles, Using Windows Messenger to Request Assistance, Viewing Security Logs, Virtual Directories, Volume Mounting, Web-Based Administration, Windows Server 2003 Licensing, Windows Server 2003 network, Windows Update Catalog, Windows Update