ShaneD90

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

My new MBPR's wifi is very slow and constantly drops the connection, although it is showing that it is always connected. If I restart the computer it fixes the problem for a little bit then it starts again. I have a 2012 Macbook Pro on the same network with no isseues, and I will have to use it sometimes just to be able to browse the web. Is there any way to fix the issue on the new Macbook?

MacBook Pro (Retina, 13-inch, Late 2013), OS X Mavericks (10.9)

Posted on Nov 7, 2013 7:38 AM

Close

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

  • All replies
  • Helpful answers

first Previous Page 41 of 54 last Next
  • by johnniecache,

    johnniecache johnniecache Apr 25, 2014 11:43 AM in response to 4rk
    Level 1 (5 points)
    Apr 25, 2014 11:43 AM in response to 4rk

    Good explanation. I can confirm that on 5GHz i am not having any disconnects and extreme slow-down at home. This is why i kept the machine in the end.

     

    However I have to add that even there the performance is still not as it should be and could be. See my earlier posts where on Mavericks I have measured less than 50% of the SMB2 transfer rates that i get with Windows 8.1. (same test setup)

  • by phoneuser,

    phoneuser phoneuser Apr 25, 2014 1:55 PM in response to ShaneD90
    Level 1 (5 points)
    Apr 25, 2014 1:55 PM in response to ShaneD90

    I think i spoke too soon ,  within 48 hours it happened again.  (actually it started when I put in charging with the external display, bluetooth mouse and keyboard). 

     

    BTW, my network is a dualband and i am connecting to the 5GHz.  I do not have any issues while connected.  but the wake from sleep issue is a shame for this beautiful machine.

     

    Also, i have trouble to login to my NAS made by LG from time to time.

  • by phoneuser,

    phoneuser phoneuser Apr 25, 2014 2:08 PM in response to ShaneD90
    Level 1 (5 points)
    Apr 25, 2014 2:08 PM in response to ShaneD90

    Here is something funny ..

     

    I did not turn the wifi off and on right away after the problem started... i happened to be busy with somethign else. and i found it eventually connects...after a long while though.

     

    equest timeout for icmp_seq 820

    Request timeout for icmp_seq 821

    Request timeout for icmp_seq 822

    Request timeout for icmp_seq 823

    Request timeout for icmp_seq 824

    64 bytes from 192.168.1.1: icmp_seq=673 ttl=64 time=152873.262 ms

    64 bytes from 192.168.1.1: icmp_seq=674 ttl=64 time=151872.520 ms

    64 bytes from 192.168.1.1: icmp_seq=675 ttl=64 time=150872.426 ms

    64 bytes from 192.168.1.1: icmp_seq=676 ttl=64 time=149871.617 ms

    64 bytes from 192.168.1.1: icmp_seq=677 ttl=64 time=148871.923 ms

    64 bytes from 192.168.1.1: icmp_seq=678 ttl=64 time=147871.209 ms

    64 bytes from 192.168.1.1: icmp_seq=679 ttl=64 time=146889.132 ms

    64 bytes from 192.168.1.1: icmp_seq=680 ttl=64 time=145888.390 ms

    64 bytes from 192.168.1.1: icmp_seq=681 ttl=64 time=144888.734 ms

    ....

     

    64 bytes from 192.168.1.1: icmp_seq=810 ttl=64 time=16232.699 ms

    64 bytes from 192.168.1.1: icmp_seq=811 ttl=64 time=15231.947 ms

    64 bytes from 192.168.1.1: icmp_seq=812 ttl=64 time=14231.200 ms

    64 bytes from 192.168.1.1: icmp_seq=813 ttl=64 time=13230.446 ms

    64 bytes from 192.168.1.1: icmp_seq=814 ttl=64 time=12229.680 ms

    64 bytes from 192.168.1.1: icmp_seq=815 ttl=64 time=11228.982 ms

    64 bytes from 192.168.1.1: icmp_seq=816 ttl=64 time=10228.268 ms

    64 bytes from 192.168.1.1: icmp_seq=817 ttl=64 time=9227.536 ms

    64 bytes from 192.168.1.1: icmp_seq=818 ttl=64 time=8226.785 ms

    64 bytes from 192.168.1.1: icmp_seq=819 ttl=64 time=7226.083 ms

    64 bytes from 192.168.1.1: icmp_seq=820 ttl=64 time=6225.337 ms

    64 bytes from 192.168.1.1: icmp_seq=821 ttl=64 time=5224.599 ms

    64 bytes from 192.168.1.1: icmp_seq=822 ttl=64 time=4223.849 ms

    64 bytes from 192.168.1.1: icmp_seq=823 ttl=64 time=3223.136 ms

    64 bytes from 192.168.1.1: icmp_seq=824 ttl=64 time=2222.391 ms

    64 bytes from 192.168.1.1: icmp_seq=825 ttl=64 time=1221.655 ms

    64 bytes from 192.168.1.1: icmp_seq=826 ttl=64 time=220.542 ms

    64 bytes from 192.168.1.1: icmp_seq=827 ttl=64 time=43.029 ms

    64 bytes from 192.168.1.1: icmp_seq=828 ttl=64 time=50.387 ms

    64 bytes from 192.168.1.1: icmp_seq=829 ttl=64 time=2.164 ms

    64 bytes from 192.168.1.1: icmp_seq=830 ttl=64 time=6.426 ms

    64 bytes from 192.168.1.1: icmp_seq=831 ttl=64 time=1.511 ms

    64 bytes from 192.168.1.1: icmp_seq=832 ttl=64 time=3.451 ms

    64 bytes from 192.168.1.1: icmp_seq=833 ttl=64 time=2.044 ms

  • by monolu,

    monolu monolu Apr 25, 2014 9:15 PM in response to monolu
    Level 1 (0 points)
    Apr 25, 2014 9:15 PM in response to monolu

    I've been having this issue here and there. What I finally decided to do is install SleepWatcher and have it turn Wifi off and on immediately after the system wakes up. So everytime it wakes up I see it turn off and back on, takes about 2 seconds, and it connects right away to my network.

     

    This will get me by until there is a fix supplied by Apple.

     

    Edit: I made a couple more tweeks and I now barely notice that I'm sometimes missing a connection and sometimes not. If anyone is interested in doing this I can send you a tutorial. You need to write some shell script and stuff. For now it's working great. No guarantees though. ;-)

  • by squelch99,

    squelch99 squelch99 Apr 26, 2014 3:19 AM in response to ShaneD90
    Level 1 (0 points)
    Apr 26, 2014 3:19 AM in response to ShaneD90

    This may be of help to someone...

     

    Having the same connection issue with a brand new 15'" late 2013 macbook pro and tried all of the router setting and other fixes in this thread on my Billion 7700n and was not able to connect to wifi at all - the router is only 3 feet from the macbook and an older unibody macbook 17" is working fine over wifi right next to it.

     

    I isolated the problem to a cheap generic usb cable extender and USB3 HD plugged into the right USB port that was interfering with the wifi signal, I plugged the HD directly into the USB port and Wifi connected straight away.

     

    On the left side of the macbook is a Thunderbolt to firewire adaptor and a Dell U2711 via display port and also acting as a 4 port hub.

     

    It might be worth unplugging and checking your USB peripherals for problems.

     

     

     

    Cheers

    Dave

  • by Grant Bennet-Alder,

    Grant Bennet-Alder Grant Bennet-Alder Apr 26, 2014 9:05 AM in response to squelch99
    Level 9 (61,180 points)
    Desktops
    Apr 26, 2014 9:05 AM in response to squelch99

    USB-3 signals are in about the same range as the 2.4GHz band of WiFi.

     

    Cables that came free in the box with a peripheral are often "lowest bidder" cables, and are not manufactured to high standards, especially regarding proper shielding of the cable.

  • by 4rk,

    4rk 4rk Apr 29, 2014 8:54 PM in response to phoneuser
    Level 1 (0 points)
    Apr 29, 2014 8:54 PM in response to phoneuser

    Hey so just to clarify my issues, they're only from waking, it doesn't resume sending packets even after 13h of trying (as mentioned before) unlike phoneuser's experience. I have tried a new location, deleting the plists, and zapping pram (that seemed to work once and once only), I'm using the late 2013 15" macbook pro retina model with the 802.11ac broadcom and 10.9.2. When it wakes the wifi is on, connected to the same (right) ssid, with the same IP the same netmask, but it can't even ping the first hop (the router itself).

     

    And my reason for updating is that I had previously written that getting a thunderbold gigabit ethernet adapter would be my way to work around this... well one amazon prime delivery later and behold: the late 2013 15" macbook pro retina model has a problem using the adapter when it's woken from sleep.

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

     

    True story. So it's probably not worth your extra $30+tax to Apple for removing the port from your slim slim machine.

     

    The fix regarding the dhcp lease after switching ipv6 to link-local only works (so far). Not sure if it will work for the wifi.

     

    Interfaces:

    en0:

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

      Firmware Version:          Broadcom BCM43xx 1.0 (6.30.223.154.63)

      MAC Address:          60:03:08:a6:8c:3e

    ...

    Apple 57762-A0:

      Name:          ethernet

      Type:          Ethernet Controller

      Bus:          PCI

      Slot:          Thunderbolt Slot 1@195,0,0

    ...

      BSD name:          en3

      Kext name:          AppleBCM5701Ethernet.kext

      Firmware version:          57762-a1.10, 0x5397cc35

    ...

      Version:          3.8.1b2

     

    In my new location I changed the order of devices and removed/disabled some unlikely ones. Again this didn't fix it.

     

    Home:

     

      Active Location:          Yes

      Services:

    Wi-Fi:

      Type:          IEEE80211

      BSD Device Name:          en0

      Hardware (MAC) Address:          60:03:08:a6:8c:3e

      IPv4:

      Configuration Method:          DHCP

      IPv6:

      Configuration Method:          Link Local

      Proxies:

      Exceptions List:          *.local, 169.254/16

      FTP Passive Mode:          Yes

      IEEE80211:

      Join Mode:          Automatic

      PowerEnabled:          0

      RememberJoinedNetworks:          1

      RequireAdminIBSS:          0

      RequireAdminNetworkChange:          0

      RequireAdminPowerToggle:          0

    Thunderbolt Bridge:

      Type:          Bridge

      BSD Device Name:          bridge0

      IPv4:

      Configuration Method:          DHCP

      IPv6:

      Configuration Method:          Automatic

      Proxies:

      Exceptions List:          *.local, 169.254/16

      FTP Passive Mode:          Yes

    Bluetooth DUN:

      Type:          PPP

      IPv4:

      Configuration Method:          PPP

      IPv6:

      Configuration Method:          Automatic

      Proxies:

      FTP Passive Mode:          Yes

      PPP:

      ACSP Enabled:          No

      Display Terminal Window:          No

      Redial Count:          1

      Redial Enabled:          Yes

      Redial Interval:          5

      Use Terminal Script:          No

      Dial on Demand:          No

      Disconnect on Fast User Switch:          Yes

      Disconnect on Idle:          Yes

      Disconnect on Idle Timer:          600

      Disconnect on Logout:          Yes

      Disconnect on Sleep:          Yes

      Idle Reminder:          No

      Idle Reminder Time:          1800

      IPCP Compression VJ:          Yes

      LCP Echo Enabled:          No

      LCP Echo Failure:          4

      LCP Echo Interval:          10

      Log File:          /var/log/ppp.log

      Verbose Logging:          No

    Thunderbolt Ethernet:

      Type:          Ethernet

      BSD Device Name:          en3

      Hardware (MAC) Address:          68:5b:35:c8:ec:6e

      IPv4:

      Configuration Method:          DHCP

      IPv6:

      Configuration Method:          Automatic

      Proxies:

      Exceptions List:          *.local, 169.254/16

      FTP Passive Mode:          Yes

  • by BTchang,

    BTchang BTchang May 1, 2014 3:54 AM in response to ShaneD90
    Level 1 (0 points)
    May 1, 2014 3:54 AM in response to ShaneD90

    I just got my Macbook Pro back after a repair session with Apple, the solution for the problem is that you need at least 20% free on you hard disk for Mac OSX to work well. It is really non-realistic solution because 20% is a lot of space of you only have 256 GB.

     

    But my wifi issue and the hopefuly my kernel panics are gone, if I ping now I get this:

     

    Schermafbeelding 2014-05-01 om 12.54.15.png

  • by 4rk,

    4rk 4rk May 1, 2014 1:23 PM in response to BTchang
    Level 1 (0 points)
    May 1, 2014 1:23 PM in response to BTchang

    Well I've got a 500GB ssd and I have 405GB free, so 20% free has always been respected and doesn't seem related to my wifi problems.

  • by bkang97,

    bkang97 bkang97 May 1, 2014 8:16 PM in response to ShaneD90
    Level 1 (0 points)
    May 1, 2014 8:16 PM in response to ShaneD90

    I have a fix. Since this fix has been running, no timeouts for the past 2 days. To put this in perpective, just before I ran this fix, every hour or so, my internet connection would drop. It's a simple but effective applescript that I compiled into an app. The applescript is this:

    tell application "Terminal"

    activate

              do script "ping -i 0.2 `netstat -nr | grep -m 1 '^default' | awk '{print $2;}'`"

              tell application "Finder" to set visible of process "Terminal" to false

    end tell

     

    Here's the link of the compiled applescript for you lazy people out there:

    https://app.box.com/s/mjlp18hf6jj87jwl5961

     

    It might be annoying to always have Terminal open, but it's worth it.

     

    By the way, if any of you more advanced coders are nice enough to make the UI a bit better and like hide the dock icon of terminal while the script is running, I would be extremely grateful.

     

    Reply your results please!

  • by monolu,

    monolu monolu May 1, 2014 8:42 PM in response to bkang97
    Level 1 (0 points)
    May 1, 2014 8:42 PM in response to bkang97

    I created an automator app with the code for you. It'll keep it running without having terminal open and a gear should appear in the menu bar from where you can close the app.

     

    I don't need the script since my conection stays on but I figured I'd wrap it for you this way. Hopefully it works for you ;-)

     

    https://www.dropbox.com/sh/rzgv6hxjzog4ehd/_neQOEL4Gh

  • by bkang97,

    bkang97 bkang97 May 1, 2014 9:01 PM in response to bkang97
    Level 1 (0 points)
    May 1, 2014 9:01 PM in response to bkang97

    Thanks!

    Here's the link to the app with monolu's automator workflow:

    https://app.box.com/s/za5lc30dgp2d5f04hlk8

     

    Edit: wait a few seconds after you open the app for automator to initialize. look for the spinning gear at the top in the menu bar like monolu said

  • by Dimor,

    Dimor Dimor May 2, 2014 2:33 AM in response to ShaneD90
    Level 1 (0 points)
    May 2, 2014 2:33 AM in response to ShaneD90

    i just got a new MBP retina 13' a few days ago and i was having similar WIFI issues. after trying almost all of the suggestions in this thread with no success, i have tried to change the authentication method from WPA2 to WPA, and i think that did the trick for me. i haven't got the chance to test it for too long yet, but it seems like it's working quite well.

     

    currently my router's wifi settings are:

    channel: 6

    mode: 11n only

    channel width 40mhz

    max tx rate: 300mbps

     

    hope this helps anyone.

  • by Grant Bennet-Alder,

    Grant Bennet-Alder Grant Bennet-Alder May 2, 2014 9:26 AM in response to Dimor
    Level 9 (61,180 points)
    Desktops
    May 2, 2014 9:26 AM in response to Dimor

    1000px-NonOverlappingChannels2.4GHz802.11-en.svg.png

     

    chart courtesy wikipedia

     

    Using a 40MHz n-mode channel in the 2.4GHz band gives you a signal shape like the third chart above, that takes up nearly half the spectrum available. If you have ANY neighbors in range, they are likley to use a Channel that overlaps Channel 6, and causes you interference. Did the Router choose Channel 6 on "automatic"? If not, it  would be better to let the Router choose the Channel, or use Channel 1 or 11.

first Previous Page 41 of 54 last Next