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.
When she got it home she said she was getting this error message that her wireless wasn't working. I took it back to my house and it didn't have any problems connecting to the wireless router. OS- Windows XP SP3 Laptop- Compaq Presario V6000 Wireless Router- Netgear N 150 WNR1000v2 Cable Modem- Arris TM502G Browser IE 8 Thanks. Once the router settles, open another browser window and see if she can surf. If yes unplug the Ethernet from the laptop and try to connect wireless.
The wireless connection of this system works fine, but when connected via the LAN connector, you will see that little connection animation (which you see when you get a DHCP address assigned as well)but only now it tells "Validating Identity" The connection works so their is no real problem, it's just very annoying. Product: DIR-655 - HW Version: A2 - FW Version: 1.33NAb01Product: DAP-1522 - HW Version: A1 FW: 1.20Product: DWA-643 - HW Version: A1 - FW Version: 2.0Product: DWA-160 - HW Version: A1 - FW Version: 1.20 EProduct: DCS-1130 - HW Version: A1 - FW Version: 1.01hmmm..question....
I have 3 routers ( Linksys wrt300n - Netgear wnr854t - D-link DIR-655 ) no SMC....I just tried to connect to them all, one at a time, with my Lenovo T60 laptop..I cant get the animation ( not in Win XP nor Win Vista - running dualboot)In the windows versions it is possible to disable the animation function..Vista just rightclick on the animation an disable XP go to settings and network connections and rightclik on your LAN connection and choose propertiesand remove the "Show icon in notificationarea when connected"Product: DIR-655 - HW Version: A2 - FW Version: 1.33NAb01Product: DAP-1522 - HW Version: A1 FW: 1.20Product: DWA-643 - HW Version: A1 - FW Version: 2.0Product: DWA-160 - HW Version: A1 - FW Version: 1.20 EProduct: DCS-1130 - HW Version: A1 - FW Version: 1.01That's good for getting rid of the symptom, but doesn't solve the cause I want to know why i get this message when using the dir-655 and not when using another router.
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.
It does a 4 packet handshake to connect/authenticate and then that's it. Now you can break WPA/WPA2 as well if you capture the handshake packets.
I moved the selection tab to WPA2 only and keep the rest the same and no luck. Ok so I setup the router to only transmit wireless N and to use WPA2 only.Hi all, I just signed up (for my elderly mom) with Comcast for their hi-speed Internet service (performance level).Self-install kit included the ARRIS model TG 862G/CT Wi-Fi tower modem.When I try to connect using the windows zero configuration utility it gets stuck validating identity.It says something about windows not finding a certificate. This can be entered as 5 or 13 as I characters or 10 or 26 hexadecimal characters. When I enter the router password, the following message appears: the network password needs to be 40bits or 104bits depending on your configuration.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.This will reinstall the known good drivers and will recreate her wireless connection, try again to connect wireless. A word about WEP vs WPA/WPA2: Mainly it comes down to when/how you are authenticated. You get enough of them, use a program and it can put all the bits together to figure it out.WPA/WPA2 only authenticates when you first connect.