How to fix validating identity wireless xp
Ok so I setup the router to only transmit wireless N and to use WPA2 only.When I try to connect using the windows zero configuration utility it gets stuck validating identity.
I then tried installing the supplied Sitecom N adapter, after some problems the network appears but I can't connect, I am told "Windows was unable to find a certificate to log you onto the network" I read several threads that led me to uncheck "Enable IEEE 802.1x authentication for this network" and I actually managed to enter the WPA2 code but this just leads to the message "This connection has limited or no connectivity" and "validating identity". I recently bought a new Linksys wireless router and after setting it up with basic WEP security, I tried to logon from my laptop and was successful! So then I tried to connect from my desktop computer that has a wireless USB adapter attached to it and I ended up getting this error message: Fabulous! I checked my settings on the wireless router to make sure I didn’t accidentally setup certificate security, but found no such thing.Also, since I was able to connect from my laptop with no problem, it led me to believe it was something wrong with my desktop.After initially setting up the Win 7 laptop, in the case of the others I was asked for the security code and the connection was duly established. I am now trying to connect a friend's laptop, it is an ageing Toshiba Satellite M70-215 and from what I have been able to gather it is running Service Pack 2 and has only 512 MB RAM. If you're familiar with wireless networks, the information in the "Summary" section is probably sufficient; if not, go to the Table of Contents below and find the section that matches your device's operating system.
If you're having trouble connecting to a wifi network, you can sometimes fix the problem by removing and re-adding that profile.
First, click on the wireless icon in your taskbar and under Related Tasks, choose Change advanced settings.
Now click on the Wireless Networks tab and select the network in the list at the bottom.
The workaround is to manually create the network profile, setting it to use WPA2-Enterprise, then use the command line to fix the profile.
Note: There have been reports of Android devices corrupting network profiles; when this happens, the device keeps trying and failing to connect to FVCCNET.
It says something about windows not finding a certificate.