You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

new macbook pro 2011 weak and dropping wireless connection

Just looked throught this part of the forum and found out there are a lot of people out there which seem to have the same problem as me.

I purchased a new modell 2011 MBP on the very first day from our apple store.
At home, sitting directly beside the wireless router I didn´t noticed anything wrong.
I have got beside of the Mac OS a bootcamp Prt. with Windows 7 on it and everythign works fine so far.

Five days after purchased I started traveling on business and at present we are for some weeks in Melbourne. Were having a wireless connection in our appartement and here I have got massiv problems with my connection.

We are having altogether four windows mashines with us, my IPad, my Iphone, another HTC smartphone, and my new Macbook.

All the other devices connecting to our room wireless without problems. The net strengh is not fantastic but the other devices bringing it up to four bars on the windows wireless symbol in the task bar. None of the other computers where ever loosing the connection.

Only my macbook can not make it over three bars and its going on and off. Donwloads fail freuquently because the conection is interrupted more than one times..
In my opinion this problem is even worse on the Windows OS and a bit better but far away from beeing good and acpetable on the Mac Os.
I hope its only a driver issue and there is no hardware problem with the new mashine. Other than this I love the new notebook and I am very satisfied with its performance.

Iphone 4, Ipad 1 ,Macbook pro 13, I 5, 8GB, early 2011, Windows 7, Mac OS

Posted on Mar 8, 2011 9:00 PM

Reply
968 replies

Apr 1, 2011 4:13 AM in response to TomB01

This is the Copy of the log taken from the ping test which got done IN The Apple Store ON there Apple Wireless Net, directly after the exchange of the network Card in my Macbook Pro 2011.

The results looking exactly the same like the ones with the "OLD" network Card:
As a comparison , there was an old Model Macbook stood up beside my 2011 Macbook and started the same Ping test at the same time on the same server: The results of this Macbook were all stable and consistent on about 20!


„Ping“ wurde gestartet …

