Wireless Enables at Startup (Access Connections Issue?)

[cb474]

I upgraded from Access Connections 4.12 to 4.21, the other day. Since then, the wireless radio will enable at startup and Access Connections will attempt to connect to whatever the last access point was that I was connected to (even if I've change locales and that access point is no longer available).

This didn't used to happen, even if I left the wireless radio switch on.

I've disabled automatic location switching. I've unchecked "enable automatic lan radio control," in global settings, and unchecked "allow wireless connection at windows logon." I've even disabled the Windows "Wireless Zero Configuration" service.

So I'm stumped. Why is this happening? I find it annoying, it slows startup and it wastes the battery.

It used to be that the radio would remain off, until I opened Access Connections and tried to connect to an access point, at which point I'd get a pop up asking me if I want to enable the wireless radio. That's how I'd like it to be.

[agarza]

Uninstall Thinkvantage Access Connections: To me it is redundant to have a software that messes up with the original Windows Wireless utility, more easy to use and no conflicts with other software

[pinesol]

........
I've disabled automatic location switching. I've unchecked "enable automatic lan radio control," in global settings, and unchecked "allow wireless connection at windows logon." I've even disabled the Windows "Wireless Zero Configuration" service.
.........

Did you also uncheck 'Allow wireless connection at Windows logon'?

[cb474]

Yes, I've also unchecked "allow wireless connection at windows logon."

[claudeo]

Re-enable automatic location switching. With automatic location switching, if AC doesn't find the old location it will look for another known connection and then if it doesn't find one it will simply give up.

Another thought: If your machine is configured to log in to a domain, the Windows login itself can be set up to try to get a connection, using every network adapter in the machine including the wireless, in order to authenticate you with the domain. If you are connected to a domain, get the network administrator to turn this off -- it might be set by a group policy over which you have no control. [/b]