Share via


IAS Client Settings for Windows Server 2003

A wireless access point that is configured as an Internet Authentication Service (IAS) client functions as a remote network access device. The remote access device will forward all connection and authentication requests from users to the IAS server. To enable IAS-based authentication on your wireless network, you need to configure your Remote Access Service (RAS) server and the 802.1x enabled access point as IAS clients. The IAS server processes the request and either grants or rejects the connection request. If the request is granted, the client is authenticated, and unique keys, from which the WEP key is derived, can be generated for that session.

Because the RAS server and the IAS server are both located on TESTSERVER, you can create a client with the same IP address that is assigned to TESTSERVER.

For information about how to create IAS clients, open Internet Authentication Service from AdministrativeTools, and from the Help menu choose Help Topics. In the Internet Authentication Service Help, search for "Add RADIUS clients."

Create the following RADIUS clients.

Friendly name IP address
TESTSERVER 10.11.0.1
CE8021X 10.11.0.11
CEWPA 10.11.0.12

When you create your IAS clients, make the following choices:

  • In the console tree, right-click RADIUS Clients, and then choose New RADIUS Client. In the New RADIUS Client dialog box, type the friendly name for the client.
  • In the Client address (IP or DNS) field, type the IP address for the client.
  • Type a shared secret, and confirm the shared secret. You will be asked to provide the shared secret for each access point when you configure your wireless access points.
  • Verify that the Request must contain the Message Authenticator attribute checkbox is cleared.
  • To verify that you have configured each IAS client correctly, double-click the RADIUS Clients node in the console tree to view a list of your IAS clients.

See Also

How to Set Up a Wireless Network with a Security Infrastructure

Last updated on Wednesday, April 13, 2005

© 2005 Microsoft Corporation. All rights reserved.