PING www.l.google.com (74.125.237.84): 56 data bytes
64 bytes from 74.125.237.84: icmp_seq=0 ttl=57 time=23.647 ms
64 bytes from 74.125.237.84: icmp_seq=1 ttl=57 time=21.550 ms
64 bytes from 74.125.237.84: icmp_seq=2 ttl=57 time=21.353 ms
64 bytes from 74.125.237.84: icmp_seq=3 ttl=57 time=44.431 ms
64 bytes from 74.125.237.84: icmp_seq=4 ttl=57 time=79.603 ms
64 bytes from 74.125.237.84: icmp_seq=5 ttl=57 time=37.282 ms
64 bytes from 74.125.237.84: icmp_seq=6 ttl=57 time=23.566 ms
64 bytes from 74.125.237.84: icmp_seq=7 ttl=57 time=19.740 ms
64 bytes from 74.125.237.84: icmp_seq=8 ttl=57 time=53.347 ms
64 bytes from 74.125.237.84: icmp_seq=9 ttl=57 time=93.421 ms
64 bytes from 74.125.237.84: icmp_seq=10 ttl=57 time=33.354 ms
64 bytes from 74.125.237.84: icmp_seq=11 ttl=57 time=19.858 ms
64 bytes from 74.125.237.84: icmp_seq=12 ttl=57 time=18.941 ms
64 bytes from 74.125.237.84: icmp_seq=13 ttl=57 time=70.164 ms
64 bytes from 74.125.237.84: icmp_seq=14 ttl=57 time=105.977 ms
64 bytes from 74.125.237.84: icmp_seq=15 ttl=57 time=47.099 ms
64 bytes from 74.125.237.84: icmp_seq=16 ttl=57 time=90.973 ms
64 bytes from 74.125.237.84: icmp_seq=17 ttl=57 time=20.352 ms
64 bytes from 74.125.237.84: icmp_seq=18 ttl=57 time=21.804 ms
64 bytes from 74.125.237.84: icmp_seq=19 ttl=57 time=118.632 ms
64 bytes from 74.125.237.84: icmp_seq=20 ttl=57 time=19.873 ms
64 bytes from 74.125.237.84: icmp_seq=21 ttl=57 time=103.192 ms
64 bytes from 74.125.237.84: icmp_seq=22 ttl=57 time=41.630 ms
64 bytes from 74.125.237.84: icmp_seq=23 ttl=57 time=19.347 ms
64 bytes from 74.125.237.84: icmp_seq=24 ttl=57 time=28.255 ms
64 bytes from 74.125.237.84: icmp_seq=25 ttl=57 time=69.830 ms
64 bytes from 74.125.237.84: icmp_seq=26 ttl=57 time=22.834 ms
64 bytes from 74.125.237.84: icmp_seq=27 ttl=57 time=18.263 ms
64 bytes from 74.125.237.84: icmp_seq=28 ttl=57 time=101.264 ms
64 bytes from 74.125.237.84: icmp_seq=29 ttl=57 time=26.285 ms
64 bytes from 74.125.237.84: icmp_seq=30 ttl=57 time=85.020 ms
64 bytes from 74.125.237.84: icmp_seq=31 ttl=57 time=22.101 ms
64 bytes from 74.125.237.84: icmp_seq=32 ttl=57 time=67.099 ms
64 bytes from 74.125.237.84: icmp_seq=33 ttl=57 time=24.419 ms
64 bytes from 74.125.237.84: icmp_seq=34 ttl=57 time=50.322 ms
64 bytes from 74.125.237.84: icmp_seq=35 ttl=57 time=109.922 ms
64 bytes from 74.125.237.84: icmp_seq=36 ttl=57 time=26.417 ms
64 bytes from 74.125.237.84: icmp_seq=37 ttl=57 time=24.036 ms
64 bytes from 74.125.237.84: icmp_seq=38 ttl=57 time=22.851 ms
64 bytes from 74.125.237.84: icmp_seq=39 ttl=57 time=64.912 ms
64 bytes from 74.125.237.84: icmp_seq=40 ttl=57 time=106.853 ms
64 bytes from 74.125.237.84: icmp_seq=41 ttl=57 time=49.778 ms
64 bytes from 74.125.237.84: icmp_seq=42 ttl=57 time=97.443 ms
64 bytes from 74.125.237.84: icmp_seq=43 ttl=57 time=32.269 ms
64 bytes from 74.125.237.84: icmp_seq=44 ttl=57 time=79.563 ms
64 bytes from 74.125.237.84: icmp_seq=45 ttl=57 time=21.627 ms
64 bytes from 74.125.237.84: icmp_seq=46 ttl=57 time=64.813 ms
64 bytes from 74.125.237.84: icmp_seq=47 ttl=57 time=110.568 ms
64 bytes from 74.125.237.84: icmp_seq=48 ttl=57 time=48.725 ms
64 bytes from 74.125.237.84: icmp_seq=49 ttl=57 time=89.651 ms
64 bytes from 74.125.237.84: icmp_seq=50 ttl=57 time=43.818 ms
64 bytes from 74.125.237.84: icmp_seq=51 ttl=57 time=82.670 ms
64 bytes from 74.125.237.84: icmp_seq=52 ttl=57 time=23.184 ms
64 bytes from 74.125.237.84: icmp_seq=53 ttl=57 time=22.465 ms
64 bytes from 74.125.237.84: icmp_seq=54 ttl=57 time=113.295 ms
64 bytes from 74.125.237.84: icmp_seq=55 ttl=57 time=45.248 ms
64 bytes from 74.125.237.84: icmp_seq=56 ttl=57 time=86.275 ms
64 bytes from 74.125.237.84: icmp_seq=57 ttl=57 time=57.277 ms
64 bytes from 74.125.237.84: icmp_seq=58 ttl=57 time=71.758 ms
64 bytes from 74.125.237.84: icmp_seq=59 ttl=57 time=20.378 ms
64 bytes from 74.125.237.84: icmp_seq=60 ttl=57 time=36.415 ms

Message was edited by: LaraJones

Apr 1, 2011 4:09 AM in response to LaraJones

I guess this is good and bad news all at the same time. Good news is that we know its probably not hardware (it is possible that boards, antenas, connectors or interference) bad news is that there is no fix, no acknowledgment or an ETA.... but with Apple this does not surprise me, we might get one of this firmware updates thru software update that will say fixes issue that affected small group of people. Lets give it some time.

Apr 1, 2011 4:57 AM in response to LaraJones

I have the same ping issue.

Rang apple support, fist thing they asked me, was this an issue with the Airport, I hadn't even said anything to them. not sure why they asked that. They escalated this to senior support, who then said he would escalate to Global Engineering and let me know if he hears anything back.

