SP2, Access Connections 3.71, Wireless

[ThinkpadEsq]

Just installed SP2 and upgraded to AC3.71.

When I reboot, AC don't give me an IP. It 169.x's and shows that there is a "WEP key error." The only way I can get this fixed is by going into the Network card properties and checking the 'let windows configure my wireless settings' box. Any advice so I don't have to do this annoying work-around every time I reboot?

Thanks!

[jdhurst]

This should all work and it does for me. I suggest completely uninstalling Access Connections, uninstalling the wireless NIC (make sure you have the current driver first - AC needs that), then reboot, install the wireless NIC and then AC after that. See if this works for you. ... JD Hurst

[ThinkpadEsq]

This should all work and it does for me. I suggest completely uninstalling Access Connections, uninstalling the wireless NIC (make sure you have the current driver first - AC needs that), then reboot, install the wireless NIC and then AC after that. See if this works for you. ... JD Hurst

I tried your fix and the problem still exists. Any other tips/diagnostics?

[cytexone]

How about creating a new profile and deleting the old one? I had a problem once where my WPA key somehow "got corrupted" and re-typing in the password connected me successfully to the device.

Diag-blurb... If you're able to connect to the device via windows standard wireless config, there is no problem with the networking components on your machine. It's a problem with AC. Additionally, if you're WEP key is incorrect, you won't be able to associate with the AP and you won't get a valid IP (hence the 169.x.x.x).

Deleting your previous profile and re-creating a new one (with the correct WEP key, of course) should fix this problem.

HTH,
Andy
CYTEXONE