Wireless connection says validating identity
He's running xp pro sp3 and as far as i know its an authentic copy.
Any help would be great Thanks jeremy Edited by jeremy_smitty5, 10 January 2009 - PM.
Everything came pre-loaded on the laptop so Im not sure why the Authentication tab wasnt there.
Or perhaps it was a wireless laptop and there is no need for that tab.
Do you have the same security setting, router name, and IP address on the router?
The computers have to match the new setting with the router. HOw do I reset the settings of the computers to match the new router? IEEE 802.1X is the standard which defines authentication against a RADIUS server.
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.
Under my Local Area Connection Properties and on the Authentication tab Enable IEEE 802.1x authentication for this network was checked.
That is the reason all the sudden "validating identity" show up on the computers.
Just copy the DIR-655 router name, security password..to the computers wireless adapter should fix the in to the router with the computer that can, you know 192.168.0.1, go to advanced/network filter, check that MAC filtering is disabled, the go to WIFI protected setup, check that it is disabled, usually the DIR-655 has at least one of them enabled by default Ummm, my wireless laptop never had problem with validating identity only 2 wired computers are should validating identity.
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.I suspect a firmware upgrade probably fixes that behaviour. If you want to accept both computer credentials and user credentials you'll need to name both "Domain Comptuers" and "Domain Users" in your policy.