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

Hi,

Ok, got my 1st 13"mbpR early nov, called up apple care, sent to genius, genius, advise hw swap.

Spoke to Apple care who gave option of swap now or wait. I waited (was given 30 days) - as still no better at day 28 called back Apple care and said they need to sort - I said don't care if firmware, software or hardware - it needs fixing as machine worse than my 2009 MBP I had just come off. (Machine also had a rattle feeling on top of touch pad so I was keen on a HW swap - small I know but I live on my machine).

Any how they decided to swap hardware.

New machine arrived yesterday.

Data migrated and been working on all morning - seems very snappy and slick (I pray it stays this way).

It arrived with 10.9 on it, have updated to 10.9.1.

Only thing I did diff than my 1st one - I migrated data on 1st one via a TM backup restore.

This time I migrated data via a ethernet cable between machines (both times using the migration assistant) - just added this incase it turns out to be important.

Am tracking forum so will report back - but until you hear from me again I guess no news is good news (hope that is not tempting fate)

Went to Chicago genius bar - worked with Trainee who seemed knowlegable - said I was getting a very slow start to WiFi connection (about 1 1/2 mins) during travel and signal gets dropped a lot - more than any other Mac I've had - pulled up bookmark to this discussion - manager came over - "Well, there are a lot of threads at any discussion". OK, I just want to have this visit noted that there is a WiFi complaint with my computer. I also mentioned that in the past, I have received a credit or some other form of compensation for an Apple device shortcoming. He didn't seem to like hearing that.

Anyway, we are all familiar with Apple doctrine - very slow to admit shortcoming or fault.

Everyone should get in touch with Apple in some way to complain - so it becomes obvious there's a glitch and they need to address it.

I spoke on the phone with apple support guy today. 

I explained I did the pram zap , smc reset,  terminal script trick , blue tooth off ....

The solutions he could come up with was a re-install of mavericks. I did that from recovery mode.

now 3 hrs later.....Testing again. No change.Problem still exists.

The tech support gy suggested that if  this would not work the next step would be a clean re-install of mavericks. And then step by step adding my back up system from my timemachine back up.

If that does not work he suggested that the machine should go for repair.

Bought on black friday.....So 1 month old.......The guy doubted I would have a right to a new machine.

Repair would be the only option he thought. You can imagine I was quite shocked to hear this.

If this would be true this would mean that the risk for manufacturing mistakes would lie with the user.......?

Anyway , the guy was from tech support so maybe aftersales will have a proper perpective on this matter.

I will wait with jumping to conclusions but if a clean re-install does not solve it and Apple does not offer a beforehand tested replacement model my planned purchase for a new mac pro is of course out of the question.

well ...we will see how it gooes.  I m trying not to make assumptions. 

Still have faith in a software solution. Net step: clean re-install. Will keep you all posted.

The problem exists on mac osx AND Windows, so I don't know why a reinstall might change anything.....

I have a multiboot environment and I got the same problems on both os.

"Repair would be the only option he thought"

In my opinion, it's okay, but I don't believe they are able to repair it at this time...

indeed windows has the same poblem here too.  your conclusion makes sense.

Reinstall of Mavericks isn't going to fix the problem. CLEAN install won't fix the problem. I booted in RECOVERY MODE and had problems connecting to WiFi and had drops. People have reported having the issue in Windows. This is obviously a hardware issue.

I just hope my replacement (being built right now) will be fixed. If not, I'll just stay on my mid-2012 13" MBA and get a refund.

Apple needs to address the issue and quick. Customers who buy a MAXED out MacBook Pro obviously need their machines... these are $3k laptops. I can get by on an Air for the most part, just really wanted the extra drive space and extra Thunderbolt port.

I'll update when I get the replacement next week.

Just want to mention that assigning static DNS information appears to have helped, although not fixed, the issue with my MBP 13" Retina.

For those wanting to try, I am using a combination of OpenDNS and Google's DNS:

208.67.220.220

208.67.222.222

8.8.8.8

Same Problems on late 2013 MBP. But under bootcamp/windows 8.1 the problem seems not to exist!? have to check it again. i called apple support. after some steps (smc reset...) didnt help, i have to go to genius bar in 3 days. but before i go there i will test some mbp's in the store if all mbps have this "ping"-problem. if yes, i will go forward to get a full refund, even the mbp is 2 months old. in germany they can repair the machine 3 times, if the problem then still exists, you get a refund. unbelievable, that there is no statemant from apple at this time.

Hi!

I've got the same problems in my late 2013 rMBP bought 2 weeks ago. I've been following this thread for the last 2 days. Using the script for keep the connection alive. It didn't fix anything, it just reconnects when needed. Useful and of course many thanks

I discovered something completely unexpected for me. I set up manual configuration (no DHCP), IP 192.168.2.150, gateway 255.255.255.0 using google DNS (8.8.8.8 ...) and the connections drops anyway BUT...

