mac osx 10.9 Mavericks wifi issue

Thanks, I have had a look at the Edimax versions and they look quite neat and unobtrusive.

I will bear them in mind as a suitable alternative.

I find it odd that my ipad mini and an old ipod touch have no problems connecting at all.

I was offered the chance to have the machine replaced but judging by the number of comments I have seen I don't think that would make any difference.

I think about the only difference it would make is a small bump in a hardware "turnaround" which may show up on someone-important-in-Apple's monthly report, and may bring more deserved attention to these issues. If it isn't a hassle for you, I would suggest you do this.

Yes there seems to be a lot of people with the same issue.

If only large companies would admit there is a problem then you would know that something is being actively done about it.

Electronics companies are quite happy to put out products (and I especially include software) that hasn't been tested to the limit.

There are always deadlines that must be met come what may.

The older machines work on the older networks because they are using standard protocols... the "new" protocol was not even conceived when many of those routers were designed and manufactured.

The "standard" was only approved in Jan of '14 - just like many technology there are "undiscovered features" as reality unfolds where "theory" meets "real life" application.

Theoretically backward compatibility was forecast not to be a problem. But one can not theorize each and every scenario a user will create or run into...

What I've just written is not really a solution, nor an endorsement, or condemnation, just an attempt at a more useful explanation of why what's happening could be happening than merely gripping.

I guess I would say that if you can not upgrade your wireless environment to 802.11 ac and you are having network issues best to drop back to 10.8.5 as an OS and use a pre mid-'011 box.

Unless you have the download speed then ac is nearly a meaningless upgrade (maybe a little stronger single). I live in the country and am lucky to get 6 Mbs download on a DSL and I am just 2K feet from a repeater. I could add an airport extreme and it wouldn't do anything for me. I cannot get enough data to take advantage of ac.

Then you probably won't upgrade machines soon.. or the upgrade won't have to do with wireless bandwidth. But if you want a solid connection regardless of your total bandwidth you may have to move to a new 802.11 ac router just to keep a constant n band connection.

