Initializing a slave server

The following steps explain how to initialize a slave NIS server:

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

The following prompt appears:

   Type <Ctrl>D to proceed with normal startup,
   (or give root password for system maintenance)

Type the root password, then press <Enter>.

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.

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 s to indicate that you are setting up a slave server. If you want to stop the initialization, enter q.

If you attempt to configure a master or slave server on a host in Secure Mode (that is, at High or Improved security default), you see the following message:

ypinit: ERROR: Invalid configuration.

The security settings of this system are incompatible with the NIS configuration requested. Please refer to your Release and Installation Notes for further details. Initialization Aborted.

Refer to ``NIS interaction with security modes'' for security restrictions.

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.

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.

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.

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.

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.

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.

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.

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).

When the initialization procedure is complete, you see a series of messages resembling the following display:

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.

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 slave server is now initialized.

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.

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.

Choose an Enforcement Method

Updated: October 6, 2008

Applies To: Windows 7, Windows Server 2008, Windows Server 2008 R2, Windows Vista

To choose the right NAP enforcement method for your network, review the following sections of this guide to understand the details of how each enforcement method works and determine which method best meets your deployment goals:

You might also consider the following when choosing an enforcement method:

Infrastructure. How well does your current network support the enforcement method?
Cost. Which aspect of your NAP deployment is more important: cost or flexibility?
Complexity. Do you have the expertise to implement and maintain your deployment?
Security. How secure is the enforcement method?

Infrastructure

All NAP enforcement methods can be implemented using a minimum of one computer running Windows Server 2008 R2 or Windows Server 2008. All enforcement methods require that NPS is installed on this computer and configured to evaluate the health of NAP clients. Additional required services depend on the enforcement method. For example, IPsec, VPN, and DHCP enforcement methods require a NAP enforcement server running Windows Server 2008 R2 or Windows Server 2008. The 802.1X enforcement method requires network hardware that supports the 802.1X authentication method and is capable of controlling port characteristics using RADIUS tunnel attributes. For more information, see NAP Configuration Overview.

MCITP Boot camp USA : MCITP CCNA Boot camp UK, MCITP MCSE CCNA Boot camp Asia, MCITP CCNA MCSE Bootcamp, MCITP MCSE RHCE Training

Cost

Because support for it is built into the Windows operating system, the cost of deploying NAP is typically low, but depends on how well your existing network hardware and software support your design. If you have deployed Windows Server 2008 R2 or Windows Server 2008 on your network, then you already have some or all of the components required to deploy NAP. Some NAP enforcement methods might require an upgrade of the components of your network infrastructure. For example, deploying NAP with 802.1X enforcement can be costly if you do not already have hardware that supports 802.1X authentication. If you already have hardware that supports 802.1X, then it is likely that you can deploy NAP with 802.1X enforcement at minimal cost. If your hardware does not support NAP, in some cases adding support can be as simple as downloading and installing new firmware. To determine the costs associated with a NAP deployment, review hardware and software requirements for the enforcement methods you have chosen and determine whether server and network hardware upgrades are required. Additional costs that might also be associated with a NAP deployment include planning and design costs and the training of support personnel.

Complexity

NAP with IPsec enforcement is generally the most complex enforcement method to deploy because it requires a public key infrastructure (PKI) and IPsec policies to create logical networks. However, Windows Server 2008 R2 and Windows Server 2008 include tools for managing and monitoring IPsec that eliminates much of this complexity. The 802.1X enforcement method is next in terms of complexity, followed by VPN enforcement. DHCP enforcement is the least complex enforcement method to deploy.

Security

IPsec enforcement is a powerful method for protecting compliant computers from any others; it can be combined with server and domain isolation to ensure that after a computer has demonstrated it is compliant, it will still be restricted to communicating only with authorized hosts. IPsec provides other benefits, too. Network packets are authenticated, which reduces the risk of man-in-the-middle and replay attacks, and traffic can be encrypted with IPsec, providing a high degree of protection from eavesdropping attacks.

Like IPsec, 802.1X offers a high degree of protection. Several enhancements to 802.1X are also available that provide improved security. Until a client has demonstrated that it complies with the organization�s health requirements, its access to the network will be restricted by the network switches and wireless access points. These restrictions can be very difficult to bypass, even by a determined malicious user.

VPN enforcement is a good choice for protecting remote access to the corporate network. Clients that connect to a NAP-enabled VPN server can be granted restricted access to the network at the point of entry using IP packet filters. The health of remote client computers is evaluated when the client connects and it is monitored during the VPN session. If a client computer becomes noncompliant, then access is restricted until the computer is compliant.

DHCP enforcement restricts noncompliant computers by providing a limited IPv4 address configuration. It is the least secure NAP enforcement method. It is easily bypassed by an advanced user who has administrative privileges on the computer.

Combining NAP enforcement methods

It is possible to use more than one enforcement method simultaneously. An organization might invest additional resources into combining these enforcement technologies because they have complementary strengths and weaknesses. NAP with VPN enforcement can be used to enforce organizational compliance policies on remote clients, while NAP with IPsec enforcement can be used for local clients. 802.1X and IPsec offer a particularly robust combination because together they can restrict network connectivity at multiple layers of the network protocol stack. The following table shows which enforcement methods can be combined. Keep in mind that the complexity of your NAP deployment will increase when you combine enforcement methods.

	IPsec	802.1X	VPN	DHCP
IPsec
802.1X			X
VPN		X		X
DHCP

Microsoft Course 20413

Audience Profile

At Course Completion

Initializing a slave server

Infrastructure

Cost

Complexity

Security

Combining NAP enforcement methods