Q: Late 2013 Macbook Pro Retina 13'' Wifi Issues

Well got to say that after I deleted preferences, created new network location (just in case) and put wifi on the top of the list – wifi works since. Before I had to flip if off and on almost every hour, now it just works. And I was about to go to the service center. 

I ordered my macbook pro yesterday, despite the apparent wifi-problems

I will let you know if I have issues too.

Fellas

I tried everything, no luck. I could connect to my private wifi, but no others. All said Connection failed.

My soultion to make wifi work again, was install Maverick on top of my current Maverick installation.

I downloaded Maverick. Didnt have time, when it asked to continue I closed it.

Anyway, the Maverick installation had been downloaded, 5gb or so. It's an app Named "Install Maverick .."something... app.

So, used that App to install Maverick on top of my existing Maverick. 1 hour after, the issue is now gone.

LOTS of fustrations, but a fix. Hope it doesnt come back.

Cheers

Hi,

Just want to add my experience with this problem. My macbook pro retina 13 arrived yesterday and after installing all updates I surfed a little bit on the web and saw some youtube videos. I was in the same room of the wireless router and I started to notice some slow down and even disconnections. I even captured one with the diagnotics tool.

I measured ping times to my router and they were very high (more than from 150ms to 8000 ms). I even got timeouts and lost packages. On my windows laptop I was getting ~1ms ping times.

Today I brought the laptop to work and I tested it side by side with a macbook pro retina 15 mid 2012. While the mid 2012 was performing 7.9ms on average my late 2013 macbook pro was performing 130ms and in the worst case 300 ms.

I tested with 3 different networks and my macbook pro performed this bad on all.

I contacted apple care and they will replaced this unit. I'm afraid that I will not solved the problem...

Does anybody have normal pings and the wireless working as expected?

PS: I know is off topic but I checked the system logs and even after the updates I still have log messages about the keyboard / trackpad problem. Maybe you should also check yours.

Best regards

I don't think anyone has "normal" ping times with the latest driver. This driver replaced an earlier one that did not have the ping latency problem (for most people), but did seem to have problems with dropping connections and reconnecting after sleep. There's a lot of discussion whether the slow pings are a "feature" or issue. For me, it's definitely an issue as this behavior goes hand in hand with slow wifi overall (slow browsing, etc.).