They suggested replacing network card etc, but I have no confidence this will fix the issue after reading this thread.

I have purchased a $20 802.11G USB network adapter (haha) for my new Mackbook Pro 15" so I can use Internet reliable. I hope Apple pays attention to these issues and releases a fix.

Apr 1, 2011 6:24 AM in response to LaraJones

Hey all, just thought I'd pop in and and contribute to the bug count. Had my laptop for almost two weeks now. Brand new 15'' MBP. Thought the internet problems might just be because my bedroom is far away from the router in my student house, however since I've gotten home I've realised this isn's the case.

Just done a ping test whilst sitting directly next to my router at home, here's the results:
Ping has started…

PING 192.168.1.254 (192.168.1.254): 56 data bytes
64 bytes from 192.168.1.254: icmp_seq=0 ttl=64 time=112.591 ms
64 bytes from 192.168.1.254: icmp_seq=1 ttl=64 time=65.703 ms
64 bytes from 192.168.1.254: icmp_seq=2 ttl=64 time=220.991 ms
64 bytes from 192.168.1.254: icmp_seq=3 ttl=64 time=215.666 ms
64 bytes from 192.168.1.254: icmp_seq=4 ttl=64 time=137.290 ms
64 bytes from 192.168.1.254: icmp_seq=5 ttl=64 time=58.428 ms
64 bytes from 192.168.1.254: icmp_seq=6 ttl=64 time=1.545 ms
64 bytes from 192.168.1.254: icmp_seq=7 ttl=64 time=208.118 ms
64 bytes from 192.168.1.254: icmp_seq=8 ttl=64 time=129.970 ms
64 bytes from 192.168.1.254: icmp_seq=9 ttl=64 time=4.161 ms
64 bytes from 192.168.1.254: icmp_seq=10 ttl=64 time=217.675 ms
64 bytes from 192.168.1.254: icmp_seq=11 ttl=64 time=201.520 ms
64 bytes from 192.168.1.254: icmp_seq=12 ttl=64 time=47.822 ms
64 bytes from 192.168.1.254: icmp_seq=13 ttl=64 time=43.240 ms
64 bytes from 192.168.1.254: icmp_seq=14 ttl=64 time=217.756 ms

192.168.1.254 ping statistics ---
15 packets transmitted, 15 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 1.545/125.498/220.991/80.891 ms

Thought the more people who say they're experiencing the problem the quicker Apple might deal with it. Would it be a good idea to ring up Apple or go in to the store and tell them I'm experiencing the problem or is the overall feel that we just need to wait for a fix?

Message was edited by: pezdispenser

Message was edited by: pezdispenser

Apr 1, 2011 6:34 AM in response to pezdispenser

Yes, pezdispenser, I think everyone that notices the problem needs to let Apple know, so they can gauge the severity of the issue. Supposedly they already are working on it, but.....

You can tell them that there are a number of other people that have already reported it, and that (famous last words) Apple Engineering is already working on it, so you just need to add your name to the list of people reporting the problem.

Apr 1, 2011 12:51 PM in response to pezdispenser

over several calls have been told to erase and install ( no change ), reset the SMC and PRAM ( temporary change ), changed the wireless netgear router channel to 1 from 6, again seemed to temporarily fix, problem came back so now we ditched the network prefs.
been told to monitor that for a couple of days and they booked me a slot in the london applestore in advance on monday, if I still get the dropouts they will send it away for a hardware test, and it's less than a month old.
all the tests so far will apparently remove the idea that the problem is software / firmware related....
and according to the apple care guy that would mean hardware......
look forward to losing a new machine for a week.....not.

Apr 1, 2011 1:03 PM in response to anguish

Sounds familiar. Have tried most of those myself, and have gotten a replacement machine as well.

Someone indicated that the problem did not exist in a Bootcamp environment (ie: when running Windows), if I can restore my bootcamp partition perhaps I can use that to provide some additional input to the issue.

Anyone have a bootcamp partition where they can test this?

Apr 1, 2011 5:50 PM in response to TomB01

For all the new folks on the thread. Here is the active case number for this issue that's been escalated to Engineering.

209718079

If your calling in to Apple Support or going to the Apple store, have your issue linked to this case so that they can see that many people are experiencing this issue and we may get more attention put on it so we can get a fix quicker.

new macbook pro 2011 weak and dropping wireless connection

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.