Use this procedure to configure a Protected Extensible Authentication Protocol-Microsoft Challenge Handshake Authentication Protocol version 2 (PEAP-MS-CHAP v2) wireless configuration profile for wireless computers running Windows XP and Windows Server 2003.

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

To configure a PEAP-MS-CHAP v2 wireless profile for computers running Windows XP
  1. Open Windows XP Wireless Network (IEEE 802.11) Policies Properties dialog box.

    On the General tab, do the following:

    1. In XP Policy Name, type a name for your wireless policy.

    2. In Description, type a description of the policy.

    3. In Networks to access, select either Any available network (access point preferred) or Access point (infrastructure) networks only.

    4. Select Use Windows WLAN AutoConfig service for clients.

  2. On the Preferred Networks tab, click Add, and then select Infrastructure. On the Network Properties tab, configure the following:

    1. In Network Name (SSID), type the service set identifier (SSID) for your network.


      The value you enter in this field must match the value configured on the access points you have deployed on your network.

    2. In Description, enter a description for the New Preferred Setting Properties.

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

      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.

    4. In Select the security methods for this network, in Authentication, select either WPA2 (preferred), or WPA. In Encryption, specify either AES or TKIP.


      In Windows XP Wireless Network (IEEE 802.11) Policies, WPA2 and WPA correspond to the Windows Vista Wireless Network (IEEE 802.11) Policies WPA2-Enterprise and WPA-Enterprise settings, respectively. WPA-PSK and WPA2-PSK are for networks that do not use 802.1X authentication. Do not use them for 802.1X authenticated wireless access deployments.


      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.

  3. Click the IEEE 802.1X tab. In EAP type, by default, Protected EAP (PEAP) is selected.

    The remaining default settings on the IEEE 802.1X tab are sufficient for most wireless deployments.

  4. Click Settings. In the Protected EAP Properties dialog box, do the following:

    1. Select Validate server certificate.

    2. 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.

    3. 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).


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

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

    5. In Select Authentication Method, select Secured Password (EAP-MSCHAP v2).

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

    7. 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.

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

    9. 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.

  5. Click OK to save the Protected EAP Properties settings, and then click OK again to save the policy.