Late 2013 Macbook Pro Retina 13'' Wifi Issues

The frog says "hi"

My wifi drops when I plug in an external monitor through the thunderbolt port

(though most of it is not applicable to my problem, since everything fine with 2nd thunderbolt, therefore the problem is within MacBook)

By the way, a lot of people were changing their wifi router to channel 1 - may be, will help to somebody here

It works! Thanks...

Before:

PING www.seznam.cz (77.75.79.39): 56 data bytes

64 bytes from 77.75.79.39: icmp_seq=0 ttl=245 time=4.981 ms

64 bytes from 77.75.79.39: icmp_seq=1 ttl=245 time=7.584 ms

64 bytes from 77.75.79.39: icmp_seq=2 ttl=245 time=7.070 ms

64 bytes from 77.75.79.39: icmp_seq=3 ttl=245 time=6.903 ms

64 bytes from 77.75.79.39: icmp_seq=4 ttl=245 time=6.679 ms

64 bytes from 77.75.79.39: icmp_seq=5 ttl=245 time=8.910 ms

64 bytes from 77.75.79.39: icmp_seq=6 ttl=245 time=512.180 ms

64 bytes from 77.75.79.39: icmp_seq=7 ttl=245 time=37.478 ms

64 bytes from 77.75.79.39: icmp_seq=8 ttl=245 time=97.633 ms

64 bytes from 77.75.79.39: icmp_seq=9 ttl=245 time=793.175 ms

64 bytes from 77.75.79.39: icmp_seq=10 ttl=245 time=5.986 ms

64 bytes from 77.75.79.39: icmp_seq=11 ttl=245 time=8.154 ms

64 bytes from 77.75.79.39: icmp_seq=12 ttl=245 time=7.513 ms

64 bytes from 77.75.79.39: icmp_seq=13 ttl=245 time=5.382 ms

64 bytes from 77.75.79.39: icmp_seq=14 ttl=245 time=5.523 ms

64 bytes from 77.75.79.39: icmp_seq=15 ttl=245 time=7.575 ms

64 bytes from 77.75.79.39: icmp_seq=16 ttl=245 time=305.124 ms

64 bytes from 77.75.79.39: icmp_seq=17 ttl=245 time=359.971 ms

Request timeout for icmp_seq 18

64 bytes from 77.75.79.39: icmp_seq=18 ttl=245 time=1333.457 ms

64 bytes from 77.75.79.39: icmp_seq=19 ttl=245 time=332.400 ms

64 bytes from 77.75.79.39: icmp_seq=20 ttl=245 time=5.471 ms

64 bytes from 77.75.79.39: icmp_seq=21 ttl=245 time=6.131 ms

64 bytes from 77.75.79.39: icmp_seq=22 ttl=245 time=5.610 ms

After:

PING www.seznam.cz (77.75.77.39): 56 data bytes

64 bytes from 77.75.77.39: icmp_seq=0 ttl=245 time=11.211 ms

64 bytes from 77.75.77.39: icmp_seq=1 ttl=245 time=15.706 ms

64 bytes from 77.75.77.39: icmp_seq=2 ttl=245 time=15.471 ms

64 bytes from 77.75.77.39: icmp_seq=3 ttl=245 time=14.171 ms

64 bytes from 77.75.77.39: icmp_seq=4 ttl=245 time=12.242 ms

64 bytes from 77.75.77.39: icmp_seq=5 ttl=245 time=15.774 ms

64 bytes from 77.75.77.39: icmp_seq=6 ttl=245 time=15.931 ms

64 bytes from 77.75.77.39: icmp_seq=7 ttl=245 time=13.837 ms

64 bytes from 77.75.77.39: icmp_seq=8 ttl=245 time=14.499 ms

64 bytes from 77.75.77.39: icmp_seq=9 ttl=245 time=12.035 ms

64 bytes from 77.75.77.39: icmp_seq=10 ttl=245 time=12.939 ms

64 bytes from 77.75.77.39: icmp_seq=11 ttl=245 time=13.938 ms

64 bytes from 77.75.77.39: icmp_seq=12 ttl=245 time=13.279 ms

