Developer's Grapevine

A Visual Studio Express Dude


As Technology Matures, a NAP is not the Same

  • Comments 1
  • Likes

Let's get the record straight -- NAP is not the same as NAQC.  And you look at the acronym, and say, "Duh!"

Network Access Protection (NAP) platform is not the same as Network Access Quarantine Control (NAQC), which is a capability provided with Windows Server 2003 to provide additional protection only for remote access (dial-up and VPN) connections. Network Access Protection provides added protection for VPN connections, Dynamic Host Configuration Protocol (DHCP) configuration, and Internet Protocol security (IPsec)-based communication.

The differences between the NAP platform and NAQC are the following:

·         NAQC is only for remote access connections (dial-up and VPN). NAP is a platform to enforce network health compliance for a variety of network access and network communication methods. VPN Quarantine in NAP only applies to remote access VPN connections.

·         NAQC requires the creation of a script to check system health policy compliance. NAP does not require a script. Instead, you configure system health policies on the IAS server.

·         NAQC places a remote access client in quarantine while the script is determining the client's system health. A VPN NAP client's health is evaluated during the connection establishment and is only quarantined if the client is unhealthy.

For more information about NAP, see the Network Access Protection Platform Architecture white paper.  On or around July 1st, there will be an article from The Cable Guy on the subject.

For more information about NAQC, see the February 2003 The Cable Guy article.

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment