MAC Yosemite OS X 10.10.2 loses Wireless connectivity

  • 0
  • 1
  • Problem
  • Updated 4 years ago
  • Acknowledged
MAC Yosemite  OS X 10.10.2 loses Wireless connectivity


Situation exists at customer site UMass Medical School  with EWC running with Wireless AP3610-1, and the authentication is 802.1x using AD credentials.

Just starting troubleshooting, but since the issue seems to be specific to this OS and it's common enough to be posted all over the internet, I figured odds are good, someone has run into this already and best practices might already exist.   If so please share.
Photo of McKitrick, Mark

McKitrick, Mark, Employee

  • 170 Points 100 badge 2x thumb

Posted 4 years ago

  • 0
  • 1
Photo of Chris Sherman

Chris Sherman

  • 546 Points 500 badge 2x thumb
Oh Lord Mark,  Good luck.  We're all Mac and have been struggling mightily with this issue for years.  I'll step through what I have but I've not found best practices.  This really seems to be a moving target for Apple with Wi-Fi updates coming with nearly every update.

  • Can they upgrade the controller?  Extreme has made several changes that specifically deal with Apple's "improvements." I'm on with the APs purposely on
  • End users really need to be trained to turn their Wi-Fi off and back on again.  This solves connectivity issues - most of the time. 
  • Macs have a problem with caching bad info and good luck finding it.  There is nothing that I know of that's akin to doing a "repair" on a windows machine which seems to always fix the issue.  Here are the steps which must be done in order though:
  1. Turn off Wi-Fi
  2. Remove relevant keychain entries
  3. Remove relevant Wi-Fi networks 
  4. Remove any 802.1x profiles
  5. Delete the AirPort's location
  6. Create a new location
  7. Turn the AirPort back on and try again.
          I know the above is tedious but I can't stress enough how many machines it has made better.  If you find this to be helpful, let me know - I have a script which can be adapted to your location.
  • Macs seem to have a way harder time finding the best signal than Windows so they'll latch on to a poor signal and all-the-sudden go looking for a better one.  I've had SOME success shrinking the cell size, but Extreme told me that what I shrunk it to is now the default: MBR for the A/N radio: 12 Mbps.  I've had (and kept) the MBR for the G/N radio at 6 Mbps (which is the default for that radio) due to low density issues in certain areas.
  • Revisiting problem areas to re-channel if necessary.
  • If any Apple client is not up to date, have them turn off Bluetooth(or update!).  This problem seems to be solved with 10.10.2 (not sure about iOS yet).
  • References:
  1. A lot of banging my head and the bricks.
  2. My testing shows this to be fixed in 10.10.2:
  3. No clue what to do about this one except the wifi off/on trick:
Hope some of this helps - at least know that you are not alone.
Photo of Ronald Dvorak

Ronald Dvorak, Embassador

  • 51,164 Points 50k badge 2x thumb
Hi Chris,
just because I'm curious... why did the APs run with the older image?

Photo of Chris Sherman

Chris Sherman

  • 546 Points 500 badge 2x thumb
Hi Ron, I upgraded to and immediately started having more problems with our AirPlay setup - we're using Extreme's bonjour VLAN solution, Wi-Fi only. Rolled back and things calmed right down.

Photo of Brandon Clay

Brandon Clay, Escalation Support Engineer

  • 13,594 Points 10k badge 2x thumb
Just a heads up, OS X 10.10.3 was just pushed out from Apple, and it looks like it has some WiFi fixes. Unfortunately, I can't say if it will help with this, but it may be worth a shot.
Photo of Chris Sherman

Chris Sherman

  • 546 Points 500 badge 2x thumb
I've just done a lot of testing on ~12 machines and honestly don't see a lot of improvement.  Several times the machines thought they had an IP but had no network access.  Each time, checking the reports on the HWC - the offending clients weren't even ON the wireless.  Again(still), I'm calling this an Apple problem.  A few of the enlightening posts that have recently showed up about 802.1h I think were too late to make it into 10.10.3 so there's still hope.