WPA2 Enterprise – Validating Identity in WPA2 Enterprise

linksysradiuswifiwindows-ias-serverwpa2

I cannot get WPA2 enterprise to work on my network. I will give you an overview of the current setup.

Windows Domain, using IAS and its own CA

Linksys WAP200 Access Point

I setup the AP to use WPA2-Enterprise Mixed using RADIUS
I setup and registered IAS on the domain controller. I added the AP as a client with and have tried using both RADIUS Standard and Cisco as the RADIUS type.

I configured the IAS policy to grant access to Domain Computers, Authentication is set to PEAP and uses a private cert issued by our CA, the other profile settings are all default.

The client settings on the laptop match the IAS settings and the certificate is definately installed. WPA2 is supported as i can connect to WPA2 personal APs. I have tried multiple laptops.

During the connection it flashes that it "connected" for a second then goes to "Validating Identity" which it eventually timesout on. I am using the Windows Wireless Connection Manager.

Any help would be very appreciated!

Best Answer

Heh heh... I setup exactly what you're describing with that very AP earlier this week for a Customer.

  • RADIUS Standard works fine for that AP.
  • To rule out the certificate validation, uncheck the "Validate Server Certificate" setting in the PEAP properties on the client at least temporarily.
  • Be sure that IAS is starting and running. I've seen problems with IAS and the need to set "ReservedPorts" since the Kaminsky DNS update. See http://support.microsoft.com/kb/956189 for details.
  • Are you seeing the authentication requests coming in from the AP in the server's event log? If not, throw "Network Monitor" on the server (or Wireshark if you're so inclined) and sniff the traffic between the server and the AP.

On a couple of occasions I've seen that particular AP (don't know what firmware) suddenly stop attempting to authnenticate clients (it never sends any RADIUS requests) and power-cycling the AP "fixes" the issue. I suspect a firmware upgrade probably fixes that behaviour.

Related Topic