When I try to go into it jus says validating identity and doesn't bring you to the stage where it asks for the WEP key.I tried it on the neighbors network and it got to that stage so I don't think the problem is the...As long as you use the same options for both, you should be fine.
WPA2 is supported as i can connect to WPA2 personal APs. 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. 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 cannot get WPA2 enterprise to work on my network. 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.
To start off, its VERY important to check the time in AD (windows clock) and ISE (show clock command).
If time is not synched, your radius authentication will fail with a variation of funky error messages (see ISE monitor image above).
I'd start by reviewing the event logs on your IAS server for reasoning as to why it's not authenticating your client.
Ok so we just got a new wireless network for our home and it is one that needs a WEP key.
Verizon is dedicated to protecting consumers and businesses from identity theft.