LaraJones
Level 1 (0 points)

Q: 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

by LaraJones,Solvedanswer
LaraJones LaraJones
Level 1 (0 points)
A:

Good morning,

Needed a moment to find my thread...the new structure...if there is any at all left is not very comfy to find your way around her in the support forum, I find....

 

News from my side....

Back home in Bavaria, back in our 32 MB Net. MacBook does not drop connection not on Bootcamp not on Mac OS Becuase of the strong link. if you look on the wireless symbol everything looks fine.

BUT

- Doing the ping test shows same horrible result like everywhere else before. Ping is going up and down, shows tomeouts.

-Downloads are very very slow considering our net speed.

-Streaming absolute NOT possible.

 

My old Fujitsu T4215 and all the other Wndows Mashines my husband uses in our net are working without any kind of problems...but we know this already, don't we????

 

I was visiting our local Apple supplier yesterday, with the paperworks about the work which was done on my MacBook in Melbourne, change of Networkcars, wihtout any change to the better.

 

Her suggested to call apple and tell them to change the logiboard next and so I did!!!! On Monday I will bring my MacBook to the apple store. Than it gets send in and I have to live ten days wihtout it.... fantastic....

 

Will keep your informed if it helps....I have got my doubts BUT what wcan we do...

Posted on Apr 16, 2011 10:03 PM

Close
LaraJones

Q: new macbook pro 2011 weak and dropping wireless connection

  • All replies
  • Helpful answers

first Previous Page 10 of 65 last Next

  • by LaraJones,

    LaraJones LaraJones Apr 1, 2011 4:01 AM in response to anguish
    Level 1 (0 points)
    Apr 1, 2011 4:01 AM in response to anguish
    Well than!!
    Thanks first at all to the Apple Store Genius Guys getting my Macbook done so fast. I got a call today that the ordered Network Card was now in stock and could get exchanged. Actually they wanted the notebook in for three days but when I wold them I had to fly back home next week one of the genius guy did the swap direct within half an hour.
    Lets repeat the story:
    I went there some days ago, One of the genius guys did the PING test and found the results shocking enough to put it down for an exchange of the defect Network Card.
    The pingtest he did there in my Macbook were looking exactly the same like the ones a lot of you where publishing here on the net.
    The guy on Thuesday did a direct comparison Pingtest between my 2011 Macbook and an older Modell Macbook Pro whch he put beside my new one. The older Model had an constant Value at about 20. The difference was horrible to watch.

    Well than after the exchange today I asked the genius Guy to make the same test again and the result is ...to say it friendly...TOTAL Frustrating.

    The Pingtest results which he showed me looked exactly the same than before. He as well put a comparison Macbook, old model, beside our new one and this older model showed exactly like the one on Thuesday constants Pings of about 20.

    I copied the ping results of my Macbook made in the Apple Store on their Wireless Network, to put them up here as this is finally proving that its certainly NOT an Router issue...
    I take it that a router in an official Apple Store is up to Date and proper set up for an Macbook.

    We tried to discus the issue further with the Genius Man, but what could he have said?????????
    He did what he could have done, he changed the Network Card, and he did it , beeing friendly, very fast for us. He run the tests and he could not say much more than:
    I have never seen an case like this before on an new Macboo Pro.

    He tried to convince me that the Ping results are not so important and unless I want to play games I could somehow live with it!!!?????? ....but he did not find an answer to the question why MY Pings are looking SO MUCH different to the Pings on HIS old Model Macbook!!!

    And that was it!
    At last, we said we would go home and test the machine in our net and so we did.

    *No changes* to before with the old Network Card.

    The Notebook drops in and out of the net, the pingtest here looks no different to the one in the Apple Store.

    I think, we did now everything we could do for now. I will go home to Germany next week and the only thing we can do is to wait for an official statement or an fix from Apple!

    I will put the Pingtests up here now for you to see what I am talking about!

    Have a nice evening everbody or a great day to the ones who just got up...
    My day is done and I am very very frustrated. I expected this outcome somehow BUT of course I hoped for the better.
    Cio Lara











    I copies them at once in a email, to safe them and I did another pingtest just here back in my apparment.

  • by LaraJones,

    LaraJones LaraJones Apr 1, 2011 4:13 AM in response to TomB01
    Level 1 (0 points)
    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

  • by yozhbk,

    yozhbk yozhbk Apr 1, 2011 4:09 AM in response to LaraJones
    Level 1 (0 points)
    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.

  • by ariliquin,

    ariliquin ariliquin Apr 1, 2011 4:57 AM in response to LaraJones
    Level 1 (0 points)
    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.

  • by pezdispenser,

    pezdispenser pezdispenser Apr 1, 2011 6:24 AM in response to LaraJones
    Level 1 (0 points)
    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

  • by TomB01,

    TomB01 TomB01 Apr 1, 2011 6:34 AM in response to pezdispenser
    Level 1 (4 points)
    Mac OS X
    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.

  • by pezdispenser,

    pezdispenser pezdispenser Apr 1, 2011 6:41 AM in response to TomB01
    Level 1 (0 points)
    Apr 1, 2011 6:41 AM in response to TomB01
    OK. I think I'll go into the Apple Store as I've not got much else to do today. By the way, I'm in the UK and just realised this is the forums on the US site (not sure if it's universal) but I'll let you know how it gets handled in a UK store.

  • by pezdispenser,

    pezdispenser pezdispenser Apr 1, 2011 9:34 AM in response to pezdispenser
    Level 1 (0 points)
    Apr 1, 2011 9:34 AM in response to pezdispenser
    Nothing but a 'wait and see' attitude. Told me to update to 10.6.7 which I have done but I assume from the comments in this thread that hasn't had much effect. Anyway told him to put my machine on the system as having this problem so that's another one added to the cause. Will give you updates if I get any.

  • by anguish,

    anguish anguish Apr 1, 2011 12:51 PM in response to pezdispenser
    Level 1 (0 points)
    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.

  • by TomB01,

    TomB01 TomB01 Apr 1, 2011 1:03 PM in response to anguish
    Level 1 (4 points)
    Mac OS X
    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?

  • by LaraJones,

    LaraJones LaraJones Apr 1, 2011 1:48 PM in response to TomB01
    Level 1 (0 points)
    Apr 1, 2011 1:48 PM in response to TomB01
    IN my bootcamp with Windows 7 the wireless problems are even worse than on the OS side!

  • by TomB01,

    TomB01 TomB01 Apr 1, 2011 3:15 PM in response to LaraJones
    Level 1 (4 points)
    Mac OS X
    Apr 1, 2011 3:15 PM in response to LaraJones
    Huh... Then maybe it IS the adapter card.....

  • by iharris,

    iharris iharris Apr 1, 2011 5:50 PM in response to TomB01
    Level 1 (0 points)
    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.

  • by iharris,

    iharris iharris Apr 1, 2011 5:52 PM in response to TomB01
    Level 1 (0 points)
    Apr 1, 2011 5:52 PM in response to TomB01
    It's not the Adapter Card itself but the firmware that's running on it.

    Older firmwares of the same card do not experience the issue.

  • by csnoel,

    csnoel csnoel Apr 1, 2011 7:23 PM in response to iharris
    Level 1 (1 points)
    Apr 1, 2011 7:23 PM in response to iharris
    Has any one gone into one of the Apple stores and checked each Macbook there to see if they are having the same problem? I am on my second one and if we are all having the same problem one would think all of the new MacBooks would have the same ping results?

    Thanks
first Previous Page 10 of 65 last Next