... i can connect to the router! I connect the router (192.168.2.1), access via web, and change settings as usual when the connection is "not working". So it is connected actually. Connection done using IP straight. So, no DNS involved.

Meanwhile i have not got connection in the MBP to anywhere beyond my router, but I insist i can connect to router without any problem..

And in addition, while my MBP connection drops, I used the PING tool in the router and

1. From router i can ping to google and google dns ( so router is connected to internet)

2. From router i CAN NOT ping the macbookpro (192.168.2.150 manual configured ip).

3. From router I can ping other computers connected ( a PC with windows7).

4. From MBP i cannot ping router

5. From MBP i cannot ping other PC

I insist, when the connection is "down" i can still connect to the router with the browser.

I think there is a problem with the driver in OSX. It seems it is a very complex behaviour for optimizing energy in the wifi. Device gets disabled until it gets a ping.

I also have samsung devices (tablet and phones) with android. I saw other posts saying that they can interfere. I was sure all were disconnected. In the router did not appear as DHCP assigned  IPs so, no I discard this hipothesis.

All in a WPA/WPSA2 network, 802.11b + 802.11g (mixed). Channel 7

I hope it helps to discover *** is happening. Im new in MAC (apple in general) but I just spent 1500€ in a laptop and this is completely unacceptable.

I am having a similar issue with the late 2013 Retina Macbook 15" with the graphics card. About 5 mins after waking the computer or starting up the wifi disconnects. I have to turn wifi off and turn it back on again to get it to reconnect. It will also do this randomly as I use the internet. I have been trying to replace my 5 year old iMac with a new computer. I started with the Macbook Air Haswell in August and returned it because of wifi issues. I tried 2 of the new Haswell iMacs and both had the same issues. I returned them. I purchased the Macbook Retina and it seemed to work well for the first month and now it is suffering from the same wifi issues. I have been a loyal Apple fan for years, but this year I have serious doubts about the quality of Apple computers. I do not have access to a wired connection where I stay and am depending on this laptop for school. I have called Apple Care and they want me to bring it in to the Genius bar. I guess I wll do that on Saturday, although from reading this discussion, I think it may be a waste of time. Good luck everybody.

i contacted apple about this today.

They tell me to bring it to a local authorized store for repair, although they think its not a hardware thing. Hardware swap is not an option, unless they really cant repair it.

They say i should have claimed this within 14 days (bought it mid November), but when i first noticed it, i suspected my new airport extreme, which i returned to a local store for a voucher! and used DLan. I had no idea that it was the Macbook, until i realized that this problem consists with all other networks that i have used so far.

Now i have to figure out how to get to that repair store during opening hours (i have a daytime job and swiss stores close at 5-6pm!!)

I am furious!!

johnniecache, You absolutely CAN return it if you bought it in November. The holiday return policy gives you until January 7th (TOMORROW!)

http://store.apple.com/us/help/returns_refund

Make sure you mention that to them. That's what I did and they processed mine immediately.

I'm not sure why or what happened but yesterday I bought a new router which is ac, my macbook pro running on ac is getting perfect pings very consistant and now when I join my old network where I had problems I don't have any issues anymore. I found it strange but these are my settings:

NEW NETWORK- mixed ac & n, WPA2, 5Ghz only 20,40,80mhz (D-Link DIR-820L)

OLD NETWORK- mixed (no ac),WPA2, 2.4Ghz only 20mhz (Cisco DPC3825-modem&router in one)

NEW NETWORK

64 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=2.598 ms

64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=1.677 ms

64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=2.482 ms

64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=1.915 ms

64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=2.088 ms

64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=1.237 ms

64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=1.480 ms

64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=1.490 ms

64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=1.423 ms

64 bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=1.499 ms

64 bytes from 192.168.1.1: icmp_seq=10 ttl=64 time=2.075 ms

64 bytes from 192.168.1.1: icmp_seq=11 ttl=64 time=1.492 ms

64 bytes from 192.168.1.1: icmp_seq=12 ttl=64 time=1.457 ms

64 bytes from 192.168.1.1: icmp_seq=13 ttl=64 time=1.399 ms

64 bytes from 192.168.1.1: icmp_seq=14 ttl=64 time=1.784 ms

64 bytes from 192.168.1.1: icmp_seq=15 ttl=64 time=1.228 ms

64 bytes from 192.168.1.1: icmp_seq=16 ttl=64 time=1.466 ms

64 bytes from 192.168.1.1: icmp_seq=17 ttl=64 time=1.504 ms

64 bytes from 192.168.1.1: icmp_seq=18 ttl=64 time=1.752 ms

64 bytes from 192.168.1.1: icmp_seq=19 ttl=64 time=1.491 ms

64 bytes from 192.168.1.1: icmp_seq=20 ttl=64 time=1.192 ms

