How this book is organized

Use the network, to log into other machines, share files, and transfer files across the network.

Administer TCP/IP, including configuring subnets, adding pseudo ttys, configuring anonymous ftp, enabling UUCP over TCP/IP, configuring user equivalence, and troubleshooting the stack.

Manage and troubleshoot the IPX/SPX protocol stack to provide networking services to other systems, including Novell servers, running the IPX/SPX protocol stack.

Configure gateway and routing protocols on your system, and configure the operation of the gated, irdd, and routed routing daemons.

Create and maintain a distributed database of system names, IP addresses, and other information with the Domain Name Service (DNS). Topics covered include server and client configuration, troubleshooting, and administration.

Manage user and system data across the network, with the Network Information Service (NIS). Topics covered include creating and maintaining NIS maps, creating and administering NIS servers and domains, and troubleshooting NIS.

Manage TCP/IP networks and network devices with the Simple Network Management Protocol (SNMP) Topics covered include configuration, the Management Information Base, SMUX peers, and using SNMP to monitor and correct network problems.

Configure TCP/IP to operate over serial lines via either the Point to Point Protocol (PPP) or the Serial Line Interface Protocol (SLIP). Topics covered include authentication, negotiation, gateways, interoperability, and troubleshooting.

Verify connectivity between sites via the TCP/IP or IPX/SPX protocol stacks with the Node Check Manager. Topics covered include adding and deleting sites from the ping list, altering the interval time, and configuring actions and alerts taken when a node is down.

Sharing files over the network with the Network File System. Topics covered include mounting, exporting, and enabling NFS® filesystems, NFS troubleshooting, and using the Filesystem Manager.

Modifying the filesharing capabilities of NFS to mount on an as-needed basis (automount). Topics covered include configuring, administering, and troubleshooting automount configurations.

Enable remote printing for your users with the remote printing capabilities of TCP/IP. Topics covered include setting up print clients and servers, adding and deleting printers and clients, and interoperating with other releases of lpd.

Create a networked Calendar database server or client. Topics covered include creating and merging calendar databases, setting up calendar servers and clients, and troubleshooting.

Synchronize clocks on a local network or on the Internet by using the Network Time Protocol (NTP), or by using the Time Synchronization Protocol (TSP), which enables you to synchronize clocks across multiple networks. Topics covered include creating clients and servers, testing and tuning your time server, and troubleshooting.

Distribute updated files to a number of sites on your network with the TCP/IP rdist command. Topics covered include writing distribution files and notifying users of new software.

Install or upgrade software components or the entire operating system across the network. Topics covered include installing products onto or from a remote machine, removing and examining software on a remote machine, initiating an operating system on a client that loads the software from a remote server, and understanding the new software storage object (SSO) product structure.

Create a networked documentation server or client. Topics covered include serving online help to other machines, receiving online help from a help server, and creating homepages.

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