To achieve load balancing for remote access connection attempts by using NPS, you must deploy multiple NPS computers. Configure connection request policies on some of these NPS computers such that remote RADIUS servers are used to perform authen- tication for remote connection attempts. This creates a deployment scenario based on RADIUS servers and RADIUS proxies.

You can create a number of RADIUS client templates and use these on the RADIUS proxies when adding a RADIUS client.

You use IP Filters templates in NPS to define the characteristics of network traffic in terms of protocol and port, and whether that traffic is allowed or blocked. After you define these templates, you can use them in network policies to control the type of traffic permitted by selecting the appropriate IP Filters template on the Configure Set- tings page in the New Policy Wizard.

172.16.24.0/21 uses 21 bits for the subnet mask. This means that the mask, expressed in decimal, is 255.255.248.0. Consequently, the first subnet ID is 172.16.8.0, the next is 172.16.16.0, the third is 172.16.24.0, and the fourth is 172.16.32.0. The first host in a subnet is 1 binary digit higher than the subnet ID. Therefore, the first host in 172.16.24.0/21 is 172.16.24.1/21.

The last host in any subnet is 2 binary digits lower than the next subnet ID. The next subnet ID in this instance is 172.16.32.0. Therefore, the last host in subnet 172.16.24.0/21 is 172.16.31.254/21.