64 bytes from 77.75.77.39: icmp_seq=13 ttl=245 time=16.104 ms

64 bytes from 77.75.77.39: icmp_seq=14 ttl=245 time=16.103 ms

64 bytes from 77.75.77.39: icmp_seq=15 ttl=245 time=15.886 ms

64 bytes from 77.75.77.39: icmp_seq=16 ttl=245 time=5.693 ms

64 bytes from 77.75.77.39: icmp_seq=17 ttl=245 time=7.818 ms

64 bytes from 77.75.77.39: icmp_seq=18 ttl=245 time=5.253 ms

64 bytes from 77.75.77.39: icmp_seq=19 ttl=245 time=6.000 ms

64 bytes from 77.75.77.39: icmp_seq=20 ttl=245 time=5.283 ms

64 bytes from 77.75.77.39: icmp_seq=21 ttl=245 time=6.052 ms

64 bytes from 77.75.77.39: icmp_seq=22 ttl=245 time=7.144 ms

64 bytes from 77.75.77.39: icmp_seq=23 ttl=245 time=5.637 ms

64 bytes from 77.75.77.39: icmp_seq=24 ttl=245 time=5.375 ms

64 bytes from 77.75.77.39: icmp_seq=25 ttl=245 time=4.779 ms

64 bytes from 77.75.77.39: icmp_seq=26 ttl=245 time=5.613 ms

I was reading through the posts and found that people are having many different issues and random fixes are working for different laptops and setups.

I've decided to troubleshoot issue simply by pinging router non-stop and trying different thing.

First I noticed that if I move the laptop to the router - connection restores to normal, but it didn't make sense, since even near desk - all was fine.

Then I looked at every step of the way and found out that connection restores after I unplug cable from thunderbolt (I have second monitor there).

Therefore, for my laptop that thunderbolt was the problem - probably it was sharing CPU PCI lanes.

Surprisingly It only occurred on the first thunderbolt, but the second one was fine.

Conclusion - 1st thunderbolt interferes with wifi card (probably on motherboard or CPU pci lanes), but has nothing to do with router or connection or spectrum...

Motherboard design fault

Therefore, for my laptop that thunderbolt was the problem - probably it was sharing CPU PCI lanes.

Motherboard design fault

I do not know how to come off Not sounding like a jerk. But you have gone WAY out own a limb and leaped to conclusions that are not warranted, based on methods that are deeply flawed.

Ping times may indicate that there ARE issues, but provide no additional information as to WHY.

Your conclusion of sharing PCI lanes is baseless, and further that these computers are all mis-designed is not based on any real data. If you study the computer architecture of these computers, there is no shortage of bandwidth to support the (near-trivial) demands of a few hundred megabits/sec of intermittent Wi-Fi traffic on a ThunderBolt Bus.

What is far, far more likely is that you are using only the very crowded and interference-prone 2.4GHz band, along with microwave ovens, portable landline phones, and baby monitors, as are all your neighbors. In addition, I expect your Router is misconfigured, too distant, or simply does not feature the 5GHz band. Interference in the 2.4GHz band from certain thunderbolt ports and cables, especially loops of cables, in close proximity are known to cause 2.4GHz Wi-Fi problems.

As you have seen, moving the thunderBolt cable away from the port closest to the Wi-Fi receiver seem to alleviate the problem. and so do lots of other brute-force things you can do.

But the real fix is likely in your Wi-Fi setup, and in the traffic and interference in the airwaves at your exact location.

DATA:

plug in monitor to 1st thunderbolt -> wifi problems

remove cable from 1st thunderbolt -> no problems

plug in monitor to 1st thunderbolt -> wifi problems

remove cable from 1st thunderbolt -> no problems

plug in monitor to 1st thunderbolt -> wifi problems

remove cable from 1st thunderbolt -> no problems

logic = conclusion

There is a lot of information available inside your Mac for troubleshooting these problems, and I work with Users every week analyzing their networks to try to figure out why their Wi-Fi may not be as happy as it should be.

