How to configure NAP services for Windows Server 2008

Published in February 08, Windows Server 2008 is part of the Microsoft Network Access Protection (NAP) program, which has Microsoft's long-awaited proprietary network access control architecture. This article explains what NAP needs to be configured during the installation process. However, given the many features and capabilities of Microsoft's Forefront software or third-party nap-related add-ons, we are only explaining a simple configuration and some NAP functionality.

We first open Network Policy server and then configure NAP in the dropdown box:

Note that it supports a variety of different network connection methods, including dhcp,802.1x and VPNs. You can select any of the connection methods that can cause the endpoint to connect to the protected network and give the selection a name. Help files are provided at the bottom of the configuration interface that illustrate some of the requirements during the installation process. Unlike general Help files, they describe not only the elements that are needed in the network infrastructure, but also which elements are not supported by the system.

For example, Wired 802.1X enables the wizard to establish a connection request policy and a health configuration NAP network system.

802.1X NAP enforcement for use

Port-based network access control 802.1x The deployment of a NAP enforcement client is based on running on both the Network Policy server (NPS) and the EAP enforcement primary client components. Using a 802.1x-based NAP enforcement client, the NPS server can instruct a 802.1X authentication switch and a 802.1X-compliant wireless access point to adjust clients that do not conform to the 802.1X network. The NPS server can restrict network access for clients by using IP filters and virtual LAN connection identifiers. The 802.1X enforcement client provides powerful network access restrictions for all computers accessing the network by accessing 802.1x servers.