Laptops dropping wireless connection at log on

[Dragon]

I have laptops that can log on the wlan but on loading the user profile it drops the connection for a split second and then reconnects. This appears to happen on several different laptops some with built in wireless, some with out. Any ideas how to keep the connection?

[Michael]

Well logic says there's an issue with the Access Points you're using. I would check there's no problem here.

[SYNACK]

How are your laptops authenticated on the wireless network, if it is set up through radius and is using user level certificates and machine level certs to authenticate the machine it could be just reconnecting with the different credentials at logon.

[Dragon]

No authentication used. We only have a handful.

Happens on different access points, and different laptops.

I notice I get the same at home with a machine that is on wireless. It is like the service is stopping and restarting at logon.

Apart from that, the wlan is fine.

[Geoff]

Do you use windows to manage the wireless or the manufacturers tool?

[tmcd35]

Intel wireless? If so you may want to make sure you have 100% latest drivers. We've had similar issues here and it turned out to be old drivers.

[spc-rocket]

Intel wireless? If so you may want to make sure you have 100% latest drivers. We've had similar issues here and it turned out to be old drivers.

Yes i second this, updating drivers is a must for wireless cards as they are constably tweaked to improve stability and performance.

If you have the intel 2200BG cards then do upgrade the drivers as the latest drivers for these are more stable.

Ash.

[Michael]

Where ever possible, allow Windows to manage wireless networks. It works, it's reliable and it's one less service running in the background using third party solutions.

[mullet_man]

Also try set IPs, we find it much more reilable than DHCP.

[Roopert]

I read somewhere that the microsoft wireless software will drop connections if a stronger one is located, causing similair issues to what you describe. The solution was to use the third party software to manage the wireless.

Otherwise use the wired wireless solution

[Geoff]

That's correct. Microsofts Wireless Zero Config service will periodically drop the connection to look for a stronger signal. The solution to this is as you've said, not use it. Alternatively you can stop the service once you are associated with an AP to avoid it. Doing this in a login script works.

[Michael]

I read somewhere that the microsoft wireless software will drop connections if a stronger one is located, causing similair issues to what you describe. The solution was to use the third party software to manage the wireless.

That's correct. Microsofts Wireless Zero Config service will periodically drop the connection to look for a stronger signal. The solution to this is as you've said, not use it. Alternatively you can stop the service once you are associated with an AP to avoid it. Doing this in a login script works.

I've never had this problem and I've always used Windows (where I can) to manage available wireless networks. I'd be interested to see whether these particular laptops are successfully receiving an IP or not.

Once logged on, (irrelevant if the profile fails), open up a command prompt and type:

ipconfig /all

and see whether all IP information is being dynamically pulled down or not. If this is happening on a variety of laptops/workstations, log into each Access Point and re-enter your wireless security information.

[Geoff]

've never had this problem and I've always used Windows (where I can) to manage available wireless networks.

This article, in paticular the 'WZC Two-Step' section explains the issue.

Windows Wireless Zero Configuration: Five Steps to Sanity

[Michael]

Thanks for the link Geoff

Near the top of the page however it says -

Not a bad strategy on paper. But what if two APs are broadcasting the same SSID and are not on the same network? WZC will connect to the stronger one, whether you want it to or not. Which might hook you up to the wrong network, possibly interrupting an existing session with your desired network.

Now the easy solution to this is to rename the network. So if it's something like Belkin54g rename it to something completely different.