Connection Request Processing
Applies To: Windows Server 2008
Connection request processing
You can use connection request processing to specify where the authentication of connection requests is performed. If you want the local server running Network Policy Server (NPS) to perform authentication for connection requests, you can use the default policy without additional configuration. Based on the default policy, NPS authenticates users and computers that have an account in the local domain and in trusted domains.
If you want to forward connection requests to a remote NPS or other RADIUS server, create a Remote RADIUS Server Group and then configure a connection request policy that forwards requests to that Remote RADIUS Server Group. With this configuration, NPS can forward authentication requests to any RADIUS server, and users with accounts in untrusted domains can be authenticated.
The following illustration shows the path of an Access-Request message from a network access server to a RADIUS proxy, and then on to a RADIUS server in a remote RADIUS server group. On the RADIUS proxy, the network access server is configured as a RADIUS client; and on each RADIUS server, the RADIUS proxy is configured as a RADIUS client.
|The network access servers that you use with NPS can be gateway devices that are compliant with the RADIUS protocol, such as 802.1X wireless access points and authenticating switches, servers running Routing and Remote Access that are configured as VPN or dial-up servers, Terminal Services Gateway (TS°Gateway) servers, and other devices.|
If you want NPS to process some authentication requests locally while forwarding other requests to a remote RADIUS server group, configure more than one connection request policy.
To configure a connection request policy that specifies which NPS or RADIUS server group processes authentication requests, start with Connection Request Policies.
To specify NPS or other RADIUS servers to which authentication requests are forwarded, start with Remote RADIUS Server Groups.