Atheros A/B/G + Win 7 = very slow to connect to network

[Badger]

* I am running the RC, build 7100 of Windows 7.

Just wondering if anyone else has experienced this with their T60 and the Atheros A/B/G wifi card with Windows 7. When I turn my computer on, it takes 4-5 minutes after the desktop is loaded for the machine to finally connect to the network (a network that is saved, used all the time, doesn't require any input to log on, etc). I'm only using the Windows wireless config, not any Thinkvantage software for connections. Once it connects, the speeds are fine and I have zero issues with the wireless. If I put the computer to standby and then wake it back up, it again takes forever to reconnect to the same network. There's just the orange asterisk over the bars in the tray, and when I click on it, it can see the network, so it knows it's there and if I click on the network's name I get the option to 'disconnect' even though it's not really connected for another couple of minutes.

I've tried the Windows Update drivers for the card as well as the Vista Atheros drivers as well as 8.0.0.197 drivers from a driver site -- all do the same thing. I swear when I first installed the RC that connecting to networks was super fast, so I'm thinking something went wrong in the course of using it over the months.

If anyone has any ideas, I would really appreciate it. I'm going to put in a new HDD in in a week or so anyway so I'll be able to install the RTM Win 7, but in the meantime I wanted to hear that other people were not having this issue because I'd hate to have the same problem all over again.

[netpenthe]

i have this same problem on my x200s

when i first installed Win 7 it was instantaneous network access (wireless or wired), not it takes about 2-3 minutes before it decides to connect

the network icon goes into "Limited Access" then "Identifying Network"

its frustrating, i don't know if i have the same network device as you, but its the same problem

[netpenthe]

VPN

i noticed i have a lot of VPN devices (isatap when you run 'ipconfig') maybe this has something to do with it?