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 52 of 54 last Next
  • by Csound1,

    Csound1 Csound1 Oct 17, 2014 2:54 AM in response to chotty1
    Level 9 (50,786 points)
    Desktops
    Oct 17, 2014 2:54 AM in response to chotty1

    chotty1 wrote:

     

    I can confirm this issue is 100% FIXED (MacBook Pro 13" late 2013) with today's release of OS X Yosemite 10.10.

    Really, a one day test is enough to convince you of a 100% cure?

     

    Good luck.

  • by chotty1,

    chotty1 chotty1 Oct 17, 2014 5:59 AM in response to Csound1
    Level 1 (1 points)
    Oct 17, 2014 5:59 AM in response to Csound1

    I've been beta-testing 10.10 also. It fixes the problem. Wifi is solid bars & working the instant you lift the screen... try it, Sparky.

  • by Csound1,

    Csound1 Csound1 Oct 17, 2014 6:02 AM in response to chotty1
    Level 9 (50,786 points)
    Desktops
    Oct 17, 2014 6:02 AM in response to chotty1

     

  • by doublelime,

    doublelime doublelime Oct 17, 2014 10:43 AM in response to chotty1
    Level 1 (0 points)
    Oct 17, 2014 10:43 AM in response to chotty1

    Do not lie, this issue is not fixed at all Yosemite did not address any wifi problems. My mac stays connected to wifi but disconnects from the internet. Late 2014 macbook pro retina. Apple doesn't care about our problems.

  • by chotty1,

    chotty1 chotty1 Oct 17, 2014 12:01 PM in response to doublelime
    Level 1 (1 points)
    Oct 17, 2014 12:01 PM in response to doublelime

    I am NOT "lying". it fixed MY macBook Pro 2013 WiFi wake from sleep issue entirely , Idjit.

  • by gympro1807,

    gympro1807 gympro1807 Oct 26, 2014 3:00 AM in response to doublelime
    Level 1 (0 points)
    Oct 26, 2014 3:00 AM in response to doublelime

    I had same problem with my iMac 27 (Late 2012), and the solution was to manually enter googles DNS servers into the wifi configuration, been working ever since.  They are 8.8.8.8, and 8.8.4.4, when you enter these they override the dhcp dns server.

  • by gympro1807,

    gympro1807 gympro1807 Oct 26, 2014 3:02 AM in response to ShaneD90
    Level 1 (0 points)
    Oct 26, 2014 3:02 AM in response to ShaneD90

    I had same problem with my iMac 27 (Late 2012), and the solution was to manually enter googles DNS servers into the wifi configuration, been working ever since.  They are 8.8.8.8, and 8.8.4.4, when you enter these they override the dhcp dns server.

  • by kevin.gc,

    kevin.gc kevin.gc Nov 13, 2014 11:07 PM in response to gympro1807
    Level 1 (0 points)
    Nov 13, 2014 11:07 PM in response to gympro1807

    This app may help. It was made specifically for the MacBook Pro Wifi issue, but it may work on iMacs as well. PingFixer

     

    https://itunes.apple.com/us/app/pingfixer/id808479246?mt=12

  • by Erik_Huber,

    Erik_Huber Erik_Huber Nov 18, 2014 11:26 PM in response to Muhammad J. Kamal
    Level 1 (0 points)
    Nov 18, 2014 11:26 PM in response to Muhammad J. Kamal

    I wanted to flag up this post, as it helped me resolve a wi-fi connectivity issue with a 2011 Macbook Air that recently came back from Apple with a new I/O board installed. The MBA would show as "connected" to our home wi-fi network (Apple Time Capsule operating in bridge mode) but internet connectivity was excruciatingly slow, with web pages timing out and/or hanging up completely. I tried several different troubleshooting tips that I'd read elsewhere (eg. deleting preferences, turning off Bluetooth, deleting/recreating network locations, renewing DHCP lease, etc) but nothing worked until I followed the instructions at the page linked below:

     

    http://www.s0hel.com/blog/401/fixed-slow-wifi-issue-with-new-macbook-pro/

     

    Changing the wireless channel to ch. 6 worked for me (same as described in the article).

     

    After several days of frustration and multiple AppleCare phone calls & visits to the Apple Store, this was an extremely welcome discovery. Thanks!!!

  • by Alex Hoven,

    Alex Hoven Alex Hoven Nov 21, 2014 1:02 PM in response to ShaneD90
    Level 1 (0 points)
    Nov 21, 2014 1:02 PM in response to ShaneD90

    I had dropped packages as well on my MBP 15" late 2013

     

    Deleting and creating a new Wi-fi service under a different name worked for me.

     

     

    1. Creating a New Wi-Fi Service (this solution worked for me!)
      • Copy and paste these instructions, because you'll be disconnected from the Internet and you'll need to reboot.
      • Go into your Network Preferences > Select Wi-Fi Service (in the list in the left column) > Click on the options (cog icon) > Select "Make Service Inactive" > Select Apply.
      • Select the same Wi-Fi Service > Delete It ( – ). Reboot.
      • Return to Network Preferences > Create a New Service ( + ).
      • Inside the prompt select Wi-Fi under Interface, name the Service Name something other than Wi-Fi. (I named mine Wi-Fi2. Apparently if you retain the previous Wi-Fi name the WiFi dropping will return on reboot.) > Click Create.
      • Click Apply.
    2. Delete and Reconnect to your Preferred Network
      • Go into your Network Preferences > Advanced > Select Your WiFi Network and Delete It ( – ). Reconnect to it.
    3. Delete Bluetooth.plist
      • Finder > Go (on your toolbar) > Computer > HD > Library > Preferences > Delete your Bluetooth.plist. Reboot
  • by lousyformac,

    lousyformac lousyformac Nov 29, 2014 12:27 PM in response to ShaneD90
    Level 1 (0 points)
    Nov 29, 2014 12:27 PM in response to ShaneD90

    My Retina MPB is just a few months old.  You would think they would stop selling them with this problem, or fix it before the sell them. 

     

    For a company that charges an arm and a leg for a computer you expect the computer to be better than anything else out there.  I have no wifi problems from any of my old MAC or PCs that cost less than half the price.

     

    Sure, they'll probably "allow" me to have if fixed for free, but I'll have to take time out of my schedule to drive an hour to an Apple store, wait there for a "genius" and then be without a computer for who knows how long while it gets fixed and then make the hour drive (2 hours both ways) to go pick it up.  All for "free" because they are such a great company.

  • by pixeldennisty,

    pixeldennisty pixeldennisty Dec 9, 2014 4:05 AM in response to lousyformac
    Level 1 (4 points)
    iPhone
    Dec 9, 2014 4:05 AM in response to lousyformac

    wow so this still has not been fixed?

  • by 4rk,

    4rk 4rk Dec 13, 2014 11:08 PM in response to chotty1
    Level 1 (0 points)
    Dec 13, 2014 11:08 PM in response to chotty1

    Guys I'm circling back on the Stuck on Wake Wifi Issue I was talking about with you all.

     

    It's tough to just tell people hey version blah fixed it for everyone! When it's really just your own experience of that problem being gone now for you. I'd like to chime in to say I also experience the problem with Yosemite.

     

    I ended up updating my Macbook Pro 15" Retina to Yosemite 10.10.1 with a totally clean re-formatted install. And I still saw the issue. Then I also bought Mac Mini (Late 2014) which ships with Yosemite 10.10.0, updated to 10.10.1 on first boot, and again had the same issue for weeks.

    I started using my 90 days of Apple Care. After about 5 calls to Apple over 3 days with the same case number (Apple Care never starts with a prompt for following up on an existing case, it's very frustrating) I was asked if I'd like to be forwarded to a "specialist" (taking a good 45 minutes after the normal 15 minute wait time, but you have to hang in there that specialist will give you a line for direct contact to follow up with the same person...) who basically walked me through what some people here already advocated and I'd previously tried unsuccessfully, only it's been working for 3-4 days straight so far. The first things tried were to change security from WPA/WPA2 PSK to just WPA2 PSK. Another was to turn off the automatic channel selection and stick to just a known channel. Neither of these on their own worked, but they may have contributed to the success of the next step.

    It was to make a new network location, one that's basically equivalent to the default "Automatic" location. He was very careful however to instruct me to turn off the wifi first before doing that... that seems to be an important detail... and delete the key for the Airport password in the keychain (oddly I didn't have one). Once the new location is created it mysteriously turned on wifi again without me doing so, which seemed to take him a bit by surprise. Then we added the one and only access point I have at home and it's been working unlike when I feel I did exactly the same thing with the Automatic location. It seems to indicate that there's something borked in the prefs for the network location that they haven't yet correctly fixed in a true update. I couldn't say what though. My worry of course is that eventually this location's prefs will become borked, leading me to have to repeat the steps (and hope they take). I'd so very much prefer a "stops borking wifi wakeup" fix.

  • by bpka,

    bpka bpka Dec 21, 2014 2:40 AM in response to 4rk
    Level 1 (0 points)
    Dec 21, 2014 2:40 AM in response to 4rk

    I have the same problem (missing wireless connection or take time to get wireless connection) after sleep. In both my macbook air and macbook pro retina. I am using the latest OS X Yosemite.

    I do not know whats the problem with Apple, or if they cannot fix it!

  • by georg50,

    georg50 georg50 Feb 12, 2015 11:15 AM in response to 4rk
    Level 1 (0 points)
    Feb 12, 2015 11:15 AM in response to 4rk

    This still is not over. I have upgraded a Macbook Pro (MacBookPro9,2 according to "About your Mac") to Yosemite 10.10.2. The WLAN chipset it has built in is the Broadcom BCM4331. The driver/firmware version is 7.15.159.13.12. I still get the same kind of latency with 1 second pings:

     

    PING 192.168.1.22 (192.168.1.22) 56(84) bytes of data.

    64 bytes from 192.168.1.22: icmp_req=1 ttl=64 time=1.84 ms

    64 bytes from 192.168.1.22: icmp_req=2 ttl=64 time=111 ms

    64 bytes from 192.168.1.22: icmp_req=3 ttl=64 time=31.7 ms

    64 bytes from 192.168.1.22: icmp_req=4 ttl=64 time=1.59 ms

    64 bytes from 192.168.1.22: icmp_req=5 ttl=64 time=71.6 ms

    64 bytes from 192.168.1.22: icmp_req=6 ttl=64 time=104 ms

    64 bytes from 192.168.1.22: icmp_req=7 ttl=64 time=19.9 ms

    64 bytes from 192.168.1.22: icmp_req=8 ttl=64 time=60.2 ms

    64 bytes from 192.168.1.22: icmp_req=9 ttl=64 time=60.4 ms

    64 bytes from 192.168.1.22: icmp_req=10 ttl=64 time=87.4 ms

    64 bytes from 192.168.1.22: icmp_req=11 ttl=64 time=110 ms

    64 bytes from 192.168.1.22: icmp_req=12 ttl=64 time=33.0 ms

    64 bytes from 192.168.1.22: icmp_req=13 ttl=64 time=64.6 ms

    64 bytes from 192.168.1.22: icmp_req=14 ttl=64 time=76.2 ms

    64 bytes from 192.168.1.22: icmp_req=15 ttl=64 time=4.44 ms

    64 bytes from 192.168.1.22: icmp_req=16 ttl=64 time=1.63 ms

    64 bytes from 192.168.1.22: icmp_req=17 ttl=64 time=42.6 ms

    64 bytes from 192.168.1.22: icmp_req=18 ttl=64 time=62.5 ms

    64 bytes from 192.168.1.22: icmp_req=19 ttl=64 time=86.3 ms

    64 bytes from 192.168.1.22: icmp_req=20 ttl=64 time=109 ms

    64 bytes from 192.168.1.22: icmp_req=21 ttl=64 time=30.5 ms

    64 bytes from 192.168.1.22: icmp_req=22 ttl=64 time=52.8 ms

    64 bytes from 192.168.1.22: icmp_req=23 ttl=64 time=75.3 ms

    64 bytes from 192.168.1.22: icmp_req=24 ttl=64 time=98.2 ms

    64 bytes from 192.168.1.22: icmp_req=25 ttl=64 time=130 ms

    64 bytes from 192.168.1.22: icmp_req=26 ttl=64 time=39.0 ms

    64 bytes from 192.168.1.22: icmp_req=27 ttl=64 time=63.7 ms

    64 bytes from 192.168.1.22: icmp_req=28 ttl=64 time=86.5 ms

    64 bytes from 192.168.1.22: icmp_req=29 ttl=64 time=116 ms

    64 bytes from 192.168.1.22: icmp_req=30 ttl=64 time=31.4 ms

    64 bytes from 192.168.1.22: icmp_req=31 ttl=64 time=59.2 ms

    ^C

    --- 192.168.1.22 ping statistics ---

    31 packets transmitted, 31 received, 0% packet loss, time 30038ms

    rtt min/avg/max/mdev = 1.597/62.117/130.333/36.253 ms

     

    If one pings in 0.2 second intervals things look up, but are still not the way they ought to be:

     

    --- 192.168.1.22 ping statistics ---

    1848 packets transmitted, 1847 received, 0% packet loss, time 370577ms

    rtt min/avg/max/mdev = 0.876/3.763/125.117/7.167 ms

     

    If I boot a Linux distribution on that Macbook and make it accessible via WLAN, the ping average drops to a bit above one millisecond, 1.2 or thereabouts. Also, the maximum latency does not go above 20 milliseconds.

     

    All my testing was done on a pretty quiet WLAN with two workstations attached. The access point was a Ubiquity Unifi, the 2.4 Ghz model that does a/b/g/n. Pinging was not done from the Mac, but from a server on the network (which should not affect results).

first Previous Page 52 of 54 last Next