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

reboot, really? Have you tried to turn off / turn back on the WiFi? This works for me.

Also I have been using VPN a lot lately, I got a lot less problems there. Probably keeps the line busy somehow.

Anyway I still believe its not a hardware issue and hope that apple will fix this eventually.

Never Mind. All the best to you and Happy New Year.

johnniecache wrote:

 

Anyway I still believe its not a hardware issue and hope that apple will fix this eventually.

Because it is fixed in 10.9.2 on my Macbook Pro.

Well there goes that NDA you signed.

If I were to take my MacBook (13 inch, Haswell) back to Apple because of this issue, what would happen? Would I get a replacement or a refund (Bought mine about a month ago)? Is there any chance, that a replacement MacBook wouldn`t also have the same Wi-Fi problem?

In the last months I had two MacBooks (13" Air & 13" MBPRO Retina, both late 2013 version) with Wi-Fi problems. Both had pings ranging from 1ms to 800ms. The Air's Wifi issue was especially hard, I couldn't make a Skype call for more than 15min. - of course I returned that one. Three and a half months later I decided to give the new MacBook Pro Retina a shot. Also that one had a Wi-Fi issue, but not as dramatic as the Air. Pings were also quite unstable (in comparison my MacBook Pro 2009 had pings ranging from 1ms - 3ms in the same network and in the same room at the same time), but long Skype calls and big downloads were no problem. After reading through some posts, I accepted the fact that the Wi-Fi issue was just a "feature", which was not well executed.

Last monday I went to an Apple Store in Germany and tested all the MacBooks in the store. Somehow pinging the router was not possible, but I pinged www.google.com via Terminal and the result was "calming" in a sense that I now know that every MacBook has dramatic pings and dropped packages. The only model, which is not effected is the old MacBook Pro non-retina.

In the end unfortunately I also had to return my MacBook Pro Retina because of the burn-in problem with the retina display (also known as "ghosting").

After two returned MacBooks the Apple support gave me a 100€ discount. This is nice, but I'd rather prefer a perfectly working machine without having to worry about what will happen with the wifi in the future than a discount. I don't buy Apple because it's cheap, I buy it because it (should) work. I have the feeling that Apple currently has a big problem with their quality control. The products are not as good as they were a couple of years ago. Fortunately they have a good after sales service, otherwise they would lose many customers.

So one advice for everyone buying a newer Macbook: Test it throroughly, make long Skype calls, download huge files >1GB, test the display. If there is anything not working well, don't hesitate to make use of the 14 days return policy. Return your MacBook until you have the perfect one. You will probably even get a discount for doing it. But don't accept the fact that you pay tons of money to get product which is not working perfectly (in the case of Wi-Fi and the display it's not even about perfection, but basic functions which should work...).

But did you eventually end up with the mbpr that wasn't affected by this issue? To my knowledge, it still isn't clear whether all late 2013 macbooks are affected.

I'm also having this issue... Wifi becomes incredibly slow then fails altogether. Late 2013 13" MacBook Pro Retina. After several support calls to Apple, they couldn't figure out what was wrong with it so I'm sending it back. After doing some searching, I'm afriad to order another one for fear that it might have the same problems.

Should I go back to 13" MacBook Air until this gets sorted out?

Dot K wrote:

 

Because it is fixed in 10.9.2 on my Macbook Pro.

Please Apple, if this is a known issue and you are working on a solution (or have one already) let us know!

If this turns out to be a hardware issue, it was my first and last mac.

Is there any official statement on this issue from Apple? For such highly priced machines as MacBooks are, it is unacceptable to fall short in such a basic requirement as network connectivity. And if such a mistake still happens, there should AT LEAST be an official statement from Apple. Everything else is a complete disgrace. One should go public and have some of the tech magzines report on this. Apple used to stand for superior quality, but they seem to compromise their own principles and we as customers are paying for it.

Mine got partially fixed when I ran the network diagnostics (command click on the wifi symbol in the top bar) and monitoring the connection for a bit. It works okay now except when I try to operate behind my University's proxy. Then it goes back to getting stuck.

Apple must have a policy of only (or at least mostly) dealing with customers directly, rather than on these forums. Maybe I'll mention that in that survey they're trying to get me to do.

Same here. Have to flip wifi off and on every 30 minutes for it to work. I want my money back, but I've ordered it online, so it's a bit hard to do.

same problems here on Macbook Pro Retina 13.3" late 2013.

I've been working with AppleCare support since I got my MacBook Pro Retina... I think my first call was around December 13th (I got the laptop on the 10th).

I just mailed it back yesterday getting a replacement, thank goodness I hadn't sold my old MacBook Air yet. They wouldn't even initiate an order for a replacement until they had received confirmation I shipped the defective unit back, and it's a custom-configured model (2.8, 16GB, 1TB) that will take "1-2 Weeks" to build. So apparently I'd just be without a computer for 2-3 weeks unless I had this old Air to use.

I hope the new MBP works fine and has no connectivity issues, but I have to say I'm pretty upset with the level of support I've gotten with this issue. If they had just acknowledged a hardware issue when I first called and sent out a replacement immediately I'd be (hopefully) using my new computer right now.

As a business customer, I shouldn't have to keep old laptops around to make sure my business is up and running. We pay a **** of a lot of money for Apple products because the support has always been top notch... this experience definitely makes me think about that though.

Same problem here.

Currently using the ping -i 0.2 workaround. For people that are perhaps not tech savvy enough to employ the solution themselves, here's one way to do it:

1. Open Terminal. It's located in your /Applications/Utilities/ folder.

2. Right click and paste the following into the window:

netstat -nr | grep '^default' | awk '{print $2;}'

3. Press Enter. You will then get the IP address of your default gateway (i.e. your wireless router). For many people, it will be "192.168.1.1"

4. Using the address you found above, issue the following command:

ping -i .2 REPLACETHIS

Where "REPLACETHIS" is instead the address of your default gateway. This will start Terminal to continually "pinging" your wireless router every 0.2 seconds to keep your wireless connection nice and snappy. This is not a "fix" -- you'll have to redo the above steps whenever Terminal gets closed (e.g. if you restart your computer).

Alternatively, instead everyone pinging their own default gateways, we could instead ping www.apple.com If enough of us suffer from this problem, Apple's website will suffer in turn.