-
All replies
-
Helpful answers
-
Dec 16, 2013 2:44 PM in response to Petolsby Crematum,Problem still persists after Mavericks update. Pings are "ping ponging" all over the place. My thunderbolt ethernet adapter has perfect ping, but AC wireless connecting to a new Apple AC router is all over the place.
-
Dec 17, 2013 5:58 AM in response to ShaneD90by flash17,Hi all,
it seems I have been able to solve my WiFi problem with Late 2013 Macbook Pro 13 Retina.
In my case, it was not due to Wi-Fi power saving features, pings etc. but to a strange interference between Bluetooth and Wi-Fi.
I noticed that because casually I turned off my Bluetooth and istantly Internet became faster than light, when it was stucked only a few seconds before.
To solve my issue once and for all, I followed the instructions on another Apple forum (sorry but I cannot find the link again):
- Go to Bluetooth preferences
- Click on Advanced button
- Disable all the options there (all three of them)
- Click OK.
Done. Hope this helps someone else, for me it was a life-saver!
-
Dec 17, 2013 6:43 AM in response to ShaneD90by aphexairlines,For me changing bluetooth settings hasn't had any effect, but changing my router to use channel 13 on the 2.4ghz band did help and I'm not seeing the sporadic periods of high latency+drops anymore.
PHY mode: 802.11n
channel: 13 (2.4GHz)
security: WPA personal
RSSI: -43
transmit rate: 130
MCS index: 15
163 packets transmitted, 163 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.671/1.467/22.427/2.589 ms
-
Dec 17, 2013 7:22 AM in response to aphexairlinesby aphexairlines,Sorry, I spoke too soon: 40 minutes later, I do see the issue again regardless of channel.
-
Dec 17, 2013 4:50 PM in response to ShaneD90by Erickton,I had the same problem after upgrading to Mavericks, diggin in another thread i found this:
https://github.com/MacMiniVault/Mac-Scripts/blob/master/unicastarp/unicastarp-RE ADME.md
That amazing work by MacMiniVault team saved my day before I went crazy, please help the community spreading the voice...
-
Dec 18, 2013 8:21 AM in response to MadbeaverDKby manstrup,"
I'm using a Netgear CG3000 from my ISP, who has locked it down with an outdated formware.
It's running 802.11 b/g/n, 40 Mhz, auto channel. I've tried cycling through all the channels manually, but untill now only 802.11g on the rMBP.
Just now I've tried enabling WMM in the router as per mshybut's post. Instantly the rMBP connected at 802.11n. Thanks dude."
I have the same Router, an your post helped. I enabled WMM, and now i run on 802.11n - Thanks
-
Dec 18, 2013 5:43 PM in response to ShaneD90by santiagoIT,I am having the same EXTREMELY ANNOYING issue. My brand new rMBP has extremely slow internet connections. Pinging the gateway is extremely bad:
4 bytes from 10.19.2.1: icmp_seq=3153 ttl=64 time=75.814 ms
64 bytes from 10.19.2.1: icmp_seq=3154 ttl=64 time=95.765 ms
64 bytes from 10.19.2.1: icmp_seq=3155 ttl=64 time=16.187 ms
64 bytes from 10.19.2.1: icmp_seq=3156 ttl=64 time=39.284 ms
64 bytes from 10.19.2.1: icmp_seq=3157 ttl=64 time=65.887 ms
64 bytes from 10.19.2.1: icmp_seq=3158 ttl=64 time=85.791 ms
64 bytes from 10.19.2.1: icmp_seq=3159 ttl=64 time=6.243 ms
64 bytes from 10.19.2.1: icmp_seq=3160 ttl=64 time=30.132 ms
64 bytes from 10.19.2.1: icmp_seq=3161 ttl=64 time=54.856 ms
64 bytes from 10.19.2.1: icmp_seq=3162 ttl=64 time=74.816 ms
64 bytes from 10.19.2.1: icmp_seq=3163 ttl=64 time=1.655 ms
64 bytes from 10.19.2.1: icmp_seq=3164 ttl=64 time=18.232 ms
64 bytes from 10.19.2.1: icmp_seq=3165 ttl=64 time=43.941 ms
64 bytes from 10.19.2.1: icmp_seq=3166 ttl=64 time=63.792 ms
64 bytes from 10.19.2.1: icmp_seq=3167 ttl=64 time=88.556 ms
64 bytes from 10.19.2.1: icmp_seq=3168 ttl=64 time=9.188 ms
64 bytes from 10.19.2.1: icmp_seq=3169 ttl=64 time=32.930 ms
64 bytes from 10.19.2.1: icmp_seq=3170 ttl=64 time=53.085 ms
64 bytes from 10.19.2.1: icmp_seq=3171 ttl=64 time=77.795 ms
I am running all the latest updates.I turned off bluetooth. If I reboot the router, things get better for a while.
My iPhone/iPad connected to the same wireless router work just fine. I will test with my old 17" MBP tomorrow...
So FRUSTRATING....
Is there a known solution to this problem by now?
-
Dec 19, 2013 7:51 AM in response to santiagoITby waitingegg,I am also the same situation , I have applied for a new machine to replace .
macbook pro retina 15 / cpu 2.0 ram 16GB , Taiwan
-
Dec 19, 2013 8:20 AM in response to waitingeggby Petols,Would be great if Apple stopped wasting their customers time with useless replacements.. but they don't even read their own support forums.
-
Dec 21, 2013 10:53 AM in response to ShaneD90by dbrm.krr,I was turned off the Apple Magic Mouse and my problems with slow wifi connection will be solved %( MBPro13 late 2013
Apple please, do it something with it!
-
Dec 22, 2013 3:39 AM in response to ShaneD90by johnniecache,same big problems with 13" MBPr late 2013 here :-(
Heres my ping:
Ping has started…
PING 192.168.2.1 (192.168.2.1): 56 data bytes
64 bytes from 192.168.2.1: icmp_seq=0 ttl=64 time=58.553 ms
64 bytes from 192.168.2.1: icmp_seq=1 ttl=64 time=34.357 ms
64 bytes from 192.168.2.1: icmp_seq=2 ttl=64 time=52.297 ms
64 bytes from 192.168.2.1: icmp_seq=3 ttl=64 time=45.963 ms
64 bytes from 192.168.2.1: icmp_seq=4 ttl=64 time=7.712 ms
64 bytes from 192.168.2.1: icmp_seq=5 ttl=64 time=3.931 ms
64 bytes from 192.168.2.1: icmp_seq=6 ttl=64 time=42.719 ms
64 bytes from 192.168.2.1: icmp_seq=7 ttl=64 time=219.384 ms
64 bytes from 192.168.2.1: icmp_seq=8 ttl=64 time=194.585 ms
64 bytes from 192.168.2.1: icmp_seq=9 ttl=64 time=110.721 ms
--- 192.168.2.1 ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 3.931/77.022/219.384/70.911 ms
Actually i have already returned an Airport Extreme Router, which was probably perfectly good. I did not suspect the MacBook being the culprit, especially since i have never had wifi issues with any other notebook or router. A bit disappointing apple..
-
Dec 22, 2013 3:50 AM in response to ShaneD90by timmyj,should try using a HD HomeRun streaming live TV on Late 2013 MacBook Pro, stream keeps stalling every few minutes when the latency spikes kick in
even just loading websites, the throughput is great but simple network activites like ssh and just initial page loading seem to incur huge latencies using both official AirPort Extreme 802.11ac and other 802.11n routers
-
Dec 22, 2013 6:58 AM in response to ShaneD90by johnniecache,ok, i just read the complete thread and figured out that a normal ping is not representative on the MBPr models. The -i 0.2 ping gets me good results. Also i am not seeing any lost packets so far.
However, loading websites is slow. I have never had such slow WiFi with any other notebook, sometimes it takes several seconds until a page loads.
-
Dec 22, 2013 1:16 PM in response to ShaneD90by johnniecache,now i left the ping -i 0.2 running in the background, turns out i am getting lots of "request timeouts" in between the successful pings. Here is an example:
64 bytes from 192.168.2.1: icmp_seq=9622 ttl=64 time=4.081 ms
64 bytes from 192.168.2.1: icmp_seq=9623 ttl=64 time=4.845 ms
Request timeout for icmp_seq 9624
Request timeout for icmp_seq 9625
64 bytes from 192.168.2.1: icmp_seq=9626 ttl=64 time=4.525 ms
64 bytes from 192.168.2.1: icmp_seq=9627 ttl=64 time=4.915 ms
Request timeout for icmp_seq 9628
64 bytes from 192.168.2.1: icmp_seq=9629 ttl=64 time=4.137 ms
64 bytes from 192.168.2.1: icmp_seq=9630 ttl=64 time=4.050 ms
64 bytes from 192.168.2.1: icmp_seq=9631 ttl=64 time=4.383 ms
64 bytes from 192.168.2.1: icmp_seq=9632 ttl=64 time=5.648 ms
64 bytes from 192.168.2.1: icmp_seq=9633 ttl=64 time=5.222 ms
Request timeout for icmp_seq 9634
Request timeout for icmp_seq 9635
Request timeout for icmp_seq 9636
Request timeout for icmp_seq 9637
64 bytes from 192.168.2.1: icmp_seq=9638 ttl=64 time=4.450 ms
Request timeout for icmp_seq 9639
Request timeout for icmp_seq 9640
Request timeout for icmp_seq 9641
Request timeout for icmp_seq 9642
Request timeout for icmp_seq 9643
Request timeout for icmp_seq 9644
Request timeout for icmp_seq 9645
Request timeout for icmp_seq 9646
64 bytes from 192.168.2.1: icmp_seq=9647 ttl=64 time=12.563 ms
Request timeout for icmp_seq 9648
64 bytes from 192.168.2.1: icmp_seq=9649 ttl=64 time=3.607 ms
64 bytes from 192.168.2.1: icmp_seq=9650 ttl=64 time=5.348 ms
64 bytes from 192.168.2.1: icmp_seq=9651 ttl=64 time=3.895 ms
Eventualy it completely looses the connection, which can only be re-established by turning off wifi and then reconnecting :-(
-
Dec 27, 2013 4:11 PM in response to ShaneD90by suedkaliber,Problem still exists with the latest 10.9.1 special release for the new retina MBPs.
My problem is, that i can't connect to fritzbox 7330 sl and a few other APs after resuming from sleep.
Only a reboot helps.