You could consider trying the older driver. It solved the ping latency and low wifi for me (I didn't have the reconnection after sleep issue). I wrote a howto with a couple of scripts to make it easy (and safer):

https://discussions.apple.com/message/24476514#24476514

Zip file you'd need:

https://www.dropbox.com/s/s6un9ou3cnxvq2q/ReplaceDriver.zip

If you decide to try it, please let us know how it worked out.

It doesn't exactly reflect the issues I'm having (actually doing better on 11g at home), but this is one of the best, most comprehensive analyses I've read thus far:

http://www.midwesternmac.com/blogs/jeff-geerling/2013-macbook-air-wifi-problems

I think that the rMBP and MBA wifi issues are virtually identical because they use the same broadcom chipset.

Just received my MacBook Pro today. After registering and stuff I quickly did a ping test on terminal with the command:

ping -c 20 192.168.0.108

PING 192.168.0.108 (192.168.0.108): 56 data bytes

64 bytes from 192.168.0.108: icmp_seq=0 ttl=64 time=0.082 ms

64 bytes from 192.168.0.108: icmp_seq=1 ttl=64 time=0.120 ms

64 bytes from 192.168.0.108: icmp_seq=2 ttl=64 time=0.123 ms

64 bytes from 192.168.0.108: icmp_seq=3 ttl=64 time=0.146 ms

64 bytes from 192.168.0.108: icmp_seq=4 ttl=64 time=0.119 ms

64 bytes from 192.168.0.108: icmp_seq=5 ttl=64 time=0.137 ms

64 bytes from 192.168.0.108: icmp_seq=6 ttl=64 time=0.136 ms

64 bytes from 192.168.0.108: icmp_seq=7 ttl=64 time=0.121 ms

64 bytes from 192.168.0.108: icmp_seq=8 ttl=64 time=0.138 ms

64 bytes from 192.168.0.108: icmp_seq=9 ttl=64 time=0.140 ms

64 bytes from 192.168.0.108: icmp_seq=10 ttl=64 time=0.140 ms

64 bytes from 192.168.0.108: icmp_seq=11 ttl=64 time=0.157 ms

64 bytes from 192.168.0.108: icmp_seq=12 ttl=64 time=0.083 ms

64 bytes from 192.168.0.108: icmp_seq=13 ttl=64 time=0.147 ms

64 bytes from 192.168.0.108: icmp_seq=14 ttl=64 time=0.150 ms

64 bytes from 192.168.0.108: icmp_seq=15 ttl=64 time=0.122 ms

64 bytes from 192.168.0.108: icmp_seq=16 ttl=64 time=0.137 ms

64 bytes from 192.168.0.108: icmp_seq=17 ttl=64 time=0.117 ms

64 bytes from 192.168.0.108: icmp_seq=18 ttl=64 time=0.137 ms

64 bytes from 192.168.0.108: icmp_seq=19 ttl=64 time=0.147 ms

--- 192.168.0.108 ping statistics ---

20 packets transmitted, 20 packets received, 0.0% packet loss

round-trip min/avg/max/stddev = 0.082/0.130/0.157/0.019 ms

I am not an expert on the wifi issues. But the 192.168.0.108 IP is the address which shows up in my control panel. So I guess this is the right one to ping?

At this moment I still have Mavericks 10.9.

My router is a sitecom wlr-6100. At this moment if have some setting set on on, on the router where it checks if a website is safe. That ***** because it slows down the browsing a bit, and I need to turn it off, but maybe it has an effect on the latency. I don't know.

The pings look right, but as I said I am no expert. So if my ping command is wrong somehow, let me know.

If I can do other testing, let me know too. If things still go downhill later I'll let you know too.

Off-topic. The laptop is great.

First of all, congrats on your buy

I get a feeling you are not using the Router IP but pinging the IP of your machine. You could get the Router Ip by going to network settings (TCP/IP Tab in More Options)

You are right about the IP...

This is what I get with the correct router IP address first time I started pinging.

ping -c 30 192.168.0.1

PING 192.168.0.1 (192.168.0.1): 56 data bytes

64 bytes from 192.168.0.1: icmp_seq=0 ttl=64 time=64.516 ms

64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=87.530 ms

64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=8.164 ms

64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=30.740 ms

64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=53.740 ms

64 bytes from 192.168.0.1: icmp_seq=5 ttl=64 time=77.440 ms

64 bytes from 192.168.0.1: icmp_seq=6 ttl=64 time=99.456 ms

64 bytes from 192.168.0.1: icmp_seq=7 ttl=64 time=19.829 ms

64 bytes from 192.168.0.1: icmp_seq=8 ttl=64 time=41.124 ms

64 bytes from 192.168.0.1: icmp_seq=9 ttl=64 time=65.038 ms

64 bytes from 192.168.0.1: icmp_seq=10 ttl=64 time=89.077 ms

64 bytes from 192.168.0.1: icmp_seq=11 ttl=64 time=8.474 ms

64 bytes from 192.168.0.1: icmp_seq=12 ttl=64 time=1.703 ms

64 bytes from 192.168.0.1: icmp_seq=13 ttl=64 time=54.688 ms

64 bytes from 192.168.0.1: icmp_seq=14 ttl=64 time=77.093 ms

64 bytes from 192.168.0.1: icmp_seq=15 ttl=64 time=100.112 ms

64 bytes from 192.168.0.1: icmp_seq=16 ttl=64 time=0.949 ms

64 bytes from 192.168.0.1: icmp_seq=17 ttl=64 time=44.718 ms

64 bytes from 192.168.0.1: icmp_seq=18 ttl=64 time=66.943 ms

64 bytes from 192.168.0.1: icmp_seq=19 ttl=64 time=89.735 ms

64 bytes from 192.168.0.1: icmp_seq=20 ttl=64 time=9.556 ms

64 bytes from 192.168.0.1: icmp_seq=21 ttl=64 time=32.082 ms

64 bytes from 192.168.0.1: icmp_seq=22 ttl=64 time=53.762 ms

64 bytes from 192.168.0.1: icmp_seq=23 ttl=64 time=77.477 ms

64 bytes from 192.168.0.1: icmp_seq=24 ttl=64 time=100.529 ms

64 bytes from 192.168.0.1: icmp_seq=25 ttl=64 time=20.883 ms

64 bytes from 192.168.0.1: icmp_seq=26 ttl=64 time=44.564 ms

64 bytes from 192.168.0.1: icmp_seq=27 ttl=64 time=66.592 ms

64 bytes from 192.168.0.1: icmp_seq=28 ttl=64 time=89.287 ms

64 bytes from 192.168.0.1: icmp_seq=29 ttl=64 time=9.601 ms

--- 192.168.0.1 ping statistics ---

30 packets transmitted, 30 packets received, 0.0% packet loss

round-trip min/avg/max/stddev = 0.949/52.847/100.529/31.981 ms

Strange thing is that after this ping series I continually get these (you can understand I am pinging my pants off right now):

ping -c 10 192.168.0.1

PING 192.168.0.1 (192.168.0.1): 56 data bytes

64 bytes from 192.168.0.1: icmp_seq=0 ttl=64 time=0.851 ms

64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=0.836 ms

64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=0.838 ms

64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=0.887 ms

64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=2.695 ms

64 bytes from 192.168.0.1: icmp_seq=5 ttl=64 time=0.769 ms

64 bytes from 192.168.0.1: icmp_seq=6 ttl=64 time=0.818 ms

64 bytes from 192.168.0.1: icmp_seq=7 ttl=64 time=1.819 ms

64 bytes from 192.168.0.1: icmp_seq=8 ttl=64 time=0.873 ms

64 bytes from 192.168.0.1: icmp_seq=9 ttl=64 time=0.863 ms

--- 192.168.0.1 ping statistics ---

10 packets transmitted, 10 packets received, 0.0% packet loss

round-trip min/avg/max/stddev = 0.769/1.125/2.695/0.600 ms

And at this moment I am doing nothing but pinging, so no internet, no downloads (no updates that I am aware of). So that looks reasonable, although there is some fluctuation.

But this is 5 minutes later

ping -c 10 192.168.0.1

PING 192.168.0.1 (192.168.0.1): 56 data bytes

64 bytes from 192.168.0.1: icmp_seq=0 ttl=64 time=18.720 ms

64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=0.890 ms

64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=64.764 ms

64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=87.223 ms

64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=0.857 ms

64 bytes from 192.168.0.1: icmp_seq=5 ttl=64 time=30.356 ms

64 bytes from 192.168.0.1: icmp_seq=6 ttl=64 time=53.137 ms

64 bytes from 192.168.0.1: icmp_seq=7 ttl=64 time=76.255 ms

64 bytes from 192.168.0.1: icmp_seq=8 ttl=64 time=99.090 ms

64 bytes from 192.168.0.1: icmp_seq=9 ttl=64 time=19.414 ms

--- 192.168.0.1 ping statistics ---

10 packets transmitted, 10 packets received, 0.0% packet loss

round-trip min/avg/max/stddev = 0.857/45.071/99.090/34.053 ms

I checked my download and uploadspeeds, but they are ok too.

I checked it on 2,4 GHz n.

Tomorrow I will test the connections at work where I will be moving a lot with my laptop.

At this moment I do not experience any severe influence of this latency.

I can play my speedchess games on a chess server (ICC) without any serious lag, internetbrowsing is ok, download speeds are fine. But I come from an awfully old and slow laptop, so my judgement is off ;-)

