Skip navigation

new macbook pro 2011 weak and dropping wireless connection

232853 Views 965 Replies Latest reply: Jan 7, 2014 3:13 AM by BananaMacintosh RSS
  • Blissedout4ever Calculating status...

    So are the tech support ppl aware of this as an engineering problem? If they are why wouldn't they tell you over the phone and not spend hours paying someone to go thru all of this rigamarole??

  • Macman 007 Calculating status...

    Hi, sorry to hear your problem. I also have that issue with my 2007 macbook pro. just turn airport on then off and your signal should be fine.

    hope that helps

  • bitserf Calculating status...

    Well, sorry to say, but the firmware fix was only temporary, as others have reported when you actually start using the connection in any way the latency spikes and packet loss is common again.

     

    So I thought I'd borrow my friend's Airport Extreme (the dual-band 2.4/5ghz N edition), since he also has a 2011 MacBook Pro but didn't report any issues like this.

     

    I've had it for the past week, and surprise, surprise, it's rock solid with stable latency:

     

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

    64 bytes from 192.168.1.1: icmp_seq=46 ttl=64 time=1.281 ms

    64 bytes from 192.168.1.1: icmp_seq=47 ttl=64 time=4.903 ms

    64 bytes from 192.168.1.1: icmp_seq=48 ttl=64 time=4.732 ms

    64 bytes from 192.168.1.1: icmp_seq=49 ttl=64 time=4.861 ms

    64 bytes from 192.168.1.1: icmp_seq=50 ttl=64 time=4.720 ms

    64 bytes from 192.168.1.1: icmp_seq=51 ttl=64 time=4.677 ms

    64 bytes from 192.168.1.1: icmp_seq=52 ttl=64 time=4.811 ms

    64 bytes from 192.168.1.1: icmp_seq=53 ttl=64 time=4.627 ms

    64 bytes from 192.168.1.1: icmp_seq=54 ttl=64 time=4.792 ms

    64 bytes from 192.168.1.1: icmp_seq=55 ttl=64 time=4.726 ms

    64 bytes from 192.168.1.1: icmp_seq=56 ttl=64 time=4.773 ms

    64 bytes from 192.168.1.1: icmp_seq=57 ttl=64 time=5.019 ms

    64 bytes from 192.168.1.1: icmp_seq=58 ttl=64 time=4.927 ms

    64 bytes from 192.168.1.1: icmp_seq=59 ttl=64 time=4.597 ms

    64 bytes from 192.168.1.1: icmp_seq=60 ttl=64 time=4.747 ms

    64 bytes from 192.168.1.1: icmp_seq=61 ttl=64 time=1.210 ms

    64 bytes from 192.168.1.1: icmp_seq=62 ttl=64 time=1.134 ms

    64 bytes from 192.168.1.1: icmp_seq=63 ttl=64 time=4.800 ms

    64 bytes from 192.168.1.1: icmp_seq=64 ttl=64 time=1.932 ms

    64 bytes from 192.168.1.1: icmp_seq=65 ttl=64 time=4.838 ms

    64 bytes from 192.168.1.1: icmp_seq=66 ttl=64 time=4.811 ms

    64 bytes from 192.168.1.1: icmp_seq=67 ttl=64 time=4.701 ms

    64 bytes from 192.168.1.1: icmp_seq=68 ttl=64 time=1.134 ms

    64 bytes from 192.168.1.1: icmp_seq=69 ttl=64 time=4.855 ms

    64 bytes from 192.168.1.1: icmp_seq=70 ttl=64 time=4.778 ms

    64 bytes from 192.168.1.1: icmp_seq=71 ttl=64 time=1.086 ms

    64 bytes from 192.168.1.1: icmp_seq=72 ttl=64 time=4.774 ms

    64 bytes from 192.168.1.1: icmp_seq=73 ttl=64 time=1.077 ms

    64 bytes from 192.168.1.1: icmp_seq=74 ttl=64 time=4.671 ms

    64 bytes from 192.168.1.1: icmp_seq=75 ttl=64 time=4.790 ms

    64 bytes from 192.168.1.1: icmp_seq=76 ttl=64 time=1.230 ms

    64 bytes from 192.168.1.1: icmp_seq=77 ttl=64 time=4.681 ms

    64 bytes from 192.168.1.1: icmp_seq=78 ttl=64 time=4.885 ms

    64 bytes from 192.168.1.1: icmp_seq=79 ttl=64 time=4.673 ms

    64 bytes from 192.168.1.1: icmp_seq=80 ttl=64 time=4.802 ms

    64 bytes from 192.168.1.1: icmp_seq=81 ttl=64 time=4.945 ms

    64 bytes from 192.168.1.1: icmp_seq=82 ttl=64 time=4.828 ms

    64 bytes from 192.168.1.1: icmp_seq=83 ttl=64 time=4.677 ms

    64 bytes from 192.168.1.1: icmp_seq=84 ttl=64 time=4.712 ms

    64 bytes from 192.168.1.1: icmp_seq=85 ttl=64 time=4.598 ms

    64 bytes from 192.168.1.1: icmp_seq=86 ttl=64 time=4.687 ms

    64 bytes from 192.168.1.1: icmp_seq=87 ttl=64 time=2.498 ms

    64 bytes from 192.168.1.1: icmp_seq=88 ttl=64 time=4.671 ms

    64 bytes from 192.168.1.1: icmp_seq=89 ttl=64 time=4.719 ms

    64 bytes from 192.168.1.1: icmp_seq=90 ttl=64 time=4.841 ms

    64 bytes from 192.168.1.1: icmp_seq=91 ttl=64 time=4.808 ms

    64 bytes from 192.168.1.1: icmp_seq=92 ttl=64 time=1.167 ms

    64 bytes from 192.168.1.1: icmp_seq=93 ttl=64 time=4.708 ms

    64 bytes from 192.168.1.1: icmp_seq=94 ttl=64 time=4.639 ms

    64 bytes from 192.168.1.1: icmp_seq=95 ttl=64 time=4.716 ms

    64 bytes from 192.168.1.1: icmp_seq=96 ttl=64 time=1.240 ms

    64 bytes from 192.168.1.1: icmp_seq=97 ttl=64 time=4.864 ms

    64 bytes from 192.168.1.1: icmp_seq=98 ttl=64 time=0.965 ms

    64 bytes from 192.168.1.1: icmp_seq=99 ttl=64 time=4.656 ms

    64 bytes from 192.168.1.1: icmp_seq=100 ttl=64 time=4.784 ms

    64 bytes from 192.168.1.1: icmp_seq=101 ttl=64 time=4.487 ms

    64 bytes from 192.168.1.1: icmp_seq=102 ttl=64 time=1.197 ms

    64 bytes from 192.168.1.1: icmp_seq=103 ttl=64 time=4.866 ms

    64 bytes from 192.168.1.1: icmp_seq=104 ttl=64 time=4.573 ms

    64 bytes from 192.168.1.1: icmp_seq=105 ttl=64 time=1.074 ms

    64 bytes from 192.168.1.1: icmp_seq=106 ttl=64 time=4.864 ms

    64 bytes from 192.168.1.1: icmp_seq=107 ttl=64 time=4.871 ms

    64 bytes from 192.168.1.1: icmp_seq=108 ttl=64 time=1.303 ms

    64 bytes from 192.168.1.1: icmp_seq=109 ttl=64 time=1.174 ms

    64 bytes from 192.168.1.1: icmp_seq=110 ttl=64 time=4.654 ms

    64 bytes from 192.168.1.1: icmp_seq=111 ttl=64 time=1.193 ms

    64 bytes from 192.168.1.1: icmp_seq=112 ttl=64 time=4.673 ms

    64 bytes from 192.168.1.1: icmp_seq=113 ttl=64 time=1.196 ms

    64 bytes from 192.168.1.1: icmp_seq=114 ttl=64 time=4.657 ms

    64 bytes from 192.168.1.1: icmp_seq=115 ttl=64 time=1.616 ms

    64 bytes from 192.168.1.1: icmp_seq=116 ttl=64 time=4.949 ms

    64 bytes from 192.168.1.1: icmp_seq=117 ttl=64 time=4.652 ms

    64 bytes from 192.168.1.1: icmp_seq=118 ttl=64 time=4.678 ms

    64 bytes from 192.168.1.1: icmp_seq=119 ttl=64 time=1.258 ms

    64 bytes from 192.168.1.1: icmp_seq=120 ttl=64 time=4.751 ms

    64 bytes from 192.168.1.1: icmp_seq=121 ttl=64 time=4.539 ms

    64 bytes from 192.168.1.1: icmp_seq=122 ttl=64 time=4.690 ms

    64 bytes from 192.168.1.1: icmp_seq=123 ttl=64 time=4.708 ms

    64 bytes from 192.168.1.1: icmp_seq=124 ttl=64 time=4.833 ms

    64 bytes from 192.168.1.1: icmp_seq=125 ttl=64 time=4.728 ms

    64 bytes from 192.168.1.1: icmp_seq=126 ttl=64 time=4.582 ms

    64 bytes from 192.168.1.1: icmp_seq=127 ttl=64 time=4.727 ms

    64 bytes from 192.168.1.1: icmp_seq=128 ttl=64 time=4.673 ms

    64 bytes from 192.168.1.1: icmp_seq=129 ttl=64 time=4.511 ms

    64 bytes from 192.168.1.1: icmp_seq=130 ttl=64 time=4.624 ms

    64 bytes from 192.168.1.1: icmp_seq=131 ttl=64 time=4.632 ms

    64 bytes from 192.168.1.1: icmp_seq=132 ttl=64 time=4.592 ms

    64 bytes from 192.168.1.1: icmp_seq=133 ttl=64 time=4.726 ms

    64 bytes from 192.168.1.1: icmp_seq=134 ttl=64 time=0.987 ms

    64 bytes from 192.168.1.1: icmp_seq=135 ttl=64 time=4.938 ms

    64 bytes from 192.168.1.1: icmp_seq=136 ttl=64 time=4.956 ms

    64 bytes from 192.168.1.1: icmp_seq=137 ttl=64 time=5.062 ms

    64 bytes from 192.168.1.1: icmp_seq=138 ttl=64 time=4.589 ms

    64 bytes from 192.168.1.1: icmp_seq=139 ttl=64 time=4.707 ms

    64 bytes from 192.168.1.1: icmp_seq=140 ttl=64 time=1.147 ms

    64 bytes from 192.168.1.1: icmp_seq=141 ttl=64 time=4.681 ms

    64 bytes from 192.168.1.1: icmp_seq=142 ttl=64 time=4.767 ms

    64 bytes from 192.168.1.1: icmp_seq=143 ttl=64 time=4.762 ms

    64 bytes from 192.168.1.1: icmp_seq=144 ttl=64 time=4.704 ms

    64 bytes from 192.168.1.1: icmp_seq=145 ttl=64 time=4.765 ms

    64 bytes from 192.168.1.1: icmp_seq=146 ttl=64 time=4.753 ms

    64 bytes from 192.168.1.1: icmp_seq=147 ttl=64 time=4.728 ms

     

    So it looks like there is some incompatibility between the 2011 MacBook Pro and all WiFi access points except Apple's own.

     

    Kind of defeats the point of WiFi, no?

     

    Annoyed, because if I buy an Airport Extreme, that would be the third WiFi device I have bought to get this $3.5k laptop's wireless to work reliably.

  • GreenTape Calculating status...

    I changed my routers Encryption from WEP to WPA2-PSK....my download speed still ***** compared to windows OS and ethernet, but it seems a **** of a lot better at streaming...I dont end up playing snake on YouTube yay!

  • pezdispenser Calculating status...

    Most amount of money I've ever paid for broken machinery. Nice one apple.

     

     

    Also, this question almost certainly isn't answered. So whoever moderates this forum can edit that.

  • GreenTape Level 1 Level 1 (0 points)

    internet speed since i got my MBP...how low will it go? seriously apple sort your stuff out!
    http://chart.googleapis.com/chart?chxt=x%2Cy&chd=s%3AMRTVXZbegikmoqtvxz1358%2C80yyovdJRLQGSNKSSGQJMG%2CACEGIKMPRTVXZbegikmoqtvxz1358%2CUUUTTTTTUVVWWXWVWWTSSRRSSSUWV%2CACEGIKMPRTVXZbegikmoqtvxz1358%2CRRRRRRQRRRRSSTSRSSSSSRRSSSTTS%2CACEGIKMPRTVXZbegikmoqtvxz1358%2CRRRRRRQRRRSSSTSSSTSSSRRSSSTTS%2CACEGIKMPRTVXZbegikmoqtvxz1358%2CRRRRRSRRRRRSSTSSSTSSTRRTSSTTS%2CACEGIKMPRTVXZbegikmoqtvxz1358%2CRQQRRRRQQPQQRRQPPRRRRRQQRRRRR&chxp=0%2C5%2C95&chxr=1%2C0%2C15.34&chco=000000%2CFFCC33%2C3072F3%2C80C65A%2CFFA6C0%2CE1E1E1&chs=550x300&cht=lxy&chtt=Speed+Comparison+over+Time&chxl=0%3A%7C04%2F15%2F11%7C05%2F13%2F11&chdl=Your+Current+Location%7CYour+ISP%2FNetwork%7Cauckland%7Cauk%7Cnzl%7Cglobal

  • damianfromreading Calculating status...

    I have this problem with two new MacBook Pros Early 2011 connected to a network of Time Capsule and Airport Express units. All of my iPhones, iPads and other network devices are okay. Even an original MacBook Pro unibody on the network is fine. I have played around with creating all sorts of different network combinations, n-only,g-only, 2.4 GHz, 5GHz on different channels with no luck whatsoever. The problem must be with the new MacBook Pros and the chipset/drivers that are used. As I say, I have had a rock solid network for years so the introduction of the new MacBook Pros and their flaky connection was surprising.

  • ziggy11 Calculating status...

    Hello everyone.

    I've been monitoring this thread since I bought my 17" MBP two weeks ago. I was so excited since this is my very first Mac. I saved up so I can finally replace my old clunky pc laptop.

     

    My delight was shortlived  however, as I, too, cannot consistenly get a "decent" connection for days. I think I might have been unreasonably arrogant to believe that an update from Apple would fix this issue. I installed the subsequent updates, but I still have the problem. I can connect through WPA, and can surf for about an hour and so then the connection will either immensely slow down or totally drop. All other devices' connection (My old PC laptop, my friend's old macbook, my iphone4 won't drop at all. I tried network assist and diagnosis, restarted my computer, restarted the router, reset PRAM and NVRAM, manually input the IP addresses, cleared the cache and keychains, turned off firewall, and a bunch of stuff as suggested in here. Alas, The issue still persists. I am using a new Netgear router by the way.

     

    I am left with four choices.

     

    1) Buy a airport extreme which is mightily expensive as compared to the new Netgear unit I have right now.

    2) Wait for another update assuming Apple is working on it.

    3) Return the unit for them to check.

    4) Go back to PC (Please no..).

     

    I hope Apple can come up with a fix soon. I'll keep an eye on this thread. Thanks to everyone for giving the suggested fixes.

  • willrussian Level 1 Level 1 (0 points)

    Hi there, hope this might help to some of you...

     

    Haven't time to read all these posts I'm afraid but want to share my own recent breakthrough with the problem of constantly slow and dropping internet connection with my macbook pro while my 4 year old pc laptop sails along with the fastest connection ever! Have been pulling my hair out over this for weeks and after three phone calls to applecare and hours wasted on the net trying to find solutions have finally seemed to have cracked it!!!

     

    Managed to log in to my wireless router (address is normally something like http://192.168.00.01) and changed two things.

     

    1) Am now using WEP rather than WPA

    2) Changed the channel on the wireless settings to channel 3 (was on 10 previously)

     

    Not sure which was the most significant change but have now had uninterupted connection for 2 weeks - nothing short of a miracle after the headaches I've been having for the previous month!

     

    Think one of the important things to mention is that my wireless connection is through VIRGIN MEDIA (this seems to be a common factor with MBP connection problems) and the wireless router provided seems to drop the connection from time and this plays havoc with the macbook's airport system - as applecare themselves told me, "the macbook is very sensitive to dropouts in wireless connection" - no kidding!

     

    Also note: apparantly WEP is an older type of encryption and not as secure as WPA, I personally feel I'm willing to take that risk for a more stable connection but you may wish to investigate that further? Also by the way, was no significance in choosing 'channel 3' in the wireless settings, just tried at random and it seemed to work. You may find a different channel works for you so something else to try I guess?

     

    Really hope this helps someone.

  • davidfromlisle Calculating status...

    My wireless connection drops for a few seconds and picks back up automatically.  VERY ANNOYING!!!  Its a joke, has been doing it since I bought the computer 1.5 years ago, figuring someday a OS update would fix the issue but no.  Im a computer tech that knows a lot about whats going on and it seems to be an OS issue.  Ive tried all of Apples tricks and none work.  Why should I have to be doing all kinds of tricks anyhow?  I have my computer setup to dual boot with Win7 and when on Windows it has NEVER happened, not once.  So Windows 7 works fine but OSX doesnt?  The arogance of Apple is getting old, VERY poor customer support. its to bad the Apple community just lets Apple do whatever and never hold them accountable, they just run out and buy the next product.  Apple people just say, turn on and off wifi (no big deal), change channels all the time, reconfigure your router, tell all your neighbors to turn off their routers, if Windows was having the issue Apple heads would be laughing and laughing.  I like some of Apples products but until they stop the arrogant crap of nothing is wrong we are Apple Im not paying up for their "crap" anymore.  I loved their products when Apple was small but since they have gotten big they just try to push products out to make Jobs $$$ and quality has suffered.  The major problem is Apple never fesses up to anything unless there is a lawsuit or Congress comes knocking.  Just a matter of time before the consumer wises up and Apple takes a fall.  Its to bad I used to recommend Apple products but I can no longer put my name out there in support of Apple.

  • davidfromlisle Level 1 Level 1 (0 points)

    My wireless connection drops for a few seconds and picks back up automatically.  VERY ANNOYING!!!  Its a joke, has been doing it since I bought the computer 1.5 years ago, figuring someday a OS update would fix the issue but no.  Im a computer tech that knows a lot about whats going on and it seems to be an OS issue.  Ive tried all of Apples tricks and none work.  Why should I have to be doing all kinds of tricks anyhow?  I have my computer setup to dual boot with Win7 and when on Windows it has NEVER happened, not once.  So Windows 7 works fine but OSX doesnt?  The arogance of Apple is getting old, VERY poor customer support. its to bad the Apple community just lets Apple do whatever and never hold them accountable, they just run out and buy the next product.  Apple people just say, turn on and off wifi (no big deal), change channels all the time, reconfigure your router, tell all your neighbors to turn off their routers, if Windows was having the issue Apple heads would be laughing and laughing.  I like some of Apples products but until they stop the arrogant crap of nothing is wrong we are Apple Im not paying up for their "crap" anymore.  I loved their products when Apple was small but since they have gotten big they just try to push products out to make Jobs $$$ and quality has suffered.  The major problem is Apple never fesses up to anything unless there is a lawsuit or Congress comes knocking.  Just a matter of time before the consumer wises up and Apple takes a fall.  Its to bad I used to recommend Apple products but I can no longer put my name out there in support of Apple.

  • vwg Calculating status...

    I found a solution! For me at least. I posted in this thread a few weeks ago after buying a brand new 2011 Macbook Pro. Had the same problems--when using wireless, websites either loaded slowly or connection would drop regularly. Very annoying.

     

    My solution: replacing my old 2.4 gHz G/B router with a brand new 2.4 + 5 gHz N router. I went with a netgear N600.

     

    I am now very pleased. Unfortunately, I think I've seen other people in this thread who replaced their routers and it still didn't work for them, which leads me to think this won't work for everyone. But this (so far) has worked for me. Just thought I'd share. And who knows--maybe the reason mac tech support and genius bar people have been unhelpful is because they are using newer routers which work with the macbook pros! That's just my guess anyways.

  • Adrian J. Calculating status...

    I'm telling you guys...if you want to relieve your suffering, do what vwg did.

     

    REPLACE YOUR ROUTER. You can either wait for an indiffinite amount of time for Apple to address the issue...or spend $50-$100 to replace your router and not only live problem-free, but probably improve your intranet networking speeds in the process.

     

    I know it's not what people want to hear.  I understand that.  At the same time, I've been dealing with such issues with Mac producs (as well as products from various PC makers) for years and have found these kind of wifi issues happen depending on the firmware of the wifi card, the firmware on the router, and the wireless security implemented.  Somtimes there is a conflict there which causes unexpected issues (like dropping wifi).  It may be Apple's fault...but it may be your wireless router (buggy firmware is common among routers and is KNOWN to cause problems with some wifi card brands/firmwares and not others).  If it's the later, not only are you blaming the wrong party for the problems, but you're also not going to get the fixes you're waiting on.

     

    Pro-tip: If you want to "fix" this issue TODAY, go pick yourself up a good router.  vwg has found good success with the N600.  I'm having no trouble with my WNDR3700.  Both are Netgear products and can be picked up either new or refurbished.  Of all the people posting complaints, I've yet to see anyone complain who owned either of these routers.  Call it a coincidence if you want to.

     

    Now, you can continue waiting if you like.  It's quite possible that this is Apple's fault and they can and will issue some sort of firmware upgrade for the wireless card that will fix the issue for your routers.  That may happen tomorrow...or 3 months from now.  But it's also possible that Apple has nothing to do with this and that there are simply some incompatabilities with your router. 

     

    I challenge all of you to go pick up a router owned by someone who IS NOT HAVING ISSUES...and see if your issues persist.  Buy from someplace like Best Buy or Amazon who has a liberal return policy.  If you still have wifi issues with a WNDR3700, N600 or similar, return it and let us know.

     

    As of right now, few people are disclosing (1) the router they own, (2) if its firmware is up-to-date, and (3) what wireless security type they're employing.  That's a big opportunity missed, as we may have been able to establish a pattern beyond Apple's computers that may be causing the issues.

     

    Anyway, you have your options:  Return/sell the computer, try a new & better router, or continue waiting indiffinitely for a fix that may or may never come (again, we really haven't established for a fact whether or not the computers are the problem in the first pace).

1 ... 31 32 33 34 35 ... 65 Previous Next

Actions

More Like This

  • Retrieving data ...

Related Articles

Bookmarked By (22)

Legend

  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.