Hey Scott

Hold up have a look here:
http://www.airdefense.net/products/adpersonal/

This may resolve the issue for you (and me) and you won't have to worry about the IP ranges or VLAN etc.. I'll be testing it tonight so will let you know my thoughts later.

Let me know if you have a go! 8)

The only problem is that we have roughly 60,000 clients globally that would need the agent and cost is an issue (as always). The XP driver fix is preferable and I am on the phone discussing it with the team as I type.

I have directed my WLAN guys to work with the client build center as they test the driver's ability to attach and detach from the WLAN appropriately AND release the IP address back to the pool. More on this by mid next week at the latest.

From the (Dell) client side, the following update was found and tested:

http://support.dell.com/support/edocs/network/p70008/EN/props.htm#toc_70

It disables the WLAN radio when it senses a wired connection

However, the client wasn't returning the DHCP assigned address automatically and the existing lease period was set to 72 hours. Ultimately we decreased that period to 3 hours at which time the released address now returns to the pool...that helped a lot.

The last issue was capacity (the number of sessions open at the AP). Using the (Cisco) WLSE tool, we monitored all of the APs in the building, logging session numbers hourly and found that at some points in the day, certain APs were showing as many as 45 simultaneous sessions (or associations). We surmised that many of these were just beaconing, no actual traffic other than the acknowledgement between the client device and the access point. (and load balancing thru auto channeling was on too.) Since we had already re-surveyed the building for an 802.11g upgrade and had planned on adding 6 additional APs, I think we will have that covered. We shall see.

An interesting exercise, Gromit...wondering how you are doing there at your place.