Skip navigation

new macbook pro 2011 weak and dropping wireless connection

232687 Views 965 Replies Latest reply: Jan 7, 2014 3:13 AM by BananaMacintosh RSS
  • mr-riot Calculating status...

    I hope the 10.6.8 update will solve this problem!

     

    any beta-users here?!

  • maclover01 Level 1 Level 1 (0 points)

    same problem............this need a fixed asap

  • putlink Calculating status...

    Have the same problem on both my MBP 15. On the older model (2009) it's so bad so it almost no idea to use the network. Have a Cisco router with latest firmware and the latest os x updates installed.

  • Chino81 Calculating status...

    Im reading this forum since march 2011, and still cant decide...buy or not lol.

  • mal808 Calculating status...

    This is driving me nuts!

     

    Running OSX I've got no network connection 99% of the time.

    Everything else on my network is fine.

    Running windows7 on the macbook pro is fine, the wifi works perfectly.

    I didn't buy this thing to spend the majority of my time on windows 7.

    what a letdown. I'm advising anyone who asks not to bother with a macbook pro. With the cost of these machines this sort of problem is unacceptable.

     

    I really hope it's sorted soon. 

  • bitserf Calculating status...

    Okay, some additional information:

     

    Even with my new Airport Extreme access point, today I saw the latency issue crop up again.

     

    I had a look at my Airport settings in System Profiler, and noticed that unlike usual, the MacBook was using a 2.4Ghz channel.

     

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

    Request timeout for icmp_seq 21

    Request timeout for icmp_seq 22

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

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

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

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

    Request timeout for icmp_seq 27

    Request timeout for icmp_seq 28

     

     

    So I reconfigured the Airport Extreme to have a separate SSID for 5Ghz, and connected to that explicitly using the MBP:

     

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

     

    In both cases I was busy playing a 1080p MKV over the air.

     

    So there you have it.

     

    It looks like the problem is that the new 2011 MBPs have problems when using anything except a 5Ghz 802.11n WiFi channel.

     

    Apparently one of the areas 10.6.8 looks at is AirPort, I hope for the rest of you guy's sakes that this will be addressed then, as the solution should not be to buy a new router.

     

    At least, for myself, I now have an easy way of testing whether they have really fixed it.

     

    Everybody who has a 5Ghz capable router, are you able to confirm that this is the case for you too? e.g. force the MBP to use a 2.4ghz channel like 11, and then check what your latency is while using the network heavily, and compare it to 5Ghz numbers.

  • jensfrommannheim Calculating status...

    same problem!

  • MilesR Calculating status...

    Bitserf...I have a dual band router (Cisco/Linsys E3000), with an 802.11n network (5Ghz) and an 802.11g network (2.4Ghz - channel 1 - set by auto scan).

    My ping rates are the same (i.e. within normal ranges <5ms) when pinging local IPs on both networks using my 2011 Macbook Pro (since the latest software update).

     

    However, every 20 or so pings when using the 802.11g network drop out, so you may be on to something with that.

    It also would explain why in the Apple store they couldn't reproduce my network dropout issues (I got the Macbook before I bought the new router), since their wireless networks are all running at 5Ghz.

     

    Thankfully I didn't have to buy the new router because of the issues, but because I changed broadband type (ADSL->Fibre), plus I wanted a dual band gigabit router anyway

  • msm msm Level 1 Level 1 (0 points)

    @bitserf... I´d like to follow your advice, but don´t know how to configure my Airport Extreme?  How can I

    "So I reconfigured the Airport Extreme to have a separate SSID for 5Ghz, and connected to that explicitly using the MBP"?

    Thanks!

    M

  • bitserf Level 1 Level 1 (0 points)

    @msm msm, here's what I did.

     

    1. Start Airport Utility (it's in Applications -> Utilities).
    2. Selected my Airport Express in the pane on the left.
    3. Clicked Manual Setup.
    4. Switched to the Wireless tab.
    5. Clicked Wireless Network Options.
    6. Ticked 5Ghz Network Name.
    7. Clicked Done and then Update to apply the settings.

     

    After the Airport Express finished restarting, I selected the new network from the Airport dropdown (I gave it a name ending with " (5Ghz)".

     

    I also dragged the 5Ghz network to the top of my preferred wireless networks in the Networks configuration preference pane in System Preferences, so that it uses it by default.

     

    Hope this helps.

  • msm msm Level 1 Level 1 (0 points)

    Hey bitserf,

    thanks a lot.  I made the changes you suggested, but I´m not sure if my situation is better or not.

    Thats because I´ve got the Extreme Dual band... (now with 5gz, but I am also extending it with an airport express... and I cant find any configuration for setting the express to 5gz...  or perhaps it is not necessary?

     

    Unfortunately, i am not real up to date about Airport set ups.

    Still thanks for your quick reply.

  • sendas Calculating status...

    Hi

     

    This problem is fixed with Snow Leopard update build 10.6.8.

     

    I've installed the most recent build and it seems that the problems are gone

  • yozhbk Level 1 Level 1 (0 points)

    i hope you are right.

  • MacFreak Calculating status...

    Hi Sendas...

    Is update 10.6.8 out for install?

    I was just trying to go through the Support Section of Apple Mac website, and couldn't see the update 10.6.8 still.. Are you sure it is out still? Have you installed it? Can you help me with its direct link to see the list of technical changes and problems addressed in this update.

     

    Thanks!

  • Adrian J. Calculating status...

    No, it's not out for consumers.

     

    A new build of 10.6.8 is out for developers, but that's the extent.  We'll have to wait and see.

1 ... 34 35 36 37 38 ... 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.