MaXKiLLz wrote:
If all you're going to do with your Air is sit at home, connected to your Airport router, then everything will seem fine to you. But if you decide to leave that dark cave of yours and wander out into the sunlight, you'll very likely experience problems. The "fix" Crapple put out doesn't fix anything. Try watching Netflix on the same router that was causing you problems before the fix. Then you'll see how nothing's changed.
People really need to stop generalising on these forums and this thread in particular!! This comment reads like it's fixed nothing for anybody. I have been testing it on my TP-Link router that I was having severe problems with prior to the fix being released and it has indeed fixed the connection issues entirely. Anyone that thinks that any device will stay connected flawlessly over wireless, forever, is living in cloud cuckoo land. Wireless ***** generally!
My only problem now is that Apple's implementation of SMB is unsuably slow. And that's a real problem for me now that all my files are shared from a Windows Server 2012 based HP Microserver. For that, I will be following up with Apple support. Not because I expect them to wave some magic wand and fix something that's been broken in OS X for a long time, but more so they have another statistic to add to the list. What worries me here is that in OS X 10.9 they are allegedly switching the default to SMB. SMB2 though, which is a different implementation so hopefully it may resolve the long standing issues there.
Anyway, back to the connection issues. Please don't generalise. It HAS fixed it for some people but what happens is that once it's fixed for them, like me they tend to turn their notifications off and will likely not bother to come back here to tell you so the people for whom it's not fixed will be the ones left shouting loudest. Which, clearly, is understandable.
