Late 2013 Macbook Pro Retina 13'' Wifi Issues

Hello,

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 ?

Regards

Mathieu

I changed the channel turned off wireless a/n nothing seems to work. I just purchased this last night and it is driving me crazy. Pings are all over the place. If I ping the router I get approximately 160ms, but if I ping my router with my 2012 MBA I get approximately 3ms.

I can say I'm having the same issue with my wifi on my MacBookPro11,3.

My specs for my WIFI:

en0:

Card Type: AirPort Extreme (0x14E4, 0x134)

Firmware Version: Broadcom BCM43xx 1.0 (6.30.223.154.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.

Note the discussion thread about failed ARP requests:

https://discussions.apple.com/thread/5483424?tstart=0

The posted solutions seem to be the remedy for most reporting this problem.

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:

Mactotum

Note the discussion thread about failed ARP requests:

https://discussions.apple.com/thread/5483424?tstart=0

The posted solutions seem to be the remedy for most reporting this problem.

I also has this prolbem. My mbp is Me294. the ping value between 1 to 200ms.

Have an issue with mine as well- 13" rMBP with 8GB/256GB. I've switched my Apple Airport Express from 802.11n to 802.11b/g and that has done away with Wi-Fi issues at home but obviously not the best solution as I can't go about changing router configs everywhere 🙂

Please fix this Apple.

My replacement device for the rMBP 15" arrived to day. I haven't yet unpacked it and after reading your comments I somehow doubt that the problem will be fixed.

Sounds like the same problem with the 2013 Macbook air. Several reported what was likely a wifi card/antenna problem (dropping wifi constantly) and then Apple modified the wifi driver which starting causing ping latency. My 2013 MBA was working fine until Apple borked up the wifi driver, I rolled back to the original driver and the pings went back to normal

So in summary, if your Mac is dropping the wifi connection (and you have other devices that work fine) it's very likely a hardware problem. The ping latency is a wifi driver problem. Not sure if the Macbook Pro can use the original driver from the MBA or not. I would only experiment with it on a bootable thumb drive.

https://discussions.apple.com/thread/5100655?start=1470&tstart=0

I got my second 13rMBP 8/2.6/256 Friday and I have had no problems with wifi from my Netgear N router.

Its pulling the full 300 mps with out any drops. I would say you people are having hardware problems and you should probably replace your device.

I'm having the same problem with a similar machine, new 13" rMBP 2.4/256GB/8GB RAM. It will only connect to my router via 802.11g whereas my 2011 11" MBA right next to it connects at 802.11n. The transmit rates on my MBA are sometimes as high as 10x those of the rMBP.

It's most noticeable while using AirPlay where the rMBP will constantly stutter both during audio only and video, as well as extending or mirroring the display.

I'm anticipating a hardware swap and have already contacted chat and phone support. I have an Apple Store appointment set up for Saturday.

Disappointing to have a new machine be faulty, especially when my old MBA is outperforming it.

mshybut,

what wireless router are you on ? Is it a 11ac router ? What RSSI are you at ? Use the built in Wireless Diagnostics tool to lookup your RSSI and Signal Quality.

http://support.apple.com/kb/HT5606

I'm on a Linksys WRT310N, not an AC router. My RSSI is -56 on my rMBP with a transmit rate of 54 on 802.11g. My MBA is at RSSI -49, transmit rate 104 on 802.11n.

I found something interesting. My 15" late 2013 MBPR also suffers from network issues, namely latency problems on pings.

Ping to my router:

PING 10.238.238.229 (10.238.238.229): 56 data bytes

64 bytes from 10.238.238.229: icmp_seq=0 ttl=64 time=24.826 ms

64 bytes from 10.238.238.229: icmp_seq=1 ttl=64 time=46.707 ms

64 bytes from 10.238.238.229: icmp_seq=2 ttl=64 time=2.371 ms

64 bytes from 10.238.238.229: icmp_seq=3 ttl=64 time=1.521 ms

64 bytes from 10.238.238.229: icmp_seq=4 ttl=64 time=12.927 ms

64 bytes from 10.238.238.229: icmp_seq=5 ttl=64 time=36.186 ms

64 bytes from 10.238.238.229: icmp_seq=6 ttl=64 time=59.893 ms

64 bytes from 10.238.238.229: icmp_seq=7 ttl=64 time=1.510 ms

64 bytes from 10.238.238.229: icmp_seq=8 ttl=64 time=1.587 ms

64 bytes from 10.238.238.229: icmp_seq=9 ttl=64 time=0.876 ms

64 bytes from 10.238.238.229: icmp_seq=10 ttl=64 time=47.706 ms

64 bytes from 10.238.238.229: icmp_seq=11 ttl=64 time=1.751 ms

64 bytes from 10.238.238.229: icmp_seq=12 ttl=64 time=94.634 ms

However, if I start a download, it starts working perfect:

# I start downloading ubuntu disk image here

[~/Desktop]$ axel http://archive.ubuntu.com/ubuntu/.../mini.iso >/dev/null &

# Then ping, everything seems ok

[~/Desktop]$ ping 10.238.238.229

PING 10.238.238.229 (10.238.238.229): 56 data bytes

64 bytes from 10.238.238.229: icmp_seq=0 ttl=64 time=1.159 ms

64 bytes from 10.238.238.229: icmp_seq=1 ttl=64 time=1.464 ms

64 bytes from 10.238.238.229: icmp_seq=2 ttl=64 time=1.182 ms

64 bytes from 10.238.238.229: icmp_seq=3 ttl=64 time=0.984 ms

64 bytes from 10.238.238.229: icmp_seq=4 ttl=64 time=1.133 ms

64 bytes from 10.238.238.229: icmp_seq=5 ttl=64 time=1.129 ms

64 bytes from 10.238.238.229: icmp_seq=6 ttl=64 time=1.776 ms

64 bytes from 10.238.238.229: icmp_seq=7 ttl=64 time=1.457 ms

64 bytes from 10.238.238.229: icmp_seq=8 ttl=64 time=1.844 ms

64 bytes from 10.238.238.229: icmp_seq=9 ttl=64 time=1.725 ms

64 bytes from 10.238.238.229: icmp_seq=10 ttl=64 time=1.180 ms

64 bytes from 10.238.238.229: icmp_seq=11 ttl=64 time=2.507 ms

64 bytes from 10.238.238.229: icmp_seq=12 ttl=64 time=1.306 ms

64 bytes from 10.238.238.229: icmp_seq=13 ttl=64 time=1.497 ms

64 bytes from 10.238.238.229: icmp_seq=14 ttl=64 time=0.920 ms

64 bytes from 10.238.238.229: icmp_seq=15 ttl=64 time=0.872 ms

64 bytes from 10.238.238.229: icmp_seq=16 ttl=64 time=1.097 ms

64 bytes from 10.238.238.229: icmp_seq=17 ttl=64 time=1.213 ms

64 bytes from 10.238.238.229: icmp_seq=18 ttl=64 time=1.270 ms

64 bytes from 10.238.238.229: icmp_seq=19 ttl=64 time=1.361 ms

64 bytes from 10.238.238.229: icmp_seq=20 ttl=64 time=1.538 ms

64 bytes from 10.238.238.229: icmp_seq=21 ttl=64 time=1.611 ms

# Download finished at the background

[1] + 743 done axel > /dev/null

# Latencies go haywire again

64 bytes from 10.238.238.229: icmp_seq=22 ttl=64 time=1.090 ms

64 bytes from 10.238.238.229: icmp_seq=23 ttl=64 time=1.824 ms

64 bytes from 10.238.238.229: icmp_seq=24 ttl=64 time=44.799 ms

64 bytes from 10.238.238.229: icmp_seq=25 ttl=64 time=44.931 ms

64 bytes from 10.238.238.229: icmp_seq=26 ttl=64 time=44.664 ms

I think it might be abour power consumption. The device goes into low performance state when you are not taxing it. Ping itself is not taxing enough. I thought maybe there is a delay or something that kicks in. If I make ping run faster it seems to be ok too.

$ ping -i 0.1 10.238.238.229

PING 10.238.238.229 (10.238.238.229): 56 data bytes

64 bytes from 10.238.238.229: icmp_seq=0 ttl=64 time=1.320 ms

64 bytes from 10.238.238.229: icmp_seq=1 ttl=64 time=1.317 ms

64 bytes from 10.238.238.229: icmp_seq=2 ttl=64 time=0.883 ms

64 bytes from 10.238.238.229: icmp_seq=3 ttl=64 time=1.358 ms

64 bytes from 10.238.238.229: icmp_seq=4 ttl=64 time=1.001 ms

64 bytes from 10.238.238.229: icmp_seq=5 ttl=64 time=1.768 ms

64 bytes from 10.238.238.229: icmp_seq=6 ttl=64 time=1.708 ms

64 bytes from 10.238.238.229: icmp_seq=7 ttl=64 time=1.444 ms

64 bytes from 10.238.238.229: icmp_seq=8 ttl=64 time=1.204 ms

64 bytes from 10.238.238.229: icmp_seq=9 ttl=64 time=1.401 ms

64 bytes from 10.238.238.229: icmp_seq=10 ttl=64 time=1.121 ms

64 bytes from 10.238.238.229: icmp_seq=11 ttl=64 time=1.500 ms

64 bytes from 10.238.238.229: icmp_seq=12 ttl=64 time=1.262 ms

64 bytes from 10.238.238.229: icmp_seq=13 ttl=64 time=1.538 ms

64 bytes from 10.238.238.229: icmp_seq=14 ttl=64 time=2.617 ms

64 bytes from 10.238.238.229: icmp_seq=15 ttl=64 time=3.567 ms

Can anyone confirm if this is the case with your setup too?