Fixing Access Request Problems

Applies To: Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2

This section describes and provides solutions for access request problems that can occur in a Network Access Protection (NAP) deployment.

A NAP client computer provides identity and health information when it requests access to the network. For the NAP with 802.1X enforcement and NAP with VPN enforcement methods, identity is authenticated by using the settings configured in Network Policy Server (NPS) connection request policies. For the NAP with IPsec enforcement method, identity is authenticated by Health Registration Authority (HRA) servers. Identity is not authenticated when you use the NAP with DHCP enforcement method.

The following is a list of known problems and solutions associated with access request problems in a NAP deployment. Problems and solutions that might be inter-related are noted and linked if needed. Problems that have more than one possible root cause are noted and have more than one proposed solution. Choose the problem that best describes your situation, and then complete the procedures for the suggested fix. This list will be continuously updated as new problems and solutions are found.

• Access Request Was Denied

• Access Request Was Discarded

• Network Access for Compliant Computers Is Restricted

• NAP-Capable Computers Are Evaluated as Non-NAP-Capable

• Access Requests Are Not Logged

• Access Requests Do Not Match Any Network Policy

• Access Requests Do Not Match Any Connection Request Policy

• Workgroup Computer Fails NAP Authentication

• NAP Clients Are Not Reported as Infected

• DHCP NAP Clients Do Not Obtain an IP Address

See Also

Concepts

Fixing Health Certificate Problems
Fixing Remediation Problems
Fixing SHA Problems
Fixing NAP Client Settings Problems