Wireless and validating identity

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. 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.

According to my friend, this prevented me from connecting to the net despite having a wi-fi connection. My problem was not actually answered by the TP-LINK technical support staff.

unless you are running into the initial problem that most older hardware had. You may need to do a firmware upgrade on your device that is connecting to the router. Firstly you can not use WPA, you can use WPA-PSK/WPA2-PSK or WEP.

I just installed a new Linksys ADSL modem/router at home.

On installation, my sons (Vista) machine connected instantly and is running like the clappers. Sly Even if this was working before (on two machines simultaneously?

WPA2 is superior as it doesn't suffer from the recently discovered flaw with WPA that allows limited cracking, though it's not a method to actually allow someone to connect. I had to surf using an unsecured network server for the past months.

It turns out that I was using a specified DNS server when I set up a static IP address for port forwarding for my u Torrent connection.

Search for wireless and validating identity:

wireless and validating identity-1

Leave a Reply

Your email address will not be published. Required fields are marked *

One thought on “wireless and validating identity”