serinde

That indeed is their contention. They assert Blackberries only try A, and on seeing no A, go into a huff and capitulate. Said assertion runs:

1. Influx of Blackberries all sending DHCP_DISCOVER on 802.11a


2. Wireless system's own DHCP server work queue fills up


3. Wireless system DHCP daemon crashes. Woe.


4. Notworks asserts Blackberry does not use b or g. Shut off a and you remove the source of the problem


5. Notworks also changes from vendor's DHCP daemon to Windows 2003 DHCP server


6. Notworks calls vendor and has them remote in and 'disable' a


7. Large numbers of Macs fail to associate


8. I tell them to put A back on. As soon as they do, my MacBook Pro can once again associate, get address, authenticate, Profit!


9. While my back was turned Notworks has turned off A again, it seems

So that's the first pile of WTF on my plate tomorrow. Off sick today.