Sorry for flooding this post with ping times.

I wouldn't worry too much about the ping times if there are no other issues like packet drops, page load issues etc. I too have low pings but do not face any other problem unlike many others here. Test with other networks and if it is fine, keep it. The ping problem is a driver issue and will be fixed for sure by Apple.

Having similar issues on my 13" 8GB/256GB. The 5ghz band is not reliable at all. Moving files to my NAS is slow and generally causes the Mac to disconnect from the network. I also get the issues waking up from sleep. However, the 2.4ghz band appears to be fine. Files move to my NAS at about 9-11MB/s and speed is consistent. The connection hasn't dropped as far as I know.

For now I'm just using the 2.4ghz band. It's fast enough and actually works. Disappointed though as my desktop on 5ghz is able to push files to my NAS at 20-30MB/s. Since I do photo work on my Mac it would be useful to transfer files 2-3x faster.

UPDATE:

I am 0,5m away from a 802.11n AP here at my workplace. I started a FTP (server is in my LAN) transfer and enabled/disabled bluetooth while the download is going. Look at the drop down - the download speed drops immediately if I enable bluetooth and goes up after i disable it:

I have quite a strange issue as well regarding WiFi.

I used to work with a MacBook Pro Mid 2010 - two weeks ago I order a new one, MacBook Pro Retina 13.

I have a router from TP-Link, Dual Band, Archer C7.

After a few days I recognized that even surfing is very slow, using 5GHz, AC mode - first I had the suspicion of some problems of my ISP, but other devices had normal speed and access.

Next I tested 5 GHz AC Mode with my smartphone (LG G2) and got connection bandwidth of approx. 450 MBits.

With my MacBook Pro for the first seconds I approx get the same bandwidth and then it drops to 7 MBit (if I can trust the informaton from MacOS, using the WiFi Icon and ALT). I already tried the latest beta firmware for my router - no change... even if I am next to the router.

At the moment I am not really sure, if it is the router or the MacBook Pro - on the other hand - if am using n-mode or 2,4 GHz network I do not have any problems...

Here some before and after screenshots to clarify what I mean, it's the same location, with a duration of about 15 secs between the screenshots:

Any hint will be highly appreciated - my 5GHz network is the only one in the area... all others are 2,4GHz.

Best regards,

Michael

Guys, today I gave up on this issue and sent my Macbook Pro 13" Retina back. I wish all of you good luck on further investigation. I'm very disappointed, but I'm still hoping for you apple will fix that.

I will reuse my old Macbook pro.

I understand you.

I was contacted by Apple and agreed to to test a beta version of a future OS version, it's worth a try.