On Mar 27, 2014, at 12:25 AM, Tristan Gulyas <[email protected]> wrote:
> Hi all, > > We’ve seen several occurrences of an issue where wireless clients would not > accept an IP address from our DHCP server after authenticating. > > This seems to be limited to Broadcom devices running either Windows 8.1 or > Ubuntu Linux (seen this on 12.04). > > Our infrastructure is Cisco based (derivative of 7.2.111.3 firmware) on 3600 > series APs. > > Has anybody else seen something similar? We have seen a small number of similar problems but in some cases they may have been Intel wireless chips that did not get DHCP when other clients were also connected to an AP. http://www.intel.com/support/wireless/wlan/sb/CS-034535.htm A work around that some folks here found (not sure if it works for both Intel and Broadcom) was to disable 802.11n on the problem machines so they just used the older 802.11 speeds. Once 802.11n was disabled on the problem machines they obtained IPs via DHCP just fine. Since it was only a small number of machines we have not discovered more details but I suspect it may be related to our disabling of lower 802.11n speeds on our wireless network. (Lower 802.11 speeds are also disabled). > > Cheers, > Tristan > > > Tristan Gulyas > Wireless Network Engineer > Network Operations > eSolutions | Monash University > 738 Blackburn Road Clayton 3800 > www.monash.edu | [email protected] > > > > > > ********** Participation and subscription information for this EDUCAUSE > Constituent Group discussion list can be found at > http://www.educause.edu/groups/. > --- Bruce Curtis [email protected] Certified NetAnalyst II 701-231-8527 North Dakota State University ********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/.
