T61 wireless works unsecured but not with network key

[wardwill]

I have a new Thinkpad T61 that will properly connect to my wireless network when the router is configured as unsecured but CANNOT connect when I set up a network key.

In my router config I have tried using both the WPA-PSK and WPA2-PSK authentications. I enter a 9 character network key made up of ordinary numbers that is accepted by the router, and save settings. The other settings on the screen are:
WPA Group Rekey Interval = 0
WPA Encryption = AES
WEP Encryption = Disabled

In the Windows wireless interface I select the network, type in the key, and get to the “acquiring network address” stage but no further. The connection window shows that packets are being sent and received. As soon as I go back to my router config and set it as unsecured, the wireless connects no problem. I have tested another laptop on the network with a passkey and it connected without problem.

Occasionally when I am tinkering with the wireless settings (especially after clicking on the wireless tray icon) the system locks and I have to reboot. Before the reboot I get a program “not responding” dialog box where it asks me to end explorer.exe and a program called CiceroUIWndFrame.exe

The system came pre-loaded with Linux but I’ve changed to XP Pro. I have done all Windows updates, through SP3. I am using Windows to configure wireless, but thinkvantage ver. 4.52 is also running. I tried disabling Windows networking and configuring through thinkvantage, but this fails also. Then I tried uninstalling access connections altogether.

Also tried reloading the drivers, both downloading the wireless driver again and reinstalling that, and also reinstalling the original drivers I found on my C drive. These didnt work. I sense that its still a driver problem, but not sure what to try now

Any ideas??

Cheers,
Will

PS apologies for first posting this in the wrong section.

[SHoTTa35]

your router i'm guessing always worked with WPA and other computers? The T61 should connect easily too but if it's stuck at the aquiring ip part then it suggests to me something is wrong with the router.

When you change to WPA, unplug it for 30 seconds then put it back and then try to make the T61 connect. The DHCP in the router might be a bit screwy. You could also give yourself a static IP and see if that works with WPA enabled. If so then you know it's the router causing problems when working in WPA mode.

You said you tried WPA2 but what about WPA-TKIP instead of AES?

[basketb]

I had once a similar problem with my T60p. The router was set to wireless-g only (no b access) and I couldn't connect securely. When set to allow b and g traffic, it worked. (btw: a concurrently connected R52 didn't have this problem )

[pjk]

If the connection process gets to "acquiring IP", then the client (Thinkpad) has already finished the authentication/encryption/association/handshake part.

Many routers will not offer a WPA2-TKIP option. Many (particularly older) models do not offer a WPA-AES option. Both of those combinations are "optional" in the respective standards.

I've had issues with Access Connections in DHCP, particularly when changing from a previous connection that uses a static IP. That could be one vector.

[Tim M]

I've experienced this issue on a T42 after installing SP3, even with up-to-date drivers and AC removed. I think this may be a SP3 issue. I haven't found a resolution and will probably go back to SP2 permanently.