I have also been having a dreadful time with my brand new rMBP 2013. This is my 3rd one. The first had problem after problem and after several visits and numerous migrations they realized it was the solid state hardrive. My second laptop had wifi issues.. turned out to be faulty aetenna/airport. Hopefulluy, this new one isnt going to cause me any problems.. but already things feel sluggish and mine it the top of the line 13"
I did smc and pram nvram resets, which seemed to help. I haven;t been able to compare my pings with someone else's computer, but they are more consistent than they were before. Here is a sample.
64 bytes from 172.31.168.1: icmp_seq=0 ttl=255 time=1.401 ms
64 bytes from 172.31.168.1: icmp_seq=1 ttl=255 time=4.919 ms
64 bytes from 172.31.168.1: icmp_seq=2 ttl=255 time=1.525 ms
64 bytes from 172.31.168.1: icmp_seq=3 ttl=255 time=1.656 ms
64 bytes from 172.31.168.1: icmp_seq=4 ttl=255 time=1.577 ms
64 bytes from 172.31.168.1: icmp_seq=5 ttl=255 time=1.618 ms
64 bytes from 172.31.168.1: icmp_seq=6 ttl=255 time=1.469 ms
64 bytes from 172.31.168.1: icmp_seq=7 ttl=255 time=1.498 ms
64 bytes from 172.31.168.1: icmp_seq=8 ttl=255 time=1.387 ms
64 bytes from 172.31.168.1: icmp_seq=9 ttl=255 time=4.172 ms
64 bytes from 172.31.168.1: icmp_seq=10 ttl=255 time=1.613 ms
64 bytes from 172.31.168.1: icmp_seq=11 ttl=255 time=2.055 ms
64 bytes from 172.31.168.1: icmp_seq=12 ttl=255 time=1.749 ms
64 bytes from 172.31.168.1: icmp_seq=13 ttl=255 time=1.463 ms
64 bytes from 172.31.168.1: icmp_seq=14 ttl=255 time=1.623 ms
64 bytes from 172.31.168.1: icmp_seq=15 ttl=255 time=1.570 ms
64 bytes from 172.31.168.1: icmp_seq=16 ttl=255 time=1.647 ms
64 bytes from 172.31.168.1: icmp_seq=17 ttl=255 time=1.823 ms
64 bytes from 172.31.168.1: icmp_seq=18 ttl=255 time=1.609 ms
64 bytes from 172.31.168.1: icmp_seq=19 ttl=255 time=3.217 ms
64 bytes from 172.31.168.1: icmp_seq=20 ttl=255 time=1.428 ms
64 bytes from 172.31.168.1: icmp_seq=21 ttl=255 time=1.967 ms
64 bytes from 172.31.168.1: icmp_seq=22 ttl=255 time=2.144 ms
64 bytes from 172.31.168.1: icmp_seq=23 ttl=255 time=1.722 ms
64 bytes from 172.31.168.1: icmp_seq=24 ttl=255 time=3.569 ms
Well, I too went through my second one in a week trying to solve this problem. Last attempt was at the apple store. I was able to actually determine with a "genius" that it was happening on EVERY computer that has the Haswell processor in it.
We did a ping to the local router and the ping results were all over the place and extemely slow.
I ended up returning the LAte 2103 MBPr 13" and will wait for them to get this right.
The only thing they said they could do is keep the laptop and run tests. I told them they have a whole store of laptops with the EXACT same issue. I was taking mine back to Best Buy and get my money back.
I'm taking my late 2013 rMBP 13" to the Apple Store tomorrow. I too am getting erratic pings to my gateway as well as slow connection speeds in general. Sometimes it would work fine for a while if I turned wifi off and back on or rebooted.
General web surfing is tolerable, but downloading a large file is painful. Interestingly, when I do a test on speedtest.net, upload speeds are unaffected. I still get my expected upload speeds (20mbit) while download speeds are about 1/4 what they should be.
After more troubleshooting by resetting my SMC and NVRAM as well as deleting the .plist files related to wifi connectivity as listed on various websites, I can no longer even connect to my 5ghz 802.11n network at all (2.4ghz on the same router does connect).
Since I’m still within my 14-day return window I’m weighing the option of just returning this thing all together and wait it out. We’ll see what the genius at my store has to say about it tomorrow.
I've been watching this thread since I first got my new rMBP on Tuesday, and now it’s up to 1500+ views. Last years retina model and the 2013 airs all had widespread wifi issues in their beginning, so I think Apple still has some work to do getting this right.
After a typical frustrating experience with the Apple genius that refused to admit my computer was having any issues even though it was replicating right in front of their eyes (they wanted to take it overnight so they can run stress tests), I decided to just return it.
Will wait a few weeks and try again. Maybe with the luck of the draw I'll get one that works just fine. It's a great machine aside from the wifi issue.
I just received my second ordered rMBP13 2.6/8/256 and the machine is perfect. My first one that I ordered the day after launch had all kind of problems. As far as wifi I have a Netgear n router which maxes at 300mps and that is what the pro is getting. I ran the ping tests with no issues. The screen is perfect with no IR at all. The track pad is also perfect. I've decided to send it back though before the 14 days because this is way more than what I need and I don't use it away from the house. I will probably wait until the mini is upgraded and max out one of them form my home entertainment system. If I was still working and needed a laptop it would be the perfect machine.
so even though the ping test says that my ping is more erratic than a control mac mini,
using pintest.com tells me that my connection is very stable with low jitter.
I think the ping test utility might not be the best way to test the wifi on these new retinas.
My ping did become more stable one I was able to test the wifi on a 5 GHZ band. Here are hte results:
PING 172.30.64.1 (172.30.64.1): 56 data bytes
64 bytes from 172.30.64.1: icmp_seq=0 ttl=255 time=38.419 ms
64 bytes from 172.30.64.1: icmp_seq=1 ttl=255 time=0.991 ms
64 bytes from 172.30.64.1: icmp_seq=2 ttl=255 time=84.742 ms
64 bytes from 172.30.64.1: icmp_seq=3 ttl=255 time=1.117 ms
64 bytes from 172.30.64.1: icmp_seq=4 ttl=255 time=28.106 ms
64 bytes from 172.30.64.1: icmp_seq=5 ttl=255 time=0.926 ms
64 bytes from 172.30.64.1: icmp_seq=6 ttl=255 time=1.033 ms
64 bytes from 172.30.64.1: icmp_seq=7 ttl=255 time=1.098 ms
64 bytes from 172.30.64.1: icmp_seq=8 ttl=255 time=1.136 ms
64 bytes from 172.30.64.1: icmp_seq=9 ttl=255 time=1.215 ms
64 bytes from 172.30.64.1: icmp_seq=10 ttl=255 time=1.308 ms
64 bytes from 172.30.64.1: icmp_seq=11 ttl=255 time=1.386 ms
64 bytes from 172.30.64.1: icmp_seq=12 ttl=255 time=1.983 ms
64 bytes from 172.30.64.1: icmp_seq=13 ttl=255 time=1.493 ms
64 bytes from 172.30.64.1: icmp_seq=14 ttl=255 time=1.287 ms
64 bytes from 172.30.64.1: icmp_seq=15 ttl=255 time=1.169 ms
64 bytes from 172.30.64.1: icmp_seq=16 ttl=255 time=1.446 ms
64 bytes from 172.30.64.1: icmp_seq=17 ttl=255 time=23.049 ms
64 bytes from 172.30.64.1: icmp_seq=18 ttl=255 time=0.922 ms
64 bytes from 172.30.64.1: icmp_seq=19 ttl=255 time=1.256 ms
--- 172.30.64.1 ping statistics ---
20 packets transmitted, 20 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.922/9.704/84.742/20.150 ms
I have the same problem on my new MacBookPro.
I have compared the ping response time between this new MacBookPro and another MacBookPro (April 2011). I have done a ping to my home router and to my business router. Results :
- New Macbook = in average 70 ms
- Old MacBook = in average 4 ms !!!!
I think that there is a problem but where ??? hardware ? OS ? I don't know.
I have contacted this morning the Apple support but they don't want to consider this behaviour as a problem !!!
I have tested to change the wifi channel without effect.
Have you got another idea ?
I can say I'm having the same issue with my wifi on my MacBookPro11,3.
My specs for my WIFI:
Card Type: AirPort Extreme (0x14E4, 0x134)
Firmware Version: Broadcom BCM43xx 1.0 (220.127.116.11.47)
Issue connection to:
HY Mode: 802.11n
While changing the router settings may help some for others this is not a option. We can wait out a fix or return the new hardware to Apple which I have a feeling will mean trading one problem wifi system for another.
On a side not turning off WIFI and then turning it back on does work at times but I have found multiple instantces that I have had to restart my machine and the wifi will then connect to the network and work.
My late 2013 rMBP 13 Retina is having a similar issue.
I'm getting ping times all over the place. I don't have disconnects, and the connection feels stable though. Another thing is the Macbook only connects to my router at 802.11g speed, whole my old pc notebook connects at 802.11n speed to the same router.
Heres a sample of my pings:
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=49.568 ms
64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=72.572 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=95.061 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=19.590 ms
64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=42.143 ms
64 bytes from 192.168.0.1: icmp_seq=5 ttl=64 time=1.832 ms
64 bytes from 192.168.0.1: icmp_seq=6 ttl=64 time=2.919 ms
64 bytes from 192.168.0.1: icmp_seq=7 ttl=64 time=5.071 ms
64 bytes from 192.168.0.1: icmp_seq=8 ttl=64 time=31.293 ms
64 bytes from 192.168.0.1: icmp_seq=9 ttl=64 time=50.650 ms
--- 192.168.0.1 ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 1.832/37.070/95.061/29.598 ms
See the post above yours:
Note the discussion thread about failed ARP requests:
The posted solutions seem to be the remedy for most reporting this problem.