Validating identity on wireless connection

Rated 3.97/5 based on 763 customer reviews

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.

Yesterday I reformatted a friends computer and reinstalled the OS and other software at my house. I brought her laptop and router to my house and it works fine. I tried to install the disc that came with the router, but it said something like the IP address wasn't static and I needed to imput the blah blah blah. Whatever PC was used when they installed Comcast needs to be connected to the router and the MAC address cloned to the router. It will be slightly inside the router housing so she'll need a paperclip to push it. She can then boot her laptop while the router does what its doing. Dot beside No for "Require a logon" and then all the way at the bottom, put the dot beside "Use Computer MAC Address" click Apply.

Everything was working fine when she picked it up, specifically the wireless. I did a search for this and maybe one of the fixes will work. Here is the manual for her router so if you are doing this over the phone you can see what she is seeing. Unplug the power to the router then plug it back in.

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. During the connection it flashes that it "connected" for a second then goes to "Validating Identity" which it eventually timesout on.

FYI- her router (Netgear) login was "routerlogin.net". I did what you said, and change the address to the computer address.

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 suspect a firmware upgrade probably fixes that behaviour.

You could break into a router the way you described.

But you'd have to know their ISP IP address, not the 192 etc address. I then changed it back to the Default Gateway, reset the Cable Modem, and hit the test button.

Leave a Reply