64 bytes from 192.168.1.1: icmp_seq=21 ttl=64 time=1.498 ms

64 bytes from 192.168.1.1: icmp_seq=22 ttl=64 time=1.662 ms

64 bytes from 192.168.1.1: icmp_seq=23 ttl=64 time=1.447 ms

64 bytes from 192.168.1.1: icmp_seq=24 ttl=64 time=1.482 ms

64 bytes from 192.168.1.1: icmp_seq=25 ttl=64 time=1.393 ms

64 bytes from 192.168.1.1: icmp_seq=26 ttl=64 time=1.434 ms

64 bytes from 192.168.1.1: icmp_seq=27 ttl=64 time=1.441 ms

64 bytes from 192.168.1.1: icmp_seq=28 ttl=64 time=1.405 ms

64 bytes from 192.168.1.1: icmp_seq=29 ttl=64 time=1.490 ms

64 bytes from 192.168.1.1: icmp_seq=30 ttl=64 time=1.404 ms

64 bytes from 192.168.1.1: icmp_seq=31 ttl=64 time=1.430 ms

64 bytes from 192.168.1.1: icmp_seq=32 ttl=64 time=1.438 ms

64 bytes from 192.168.1.1: icmp_seq=33 ttl=64 time=1.394 ms

64 bytes from 192.168.1.1: icmp_seq=34 ttl=64 time=1.478 ms

64 bytes from 192.168.1.1: icmp_seq=35 ttl=64 time=1.391 ms

64 bytes from 192.168.1.1: icmp_seq=36 ttl=64 time=1.432 ms

64 bytes from 192.168.1.1: icmp_seq=37 ttl=64 time=1.438 ms

64 bytes from 192.168.1.1: icmp_seq=38 ttl=64 time=1.380 ms

64 bytes from 192.168.1.1: icmp_seq=39 ttl=64 time=1.513 ms

64 bytes from 192.168.1.1: icmp_seq=40 ttl=64 time=2.276 ms

64 bytes from 192.168.1.1: icmp_seq=41 ttl=64 time=1.425 ms

64 bytes from 192.168.1.1: icmp_seq=42 ttl=64 time=1.432 ms

64 bytes from 192.168.1.1: icmp_seq=43 ttl=64 time=1.831 ms

64 bytes from 192.168.1.1: icmp_seq=44 ttl=64 time=1.905 ms

64 bytes from 192.168.1.1: icmp_seq=45 ttl=64 time=2.074 ms

OLD NETWORK

64 bytes from 192.168.0.1: icmp_seq=8 ttl=64 time=1.586 ms

64 bytes from 192.168.0.1: icmp_seq=9 ttl=64 time=1.599 ms

64 bytes from 192.168.0.1: icmp_seq=10 ttl=64 time=1.657 ms

64 bytes from 192.168.0.1: icmp_seq=11 ttl=64 time=1.587 ms

64 bytes from 192.168.0.1: icmp_seq=12 ttl=64 time=1.632 ms

64 bytes from 192.168.0.1: icmp_seq=13 ttl=64 time=3.451 ms

64 bytes from 192.168.0.1: icmp_seq=14 ttl=64 time=1.657 ms

64 bytes from 192.168.0.1: icmp_seq=15 ttl=64 time=1.634 ms

64 bytes from 192.168.0.1: icmp_seq=16 ttl=64 time=1.555 ms

64 bytes from 192.168.0.1: icmp_seq=17 ttl=64 time=3.517 ms

64 bytes from 192.168.0.1: icmp_seq=18 ttl=64 time=1.557 ms

64 bytes from 192.168.0.1: icmp_seq=19 ttl=64 time=1.383 ms

64 bytes from 192.168.0.1: icmp_seq=20 ttl=64 time=1.653 ms

64 bytes from 192.168.0.1: icmp_seq=21 ttl=64 time=1.571 ms

64 bytes from 192.168.0.1: icmp_seq=22 ttl=64 time=1.627 ms

64 bytes from 192.168.0.1: icmp_seq=23 ttl=64 time=1.547 ms

64 bytes from 192.168.0.1: icmp_seq=24 ttl=64 time=2.051 ms

64 bytes from 192.168.0.1: icmp_seq=25 ttl=64 time=2.968 ms

64 bytes from 192.168.0.1: icmp_seq=26 ttl=64 time=1.604 ms

64 bytes from 192.168.0.1: icmp_seq=27 ttl=64 time=1.612 ms

64 bytes from 192.168.0.1: icmp_seq=28 ttl=64 time=1.600 ms

All in all the wifi on the mac is working quite nicely now, although I haven't yet tested it on other networks apart from a mobile hotspot which also worked great with consitent pings.

thank you so much! I just called again, mentioned the "holiday return policy" and they processed it right away.

You just saved me so much hassle