User's Manual

Step 1 of 2: PEAP User
PEAP relies on Transport Layer Security (TLS) to allow unencrypted authentication types (for
example, EAP-Generic Token Card (GTC) and One-Time Password (OTP) support).
1. Authentication Protocol: Select either
GTC, MS-CHAP-V2 (Default), or TLS. Refer
to
Authentication Protocols.
2. User Credentials: Select one of the following:
■ Use Windows Logon: Allows the 802.1x credentials to match your
Windows user name and password. Before connection, you are prompted
for your Windows logon credentials.
■ Prompt each time I connect: Prompts for user name and password
every time you log onto the network.
■ Use the following: The user name and password are securely
(encrypted) saved in the profile.
■ User Name: This user name must match the user name that is set
in the authentication server.
■ Domain: Name of the domain on the authentication server. The
server name identifies a domain or one of its subdomains (for
example, zeelans.com, where the server is blueberry.zeelans.com).
NOTE: Contact your administrator to obtain the domain name.
■ Password: This password must match the password that is set in
the authentication server. The entered password characters display
as asterisks.
■ Confirm Password: Reenter the user password.
■ Roaming Identity: If the Roaming Identity is cleared,
%domain%\%username% is the default.
When 802.1x MS RADIUS is used as an authentication server, the
authentication server authenticates the device with the Roaming Identity
user name from the Intel PROSet/Wireless utility and ignores the
Authentication Protocol MS-CHAP-V2 user name. This feature is the 802.1x
identity supplied to the authenticator. Microsoft IAS RADIUS accepts only a
valid user name (dotNet user) for EAP clients. Enter a valid user name
whenever 802.1x MS RADIUS is used. For all other servers, this is optional,
therefore, it is recommended that you no use a true identity, but instead the
desired realm (for example, anonymous@myrealm).
Configure Roaming Identity to support multiple users:
If you use a
Pre-Logon or Common connection profile that requires the roaming
identity to be based on the Windows logon credentials, the creator of the
profile can add a roaming identity that uses %username% and %domain%.
The roaming identity is parsed and the appropriate log on information is
substituted for the keywords. This allows maximum flexibility in configuring
the roaming identity while allowing multiple users to share the profile.
Please refer to your authentication server user guide for directions about how
to format a suitable roaming identity. Possible formats are: