Late 2013 Macbook Pro Retina 13'' Wifi Issues

I wanted to flag up this post, as it helped me resolve a wi-fi connectivity issue with a 2011 Macbook Air that recently came back from Apple with a new I/O board installed. The MBA would show as "connected" to our home wi-fi network (Apple Time Capsule operating in bridge mode) but internet connectivity was excruciatingly slow, with web pages timing out and/or hanging up completely. I tried several different troubleshooting tips that I'd read elsewhere (eg. deleting preferences, turning off Bluetooth, deleting/recreating network locations, renewing DHCP lease, etc) but nothing worked until I followed the instructions at the page linked below:

http://www.s0hel.com/blog/401/fixed-slow-wifi-issue-with-new-macbook-pro/

Changing the wireless channel to ch. 6 worked for me (same as described in the article).

After several days of frustration and multiple AppleCare phone calls & visits to the Apple Store, this was an extremely welcome discovery. Thanks!!!

I had dropped packages as well on my MBP 15" late 2013

Deleting and creating a new Wi-fi service under a different name worked for me.

1. Creating a New Wi-Fi Service (this solution worked for me!)
   • Copy and paste these instructions, because you'll be disconnected from the Internet and you'll need to reboot.
   • Go into your Network Preferences > Select Wi-Fi Service (in the list in the left column) > Click on the options (cog icon) > Select "Make Service Inactive" > Select Apply.
   • Select the same Wi-Fi Service > Delete It ( – ). Reboot.
   • Return to Network Preferences > Create a New Service ( + ).
   • Inside the prompt select Wi-Fi under Interface, name the Service Name something other than Wi-Fi. (I named mine Wi-Fi2. Apparently if you retain the previous Wi-Fi name the WiFi dropping will return on reboot.) > Click Create.
   • Click Apply.
2. Delete and Reconnect to your Preferred Network

   Go into your Network Preferences > Advanced > Select Your WiFi Network and Delete It ( – ). Reconnect to it.

3. Delete Bluetooth.plist

   Finder > Go (on your toolbar) > Computer > HD > Library > Preferences > Delete your Bluetooth.plist. Reboot

My Retina MPB is just a few months old. You would think they would stop selling them with this problem, or fix it before the sell them.

For a company that charges an arm and a leg for a computer you expect the computer to be better than anything else out there. I have no wifi problems from any of my old MAC or PCs that cost less than half the price.

Sure, they'll probably "allow" me to have if fixed for free, but I'll have to take time out of my schedule to drive an hour to an Apple store, wait there for a "genius" and then be without a computer for who knows how long while it gets fixed and then make the hour drive (2 hours both ways) to go pick it up. All for "free" because they are such a great company.

wow so this still has not been fixed?

Guys I'm circling back on the Stuck on Wake Wifi Issue I was talking about with you all.

It's tough to just tell people hey version blah fixed it for everyone! When it's really just your own experience of that problem being gone now for you. I'd like to chime in to say I also experience the problem with Yosemite.

I ended up updating my Macbook Pro 15" Retina to Yosemite 10.10.1 with a totally clean re-formatted install. And I still saw the issue. Then I also bought Mac Mini (Late 2014) which ships with Yosemite 10.10.0, updated to 10.10.1 on first boot, and again had the same issue for weeks.

I started using my 90 days of Apple Care. After about 5 calls to Apple over 3 days with the same case number (Apple Care never starts with a prompt for following up on an existing case, it's very frustrating) I was asked if I'd like to be forwarded to a "specialist" (taking a good 45 minutes after the normal 15 minute wait time, but you have to hang in there that specialist will give you a line for direct contact to follow up with the same person...) who basically walked me through what some people here already advocated and I'd previously tried unsuccessfully, only it's been working for 3-4 days straight so far. The first things tried were to change security from WPA/WPA2 PSK to just WPA2 PSK. Another was to turn off the automatic channel selection and stick to just a known channel. Neither of these on their own worked, but they may have contributed to the success of the next step.

It was to make a new network location, one that's basically equivalent to the default "Automatic" location. He was very careful however to instruct me to turn off the wifi first before doing that... that seems to be an important detail... and delete the key for the Airport password in the keychain (oddly I didn't have one). Once the new location is created it mysteriously turned on wifi again without me doing so, which seemed to take him a bit by surprise. Then we added the one and only access point I have at home and it's been working unlike when I feel I did exactly the same thing with the Automatic location. It seems to indicate that there's something borked in the prefs for the network location that they haven't yet correctly fixed in a true update. I couldn't say what though. My worry of course is that eventually this location's prefs will become borked, leading me to have to repeat the steps (and hope they take). I'd so very much prefer a "stops borking wifi wakeup" fix.

I have the same problem (missing wireless connection or take time to get wireless connection) after sleep. In both my macbook air and macbook pro retina. I am using the latest OS X Yosemite.

I do not know whats the problem with Apple, or if they cannot fix it!

This still is not over. I have upgraded a Macbook Pro (MacBookPro9,2 according to "About your Mac") to Yosemite 10.10.2. The WLAN chipset it has built in is the Broadcom BCM4331. The driver/firmware version is 7.15.159.13.12. I still get the same kind of latency with 1 second pings:

PING 192.168.1.22 (192.168.1.22) 56(84) bytes of data.

64 bytes from 192.168.1.22: icmp_req=1 ttl=64 time=1.84 ms

64 bytes from 192.168.1.22: icmp_req=2 ttl=64 time=111 ms

64 bytes from 192.168.1.22: icmp_req=3 ttl=64 time=31.7 ms

64 bytes from 192.168.1.22: icmp_req=4 ttl=64 time=1.59 ms

64 bytes from 192.168.1.22: icmp_req=5 ttl=64 time=71.6 ms

64 bytes from 192.168.1.22: icmp_req=6 ttl=64 time=104 ms

64 bytes from 192.168.1.22: icmp_req=7 ttl=64 time=19.9 ms

64 bytes from 192.168.1.22: icmp_req=8 ttl=64 time=60.2 ms

64 bytes from 192.168.1.22: icmp_req=9 ttl=64 time=60.4 ms

64 bytes from 192.168.1.22: icmp_req=10 ttl=64 time=87.4 ms

64 bytes from 192.168.1.22: icmp_req=11 ttl=64 time=110 ms

64 bytes from 192.168.1.22: icmp_req=12 ttl=64 time=33.0 ms

64 bytes from 192.168.1.22: icmp_req=13 ttl=64 time=64.6 ms

64 bytes from 192.168.1.22: icmp_req=14 ttl=64 time=76.2 ms

64 bytes from 192.168.1.22: icmp_req=15 ttl=64 time=4.44 ms

64 bytes from 192.168.1.22: icmp_req=16 ttl=64 time=1.63 ms

64 bytes from 192.168.1.22: icmp_req=17 ttl=64 time=42.6 ms

64 bytes from 192.168.1.22: icmp_req=18 ttl=64 time=62.5 ms

64 bytes from 192.168.1.22: icmp_req=19 ttl=64 time=86.3 ms

64 bytes from 192.168.1.22: icmp_req=20 ttl=64 time=109 ms

64 bytes from 192.168.1.22: icmp_req=21 ttl=64 time=30.5 ms

64 bytes from 192.168.1.22: icmp_req=22 ttl=64 time=52.8 ms

64 bytes from 192.168.1.22: icmp_req=23 ttl=64 time=75.3 ms

64 bytes from 192.168.1.22: icmp_req=24 ttl=64 time=98.2 ms

64 bytes from 192.168.1.22: icmp_req=25 ttl=64 time=130 ms

64 bytes from 192.168.1.22: icmp_req=26 ttl=64 time=39.0 ms

64 bytes from 192.168.1.22: icmp_req=27 ttl=64 time=63.7 ms

64 bytes from 192.168.1.22: icmp_req=28 ttl=64 time=86.5 ms

64 bytes from 192.168.1.22: icmp_req=29 ttl=64 time=116 ms

64 bytes from 192.168.1.22: icmp_req=30 ttl=64 time=31.4 ms

64 bytes from 192.168.1.22: icmp_req=31 ttl=64 time=59.2 ms

^C

--- 192.168.1.22 ping statistics ---

31 packets transmitted, 31 received, 0% packet loss, time 30038ms

rtt min/avg/max/mdev = 1.597/62.117/130.333/36.253 ms

If one pings in 0.2 second intervals things look up, but are still not the way they ought to be:

--- 192.168.1.22 ping statistics ---

1848 packets transmitted, 1847 received, 0% packet loss, time 370577ms

rtt min/avg/max/mdev = 0.876/3.763/125.117/7.167 ms

If I boot a Linux distribution on that Macbook and make it accessible via WLAN, the ping average drops to a bit above one millisecond, 1.2 or thereabouts. Also, the maximum latency does not go above 20 milliseconds.

All my testing was done on a pretty quiet WLAN with two workstations attached. The access point was a Ubiquity Unifi, the 2.4 Ghz model that does a/b/g/n. Pinging was not done from the Mac, but from a server on the network (which should not affect results).

I had all the same problems - slow internet, wifi connection, slow to router, connection dropping etc. I did all the things I could found on the blogs - change channel, change dates and time zones, delete wifi files, do all possible resets on the mac, etc., but nothing worked. I am running Yosemite 10.10.2. At the same time my iphone and Windows based PC worked fine with the previous router (tp-link).

So I gues there must be some compatability issue which I failed to fix or even find. Maybe it is that there are other routers around me that cause this interfierance, I do not know.

Finally, I got tired of all this mocking about and simply went to the shop and bougt a little more expensive router (cisco) and it all is fixed now and working great. No problem at all. Just pluged in the router, connected the mac and the net flies!!

I turned off IPv6 and my Netgear 2.4GHz works a treat with my MacBook Pro Retina.

It seems that this crappy issue is still ongoing. My 13"MBP non-retina (OSX10.9.5) just reached a constant speed of 57Mbps and the newly bought 13"MBP retina (OSX10.10.2) had a peak of 26Mbps. And I have tried all mentioned solutions, except for downgrading.

Between all tests,..noticed the MBP retina did not want to connect to a 5Ghz wireless N only. Only 5Ghz mixed mode A/N worked..

This is ridiculous. Is this where Apple wants to be seen as? Overpriced design and no/bad functionality? What happened to the quality of roughly 5 years ago?

This is indeed ridiculous. HOURS on the phone with Apple support, HOURS going through all the suggested fix sites.

In the end, we found that if we changed to WR702N wifi extender to wireless N ONLY, then it would actually work!

We've also got a £5 lan to USB adaptor coming from ebay, I'll let you know how that gets on. The problem now is that with the wifi on n only, an older Android phone and the Wii won't connect.

We should not be having to do this on 10.2.2 - we shouldn't be having to spend money on devices to workaround a problem that ONLY this one Mac has.

You can sit an Android phone and the old Mac all three together streaming something - the other two will be rock solid. The 2 month old Retina Macbook will randomly drop. Massive PITA.

I had quite similar issue (MBP 13 Retina, late 2013) just a moment ago:

The pings to the nearest AP looked like:

PING 192.168.1.80 (192.168.1.80): 56 data bytes

Request timeout for icmp_seq 0

Request timeout for icmp_seq 1

64 bytes from 192.168.1.80: icmp_seq=2 ttl=255 time=726.725 ms

Request timeout for icmp_seq 3

Request timeout for icmp_seq 4

64 bytes from 192.168.1.80: icmp_seq=3 ttl=255 time=2015.935 ms

64 bytes from 192.168.1.80: icmp_seq=4 ttl=255 time=1421.472 ms

64 bytes from 192.168.1.80: icmp_seq=5 ttl=255 time=809.569 ms

64 bytes from 192.168.1.80: icmp_seq=6 ttl=255 time=1028.922 ms

Request timeout for icmp_seq 9

Request timeout for icmp_seq 10

Request timeout for icmp_seq 11

^C

--- 192.168.1.80 ping statistics ---

13 packets transmitted, 5 packets received, 61.5% packet loss

round-trip min/avg/max/stddev = 726.725/1200.525/2015.935/473.390 ms

I tried to look for solution and I found out the problem is related to BLUETOOTH. I just switched BT off, switched WiFi off, then started WiFi on and BT on. Now it works fine, no problems. Pings usually below 2ms.

I hope this helps somebody.

Hello,

to everyone who has been tortured since this issue had popped up at the day light...

I just mention that I tried most of things (wifi on/off, changing router settings,...standing on my hands praying and stinging needles to woodo figure of yosemite developer)...

Coming back to the point, after all this I tried the last call option - which in it's own way, does not present anything extraordinary.

I did RESET of system management controller aka SMC.

The thing is very basic: turn off mac > simultaneously press key combination > SHIFT + CTRL + ALT + power button

Well I did it for several time to assure myself, that i did not miss any hokus-pokus thing anymore (I even hold this button comb for a sec;))

After you guys go through this, JUST SIMPLY TURN ON your mac again, as usual...well...if this does not help at least to some of you then I do not knwo what else...

Actually my friend is a developer and he stated, that 10.10.2 should remove the bug...and here we go...different people, different machines, diff experiences:///??? LUCK OR JUST BAD WOODOOO??

who knows...

here comes a link to official guide for SMC reset:

Intel-based Macs: Resetting the System Management Controller (SMC) - Apple Support

wish to all of us a luck with this shajt:P

Hello,

So 10.10 solved the problem but it seems it is now back!

Here is what happen to a ping:

64 bytes from 8.8.8.8: icmp_seq=1685 ttl=56 time=23.634 ms

64 bytes from 8.8.8.8: icmp_seq=1686 ttl=56 time=17.881 ms

64 bytes from 8.8.8.8: icmp_seq=1687 ttl=56 time=22.189 ms

64 bytes from 8.8.8.8: icmp_seq=1688 ttl=56 time=27.764 ms

Request timeout for icmp_seq 1689

Request timeout for icmp_seq 1690

Request timeout for icmp_seq 1691

Request timeout for icmp_seq 1692

Request timeout for icmp_seq 1693

Request timeout for icmp_seq 1694

Request timeout for icmp_seq 1695

Request timeout for icmp_seq 1696

Request timeout for icmp_seq 1697

Request timeout for icmp_seq 1698

Turning off and on the wifi solves the issue. But this is quite annoying.

I keep BT on.

I submitted a bug report to apple. But no response yet.

I had the same problem and what seems to have helped me was this : Slow WiFi issues after 10.10.2

Fingers crossed, everything seems for now.