Typical Wi-Fi problems are very seldom un-explainable. I have never even suspected a design error, although there have been a few disconnected antenna leads. There has been a lot of interference from neighbor's Routers.

There may well be interference in the 2.4GHz band cause by certain Thunderbolt cables and adapters -- but this is most likely because the cables themselves are radiating energy near the required frequencies, and loops of cable, or using the port closest to the Wi-Fi Antenna may indeed make it worse. There have been far too many problems solved by turning off Bluetooth, which competes in the 2.4GHz band but uses a different modulation method (it channel hops).

Changing the channel is likely to change the symptoms. But it is not a scientific thing to do, and there are better ways to force the Router to optimize which channel it uses.

If you are having some Wi-Fi problems, please start new thread providing which model Mac, which MacOS, and what sorts of problems you are encountering. Delays in Ping and lost packets on Ping are symptoms of problems, but they provide no diagnostic information.

Yes, there can be many reasons and so on and on...

But some people might not even think that their wifi problem caused by thunderbolt port (or monitor interference)

Somebody could go crazy about changing routers and million settings that are connected to the network.

May be, my suggestion can really help somebody.

Sharing is caring.

Mihael_Keehl

I appreciate your helpfulness, and your suggestions may well help someone.

It maintain it would be more helpful to most folks who are actually having a problem to start a new thread and post their Mac model, MacOS version, and a description of their problem. These types of issues are complex, and it often takes several rounds of questions and answers to home in on what some of the issues might be.

When folks post "Me, too" on a thread like this with over 800 individual posts by dozens of different users over 55 pages of posts, I cannot keep track of who might have cable issues, who might benefit from turning off Bluetooth, who might have a broken antenna, who needs to consider buying a new Router, who should try changing the channel on their Router, and so on.

When you start a new thread with only your information and give it a catchy title, it will attract the readers you need to make suggestions, and problems can get solved in short order.

I have the 8GB/256GB model and having the same problem, WIFI has lag spikes intermittently. My mid 2010 MBP has no issues.

I have only had this MBP for less than 1 week, so if there is a problem, I'd like to get it replaced.

Edit: looks like something that the MBA had: http://support.apple.com/kb/TS4611

Did you read the warranty paperwork that came w/your computer?

You have 14 days to return the computer w/no questions asked. Plus you have 90 days of FREE phone tech support on top of your standard 1 year warranty unless you also purchased AppleCare which gives you an additional 2 years of coverage plus FREE phone support.

Strongly suggest that you take FULL advantage of the above before it runs out. Let Apple deal w/the problems.

I have found the issue to be associated with the wireless N network. If i disable N and run only b/g from my router, I have no issues. When N is enabled, I get dropped packets even when running a ping test to my router.

I will test with another wireless N router to prove what is happening.

Give it a try Shane.

Same problem here with the new rMBP 15"/16GB/512GB/750M.

All other devices (2 MacBooks, iMac and PC) have absolutely no wifi-problems, but the rMBP 15" Late 2013 has connections drops and generally a very slow wifi speed. It gets better when I move closer to the router, but that can't be a solution as ALL the other devices work perfect from the room, where I use to work.

Update:

Apple has confirmed I have a faulty Airport card, antenna, logic board.

Get your MBP's in and checked for problems at your local Apple store.

I am trying to get a DOA at the moment but my retailer is giving me the run around.

I'm having a really hard time diagnosing if I'm even suffering from this problem or not. On one hand, streaming video over my local network skips and lags, but on the other, I get a consistent 64mbps (definitely lowballing it too) when copying said videos over my local network, which is more than enough to smoothly playback these files. I'd chalk it up to a software issue, but I have the same problem accross multiple playback applications. My roommate's 2012 MBA doesn't suffer from this issue either adding even more confusion. Any advice for debugging this?

The cause of my problems was eratic pings and dropped packets.

Try doing a ping test against your gateway to see how high your pings are and if you get dropped packets. I ran tests of 1000 pings and found i lost on avg 5% of the packets, with pings ranging from 1ms to 600ms.

My 2010 MBP was getting 1ms to 5ms, no dropped packets.