Export (0) Print
Expand All
6 out of 18 rated this helpful - Rate this topic

Configure Wireless Clients running Windows 7 and Windows Vista for PEAP-TLS Authentication

Updated: March 29, 2012

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

Use this procedure to configure a Protected Extensible Authentication Protocol–Transport Layer Security (TLS) profile for authentication using smart cards or other certificates.

Membership in Domain Admins , or equivalent, is the minimum required to complete this procedure.

To configure a PEAP-TLS wireless profile for computers running Windows 7 and Windows Vista

  1. Open the New Wireless Network (IEEE 802.11) Policies Properties dialog box.

  2. On the General tab, in Policy Name , type a new name for your policy, or leave the default.

  3. In Description , type a description of your policy.

  4. Select Use Windows to configure wireless network settings for clients to specify that WLAN AutoConfig is used to configure wireless network adapter settings.

  5. On the General tab, do one of the following:

    • To add and configure a new profile, click Add , and then select Infrastructure .

    • To edit an existing profile, select the profile you want to modify, and then click Edit .

  6. On the Connection tab, in Profile Name , if you are adding a new profile, type a name for the profile. If you are editing a profile that is already added, use the existing profile name, or modify the name as needed.

  7. In Network Name(s) (SSID) , type the service set identifier (SSID) for your wireless APs, and then click Add .

    If your deployment uses multiple SSIDs and each wireless AP uses the same wireless security settings, repeat this step to add the SSID for each wireless AP to which you want this profile to apply.

    If your deployment uses multiple SSIDs and the security settings for each SSID do not match, configure a separate profile for each group of SSIDs that use the same security settings. For example, if you have one group of wireless APs configured to use WPA2-Enterprise and AES, and another group of wireless APs to use WPA-Enterprise and TKIP, configure a profile for each group of wireless APs.

  8. To specify that wireless clients automatically connect to wireless APs for which the SSID is specified in Network Name(s) (SSID) , select Connect automatically when this network is in range .

  9. To specify that wireless clients connect to networks in order of preference, select Connect to a more preferred network if available .

  10. If you deployed wireless access points that are configured to suppress the broadcast beacon, select Connect even if the network is not broadcasting .

    security Security Note
    Enabling this option can create a security risk because wireless clients will probe for and attempt connections to any wireless network. By default, this setting is not enabled.

  11. Click the Security tab. In Select the security methods for this network , in Authentication , select WPA2-Enterprise if it is supported by your wireless AP and wireless client network adapters. Otherwise, select WPA-Enterprise .

    noteNote
    Selecting WPA2 exposes settings for Fast Roaming that are not displayed if WPA is selected. The default settings for Fast Roaming are sufficient for most wireless deployments.

  12. In Encryption , select AES , if it is supported by your wireless AP and wireless client network adapters. Otherwise, select TKIP .

    noteNote
    The settings for both Authentication and Encryption must match the settings configured on your wireless AP.

  13. In Select a network authentication method , select Microsoft: Protected EAP (PEAP) .

  14. In Authentication mode , select from the following, depending on your needs: User or Computer authentication , Computer authentication , User authentication , Guest authentication . By default, User or Computer authentication is selected.

  15. In Max Authentication Failures , specify the maximum number of failed attempts allowed before the user is notified that authentication has failed. By default, this value is set to “1.”

  16. To specify that user credentials are held in cache, select Cache user information for subsequent connections to this network .

  17. Click Advanced , and then configure the following:

    1. To configure advanced 802.1X settings, in IEEE 802.1X , select Enforce advanced 802.1X settings , and then configure the following settings, depending on your needs: Max Eapol-Start Msgs , Held Period , Start Period , and Auth Period .

      When the advanced 802.1X settings are enforced, the default values are sufficient for most wireless deployments.

    2. To enable Single Sign On, select Enable Single Sign On for this network .

    3. To specify when Single Sign On occurs, select either Perform immediately before User Logon or Perform immediately after User Logon , depending on your needs.

      The remaining default values in Single Sign On are sufficient for typical wireless deployments.

    4. To specify the maximum amount of time, in seconds, in which 802.1X authentication must complete and authorize network access, in Max delay for connectivity (seconds) , enter a value, depending on your needs.

    5. To allow dialogs during Single Sing On, select Allow additional dialogs to be displayed during Single Sign On .

    6. To specify that wireless computers are placed on one virtual local area network (VLAN) at startup, and then transitioned to a different network after the user logs on to the computer, select This network uses different VLAN for authentication with machine and user credentials .

    7. To enable Fast Roaming, in Fast Roaming , select Enable Pairwise Master Key (PMK) Caching . The default values for PMK Time to Live (minutes) and Number of entries in PMK Cache are typically sufficient for Fast Roaming.

    8. Select This network uses pre-authentication , if your wireless AP is configured for pre-authentication. The default value of 3 is typically sufficient for Maximum Pre-authentication attempts .

    9. To specify that cryptography adheres to the FIPS 140-2 certified mode, select Perform cryptography in FIPS 140-2 certified mode .

  18. Click OK to save your settings and return to the Security tab.

  19. Click Properties . The Protected EAP Properties dialog box opens.

  20. In Protected EAP Properties , verify that Validate server certificate is selected.

  21. In Trusted Root Certification Authorities , select the trusted root certification authority (CA) that issued the server certificate to your server running Network Policy Server (NPS).

    noteNote
    This setting limits the trusted root CAs that clients trust to the selected CAs. If no trusted root CAs are selected, then clients trust all root CAs listed in their trusted root certification authority store.

  22. To specify which Remote Authentication Dial-In User Service (RADIUS) servers your wired access clients must use for authentication and authorization, in Connect to these servers , type then name of each RADIUS server, exactly as it appears in the subject field of the server certificate. Use semicolons to specify multiple RADIUS server names.

  23. For improved security and a better user experience, select Do not prompt user to authorize new servers or trusted certification authorities .

  24. In Select Authentication Method , select Smart Card or other certificate .

  25. To enable PEAP Fast Reconnect, select Enable Fast Reconnect .

  26. To specify that Network Access Protection (NAP) performs system health checks on clients to ensure they meet health requirements, before connections to the network are permitted, select Enforce Network Access Protection .

  27. To require cryptobinding Type-Length-Value (TLV), select Disconnect if server does not present cryptobinding TLV .

  28. To configure your clients so that they will not send their identity in plaintext before the client has authenticated the RADIUS server, select Enable Identity Privacy , and then in Anonymous Identity , type a name or value, or leave the field empty.

    For example, if Enable Identity Privacy is enabled and you use “guest” as the anonymous identity value, the identity response for a user with identity alice@realm is guest@realm. If you select Enable Identity Privacy but do not provide an anonymous identity value, the identity response is @realm.

  29. Click Configure . In the Smart Card or other Certificate Properties dialog box, in When connecting , select either Use my smart card or select both Use a certificate on this computer and Use simple certificate selection (Recommended) .

  30. To require that access clients validate the NPS server certificate, select Validate server certificate .

  31. To specify which RADIUS servers your wired access clients must use for authentication and authorization, in Connect to these servers , type then name of each RADIUS server, exactly as it appears in the subject field of the server’s certificate. Use semicolons to specify multiple RADIUUS server names.

  32. In Trusted Root Certification Authorities , select the CA that issued certificates to your NPS servers.

  33. To specify that clients use an alternate name for the access attempt, select Use a different user name for the connection .

  34. To prevent users from being prompted to trust a server certificate if that certificate is incorrectly configured, is not already trusted, or both, select Do not prompt user to authorize new servers or trusted certification authorities . (Recommended)

  35. Click OK to close the Smart card or other Certificate Properties dialog box, and then click OK again to close the Protected EAP (PEAP) Properties dialog box, returning you to New Wireless Network Policy Properties .

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft. All rights reserved.