At a certain point old technology becomes obsolete... wireless routers that do not, or can not support 802.11 ac are about to join (if they haven't already) dot matrix printers and B & W or G & W monitors, floppy disks and optical drives. If you have a new MB A or P you really need to rethink the decision to not upgrade your wireless router.

I'm a guy who's still using a PowerPC 7600 running OS 9 - for certain applications that I do not "appreciate" or feel a need to have/use the "newest" version. I also have a newer 11" MBA.

I have a '93 Corvette - because I appreciate it's style... I will keep it but I am currently shopping for a new coupe (won't be a 'Vette).

Ultimately satisfaction is achieved when you feel you "got a good deal" for most that's when use directly correlates with function.

I have no proof - but I think a lot of people jumped on Mavericks because it was a "free" upgrade. My Daddy always said "You pay for what you get and you get what you pay for." - for many of the people here... they received full value.

Of course I'm not talking about first time Apple Laptop users... if you get a new box you have no choice...

I don't think any of these issues have to do with Wifi standards, and it is very annoying when people try to make excuses for Apple's incompetence.

These problems, all of them, have to do with either Apple hardware being crap or their software engineer's incompetence and all that points to Apple's lack of quality control. Apple has always had crap software, they have just been very good at presenting a "polished" look (read: lipstick on a pig) ...so none of this is surprising really.

I can offer proof that "I'm not making this up!"- as Dave Berry likes to say-

Most of these articles are from mid to late '013 - remember the standard was only just approved ~3 months ago. Apple is one of the first... I predict similar problems for other manufactures... but have no hard data.

http://www.zdnet.com/the-five-things-you-need-to-know-about-gigabit-wi-fi-802-11 ac-7000017112/

http://www.fiercecio.com/techwatch/story/why-enterprise-should-forget-about-8021 1ac-now/2013-09-17

http://www.fiercecio.com/techwatch/story/why-enterprise-should-forget-about-8021 1ac-now/2013-09-17

Again as I said the 802.11 ac is more complicated than earlier versions of wireless.

..Even though 802.11ac is the futurephysical layer in wireless LANs, it will not be the only physical layer. APs that are sold as “802.11ac APs” will have one 5 GHz radio running 802.11ac, and they will also have a second 2.4 GHz radio running 802.11n. Even as 802.11ac becomes established, the 2.4 GHz band will continue to depend on the same 802.11n technology that has been used for the past several years.

As I said it's not just "crappy hardware or programming" it's a complicated new technology that as pioneers discover and point out the quicksand, badlands and other dangers as it were those following will have an easier time.

no237 wrote:

I don't think any of these issues have to do with Wifi standards, and it is very annoying when people try to make excuses for Apple's incompetence.

These problems, all of them, have to do with either Apple hardware being crap or their software engineer's incompetence and all that points to Apple's lack of quality control. Apple has always had crap software, they have just been very good at presenting a "polished" look (read: lipstick on a pig) ...so none of this is surprising really.

+1

I knew the second that this thread popped up long after all the others that already existed with hundreds of thousands of veiws, that this conversation would go awry. OK. Now listen, THIS HAS BEEN A PROBLEM SINCE 2007. IT'S NOT A MAVERICKS PROBLEM OR SPECIFIC MODEL. IT'S AN APPLE, LOOKING TO BE SOFTWARE SINCE SNOW LEOPARD ISSUE OR BEFORE. AND IT COULD BE HARDWARE, BUT THERE ARE TOO MANY CONFIGURATIONS OUT AND ONLY A FEW OS's. Understand?

My early 2008 MBP was working great up until last June (Snow Leopard, MTNLN, Lion, XP on separate partitions), then the WiFi just stopped. And all the while up to June I was counting my blessings while I read the threads about WiFi dropping, then it just stopped. Long before Mvrx was around. Then in early August it started working again. Nothing changed. It just started working. Then in October it stopped again and now it tries to work in many ways but just doesn't come fully up and stay up. So under any OS that I can run on my MBP. I get no WiFi where I did.

But the amazing part is how quiet and in some cases "dumb" Apple is being about this. Unless the problem is so wide spread that it's gonna nail the "heck" out of the bottom line and they are burying it. Good Luck!

OK, Trolls - "Come and get me!!!!"

I have a rMBP 13" 2013 Late model. I've gone through all 21 pages of this discussion and have tried ALL suggestions and recommended repairs expect for the ping work arounds. I have been on the phone with Apple Care several hours several times and was escalated to a wifi specialist who was very thorough and nice... But unfortunately all the present suggestions and trouble shooting has not fixed the same problem most are having of their wifi not automatically reconnecting after sleep mode.

The only thing that has worked for me, which just a band aid at this moment, is turning Bluetooth OFF. It appears to me that it is Bluetooth/Wifi signal conflict.

Hope Apple releases a fix for this soon. Have had my Mac for a month, love it, but this issue is really inconvenient and not like Apple

I agree it's a Mavericks issue and Apple needs to fix it. Late last year we replaced an old laptop with a MacBookPro Haswell w/Mavericks. After only a week it developed this problem, WiFi seems to go Zombie after the laptop went to sleep. Turning WiFi of an on again restored the connection. Most of the time turning off Bluetooth prevented that from happening.

I did many of the things suggested on the Forum. At some point, months later, and several AppleCare calls later, it seemed to resolve itself tho I'm not 100% sure which step did it but it was before the 10.9.2 update. I now have BT on and I'm not seeing the problem.

I learned to ask the AppleCare reps (who seemed not to be aware of this) to forward me to the Network specialists who ABSOLUTELY KNEW it was a problem and said a fix would be offered perhaps by Mar or Apr!

We just replaced our aged MacPro with an iMac with Mav 10.9.2. After two days of use, I am seeing the very same problem on the iMac! Turning off BT is not an option as it's needed for the keyboard and the track pad.

I'm going to send another email to timcook@apple.com tho I received no response (not surprised) the first time.

I'm a long time Apple user (owned an Apple IIe and half of every model since) and this is poor at best. It's been months and no fix yet.

i m on 10.9.2 using macbook air. my wifi works only around d router n if i take away my mac a bit away it get disconnected inspite of my iphn n ipad is working very well in dat same locations whr my macbook is nt working. plzzz any suggestions. n it show d exclaimatry sign(!) on wifi dislay sign.. plzzz guide me guys

no237,

Your comments are not helpful and suggest that you might want to go back to your Windows forum and let the Macintosh users deal with their own problems.

I can report that, so far, the fix I posted here a month ago that solve it for a new MacBookPro with Mavericks, seems to have solved the problem on the new iMac.

That fix is, go to Energy Saver control panel and uncheck "Wake for network access".

Kindly try it and let us know if it works for you. If enough people find this works, we'll let Apple know via the Developer's Bug Report.