My 2 week old MacBook Pro 13 inch has no issues at all whatsoever connecting. Sorry if anyone is having issues, sucks when your stuff does not work right.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
2011 MacBook Pros have network issues (Confirmed by Apple)
- Thread starter lundh
- Start date
- Sort by reaction score
Negative. Use PingTest.net, not the built in pinging utility.
Here is my result with my Thunderbolt set as a hotspot and my MacBook Pro 2011 connected:
Here is the same test - same server - with my Airport Extreme bought late 2010/early 2011, same MacBook Pro:
As I stated earlier, significantly more jitter (which is what you guys are really seeing) than the Airport. Though I don't see it nearly as erratic as you guys do. I suspect you're also having some other interference going on.
TO the one with the AEBS: How do you have it configured and how is your Mac talking to it?
In my case I have an isolated 5GHz SSID, and only the computers connect to it. So my Pro, Air, and iMac all are connecting 5GHz Wireless N, the Extreme is not doing anything but 802.11n and it's running in isolated mode with increased output.
Every other wireless device connects to the Time Capsule, which is running in isolated 2.4GHz and bridged over to the Extreme. That way there is no possibility of interference between the devices.
I run the two radios (2.4 an 5 GHz) in in the same network. I use wide channels and I have tried both with and without interface robustness. 100% transmit power and low mulitcast rate, automatic radio mode.
I have tried many different channels and as I said before, other networks with unknown configurations.
I use one radio at 5GHz for computers, all my other devices connect to the other radio using G. I'm using the 5GHz band as part of a WDS with 2 additional AEBS.
Either way, I consider this a problem with my MBP. I've had my AEBS configured this way since it was released and it works perfectly with my other MBP, my Mac Pro, and my wife's HP netbook. Only the new MBP has the erratic pings.
I can also switch the new MBP to the G radio and the problem follows /continues. I can take the MBP to different networks, both public and private. Again, the ping problem follows the MBP.
Both of you run PingTest.net and post results - local and remote, instead of the built in ping app. If it returns more stable than the built-in app it could point to a software/firmware issue rather than an actual defect. If it's just as erratic, then it points to a defect with your MBP - but not a global issue as it can't be replicated by others.
It's been replicated by a lot of folks that haven't bothered with this thread. That's why I even tried to ping. There are absolutely zero reasons that I would have noticed this on my own.
Damn. I have owned this early 2011 Macbook Pro for over one month now and until the very moment I read this thread I had excellent wireless performance. One second after reading the thread my wireless performance became soooooooo sloooooow.
Anyone want to buy a one month old computer really cheap.
Anyone want to buy a one month old computer really cheap.
Using Network Utility, my local ping is quite erratic:
But using PingTest.net, it looks good:
That is weird...
Code:
PING 192.168.0.1 (192.168.0.1): 56 data bytes
64 bytes from 192.168.0.1: icmp_seq=0 ttl=64 time=30.265 ms
64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=54.592 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=3.522 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=2.797 ms
64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=22.907 ms
64 bytes from 192.168.0.1: icmp_seq=5 ttl=64 time=46.505 ms
64 bytes from 192.168.0.1: icmp_seq=6 ttl=64 time=70.560 ms
64 bytes from 192.168.0.1: icmp_seq=7 ttl=64 time=94.310 ms
64 bytes from 192.168.0.1: icmp_seq=8 ttl=64 time=15.645 ms
64 bytes from 192.168.0.1: icmp_seq=9 ttl=64 time=39.420 ms
--- 192.168.0.1 ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 2.797/38.052/94.310/27.921 msBut using PingTest.net, it looks good:
That is weird...
I did 100 pings and yes it's all over the place.
However, I also transfer a lot of files and I've never had any issues.
And I'm connect to my wireless via 5GHz.
Code:
Ping has started
PING 192.168.1.1 (192.168.1.1): 56 data bytes
64 bytes from 192.168.1.1: icmp_seq=0 ttl=255 time=0.773 ms
64 bytes from 192.168.1.1: icmp_seq=1 ttl=255 time=144.242 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=255 time=0.775 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=255 time=0.965 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=255 time=0.903 ms
64 bytes from 192.168.1.1: icmp_seq=5 ttl=255 time=136.989 ms
64 bytes from 192.168.1.1: icmp_seq=6 ttl=255 time=3.449 ms
64 bytes from 192.168.1.1: icmp_seq=7 ttl=255 time=0.978 ms
64 bytes from 192.168.1.1: icmp_seq=8 ttl=255 time=208.179 ms
64 bytes from 192.168.1.1: icmp_seq=9 ttl=255 time=1.087 ms
64 bytes from 192.168.1.1: icmp_seq=10 ttl=255 time=51.295 ms
64 bytes from 192.168.1.1: icmp_seq=11 ttl=255 time=279.254 ms
64 bytes from 192.168.1.1: icmp_seq=12 ttl=255 time=200.620 ms
64 bytes from 192.168.1.1: icmp_seq=13 ttl=255 time=122.038 ms
64 bytes from 192.168.1.1: icmp_seq=14 ttl=255 time=44.070 ms
64 bytes from 192.168.1.1: icmp_seq=15 ttl=255 time=271.913 ms
64 bytes from 192.168.1.1: icmp_seq=16 ttl=255 time=0.762 ms
64 bytes from 192.168.1.1: icmp_seq=17 ttl=255 time=0.981 ms
64 bytes from 192.168.1.1: icmp_seq=18 ttl=255 time=36.500 ms
64 bytes from 192.168.1.1: icmp_seq=19 ttl=255 time=264.517 ms
64 bytes from 192.168.1.1: icmp_seq=20 ttl=255 time=0.868 ms
64 bytes from 192.168.1.1: icmp_seq=21 ttl=255 time=107.376 ms
64 bytes from 192.168.1.1: icmp_seq=22 ttl=255 time=28.538 ms
64 bytes from 192.168.1.1: icmp_seq=23 ttl=255 time=1.011 ms
64 bytes from 192.168.1.1: icmp_seq=24 ttl=255 time=3.453 ms
64 bytes from 192.168.1.1: icmp_seq=25 ttl=255 time=3.400 ms
64 bytes from 192.168.1.1: icmp_seq=26 ttl=255 time=21.320 ms
64 bytes from 192.168.1.1: icmp_seq=27 ttl=255 time=249.912 ms
64 bytes from 192.168.1.1: icmp_seq=28 ttl=255 time=1.091 ms
64 bytes from 192.168.1.1: icmp_seq=29 ttl=255 time=92.632 ms
64 bytes from 192.168.1.1: icmp_seq=30 ttl=255 time=0.924 ms
64 bytes from 192.168.1.1: icmp_seq=31 ttl=255 time=66.027 ms
64 bytes from 192.168.1.1: icmp_seq=32 ttl=255 time=27.513 ms
64 bytes from 192.168.1.1: icmp_seq=33 ttl=255 time=1.808 ms
64 bytes from 192.168.1.1: icmp_seq=34 ttl=255 time=6.633 ms
64 bytes from 192.168.1.1: icmp_seq=35 ttl=255 time=0.776 ms
64 bytes from 192.168.1.1: icmp_seq=36 ttl=255 time=156.727 ms
64 bytes from 192.168.1.1: icmp_seq=37 ttl=255 time=78.134 ms
64 bytes from 192.168.1.1: icmp_seq=38 ttl=255 time=4.261 ms
64 bytes from 192.168.1.1: icmp_seq=39 ttl=255 time=228.007 ms
64 bytes from 192.168.1.1: icmp_seq=40 ttl=255 time=149.389 ms
64 bytes from 192.168.1.1: icmp_seq=41 ttl=255 time=71.130 ms
64 bytes from 192.168.1.1: icmp_seq=42 ttl=255 time=299.413 ms
64 bytes from 192.168.1.1: icmp_seq=43 ttl=255 time=220.991 ms
64 bytes from 192.168.1.1: icmp_seq=44 ttl=255 time=142.219 ms
64 bytes from 192.168.1.1: icmp_seq=45 ttl=255 time=3.418 ms
64 bytes from 192.168.1.1: icmp_seq=46 ttl=255 time=3.357 ms
64 bytes from 192.168.1.1: icmp_seq=47 ttl=255 time=213.477 ms
64 bytes from 192.168.1.1: icmp_seq=48 ttl=255 time=0.819 ms
64 bytes from 192.168.1.1: icmp_seq=49 ttl=255 time=56.230 ms
64 bytes from 192.168.1.1: icmp_seq=50 ttl=255 time=284.931 ms
64 bytes from 192.168.1.1: icmp_seq=51 ttl=255 time=1.012 ms
64 bytes from 192.168.1.1: icmp_seq=52 ttl=255 time=127.605 ms
64 bytes from 192.168.1.1: icmp_seq=53 ttl=255 time=48.865 ms
64 bytes from 192.168.1.1: icmp_seq=54 ttl=255 time=277.468 ms
64 bytes from 192.168.1.1: icmp_seq=55 ttl=255 time=0.871 ms
64 bytes from 192.168.1.1: icmp_seq=56 ttl=255 time=0.930 ms
64 bytes from 192.168.1.1: icmp_seq=57 ttl=255 time=41.399 ms
64 bytes from 192.168.1.1: icmp_seq=58 ttl=255 time=269.926 ms
64 bytes from 192.168.1.1: icmp_seq=59 ttl=255 time=1.838 ms
64 bytes from 192.168.1.1: icmp_seq=60 ttl=255 time=113.691 ms
64 bytes from 192.168.1.1: icmp_seq=61 ttl=255 time=34.000 ms
64 bytes from 192.168.1.1: icmp_seq=62 ttl=255 time=262.525 ms
64 bytes from 192.168.1.1: icmp_seq=63 ttl=255 time=0.996 ms
64 bytes from 192.168.1.1: icmp_seq=64 ttl=255 time=1.256 ms
64 bytes from 192.168.1.1: icmp_seq=65 ttl=255 time=26.770 ms
64 bytes from 192.168.1.1: icmp_seq=66 ttl=255 time=255.427 ms
64 bytes from 192.168.1.1: icmp_seq=67 ttl=255 time=176.786 ms
64 bytes from 192.168.1.1: icmp_seq=68 ttl=255 time=3.383 ms
64 bytes from 192.168.1.1: icmp_seq=69 ttl=255 time=19.919 ms
64 bytes from 192.168.1.1: icmp_seq=70 ttl=255 time=247.922 ms
64 bytes from 192.168.1.1: icmp_seq=71 ttl=255 time=1.460 ms
64 bytes from 192.168.1.1: icmp_seq=72 ttl=255 time=90.964 ms
64 bytes from 192.168.1.1: icmp_seq=73 ttl=255 time=12.212 ms
64 bytes from 192.168.1.1: icmp_seq=74 ttl=255 time=240.421 ms
64 bytes from 192.168.1.1: icmp_seq=75 ttl=255 time=0.708 ms
64 bytes from 192.168.1.1: icmp_seq=76 ttl=255 time=3.470 ms
64 bytes from 192.168.1.1: icmp_seq=77 ttl=255 time=4.841 ms
64 bytes from 192.168.1.1: icmp_seq=78 ttl=255 time=0.931 ms
64 bytes from 192.168.1.1: icmp_seq=79 ttl=255 time=0.838 ms
64 bytes from 192.168.1.1: icmp_seq=80 ttl=255 time=75.813 ms
64 bytes from 192.168.1.1: icmp_seq=81 ttl=255 time=1.832 ms
64 bytes from 192.168.1.1: icmp_seq=82 ttl=255 time=225.668 ms
64 bytes from 192.168.1.1: icmp_seq=83 ttl=255 time=147.161 ms
64 bytes from 192.168.1.1: icmp_seq=84 ttl=255 time=68.463 ms
64 bytes from 192.168.1.1: icmp_seq=85 ttl=255 time=296.774 ms
64 bytes from 192.168.1.1: icmp_seq=86 ttl=255 time=0.984 ms
64 bytes from 192.168.1.1: icmp_seq=87 ttl=255 time=0.974 ms
64 bytes from 192.168.1.1: icmp_seq=88 ttl=255 time=61.846 ms
64 bytes from 192.168.1.1: icmp_seq=89 ttl=255 time=289.631 ms
64 bytes from 192.168.1.1: icmp_seq=90 ttl=255 time=211.044 ms
64 bytes from 192.168.1.1: icmp_seq=91 ttl=255 time=0.938 ms
64 bytes from 192.168.1.1: icmp_seq=92 ttl=255 time=55.383 ms
64 bytes from 192.168.1.1: icmp_seq=93 ttl=255 time=0.917 ms
64 bytes from 192.168.1.1: icmp_seq=94 ttl=255 time=0.823 ms
64 bytes from 192.168.1.1: icmp_seq=95 ttl=255 time=125.305 ms
64 bytes from 192.168.1.1: icmp_seq=96 ttl=255 time=46.748 ms
64 bytes from 192.168.1.1: icmp_seq=97 ttl=255 time=275.325 ms
64 bytes from 192.168.1.1: icmp_seq=98 ttl=255 time=0.898 ms
64 bytes from 192.168.1.1: icmp_seq=99 ttl=255 time=0.823 ms
--- 192.168.1.1 ping statistics ---
100 packets transmitted, 100 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.708/84.519/299.413/100.894 msHowever, I also transfer a lot of files and I've never had any issues.
And I'm connect to my wireless via 5GHz.
Results on a 15.5" 2.0ghz 2011 MBP. This is three floors below and outside the house on the opposite side from the WAN source connected to an extension network. I've never been particularly good with networking, it took a lot of research and some equipment upgrades to consistently pull 4mb/s downloads off remote servers at this distance from the router. I know just enough to realize that it takes a good deal of effort to get a good wifi setup, and I have a feeling that a lot of people haven't done the homework and want to return their fancy apple laptops now because some random internet source informed them that their top of the line machine is secretly a piece of ****.
I'm not saying a defect isn't possible, I'm just saying home wifi networks are in my experience usually poorly set up/administered, and your 50 dollar bargain N-router is more likely to blame than your state of the art computer system.
... also bearing in mind some test conditions. 802.11g, with direct line of site can function better than 802.11n.
I don't recall anyone saying they wanted to return the unit over the issue, which for the most part is benign.
I always enjoy the naysayer posts. If you don't have an issue, congratulations. Unfortunately, the issue is real and not a product of people's imaginations, poor gear, or embarrassing networking skills.
Regardless of your feelings on the quality of Apple's own networking gear, I think we can all agree that it should work just fine with their notebooks, no?
Well said.
I haven't done any pinging yet, but mine does randomly drop it's connection for no apparent reason while my phone/other Macs all hold onto theirs and download content just fine.
I'm hoping this is a firmware/energy saving issue or whatever as I reeeeally don't want to have to exchange my system.
Last edited:
I just ran the test at www.pingtest.net and got the following:
With nothing happening except the ping test:
Ping: 352ms
Jitter: 162ms
Running ping test while downloading Ubuntu at the same time:
Ping: 125ms
Jitter: 16ms
This is 5GHz about 10 feet from the AEBS
With nothing happening except the ping test:
Ping: 352ms
Jitter: 162ms
Running ping test while downloading Ubuntu at the same time:
Ping: 125ms
Jitter: 16ms
This is 5GHz about 10 feet from the AEBS
Here's what I got from Pingtest.net
Ping: 65 ms
Jitter:3ms
Which I guess doesn't seem to bad compared to some others that have posted?
But like I said, I haven't really had speed issues, just random connection drops.
Ping: 65 ms
Jitter:3ms
Which I guess doesn't seem to bad compared to some others that have posted?
But like I said, I haven't really had speed issues, just random connection drops.
I have really no idea about how pingtest.net works but the issue is easiest identified by using the normal ping command in a terminal. Why use a separate tool when we have a tool built in that makes it easy to identify the issue?
My computer actually borders on useless when connected to a wireless network. It is frequently killing persistent connections. I have to keep reseting my network connection to have wireless access working even for just a few hours.
Apple refuses to replace/repair my computer due to the fact that "it wont solve the issue". I am a bit confused by this statement when so many of you have no noticable issues at all with your computers and mine is as bad as it is.
Apple even went as far as offered me a refund (I did not ask for it) instead of doing any more repairs. I really dont have any option other then accepting at this point. I need a stable wireless connection and my current computer is not capable of that.
It sounds like my MBP is particulary bad and a replacement computer might very well reduce the issue to something I can handle, but Apple wont let me replace it.
My computer actually borders on useless when connected to a wireless network. It is frequently killing persistent connections. I have to keep reseting my network connection to have wireless access working even for just a few hours.
Apple refuses to replace/repair my computer due to the fact that "it wont solve the issue". I am a bit confused by this statement when so many of you have no noticable issues at all with your computers and mine is as bad as it is.
Apple even went as far as offered me a refund (I did not ask for it) instead of doing any more repairs. I really dont have any option other then accepting at this point. I need a stable wireless connection and my current computer is not capable of that.
It sounds like my MBP is particulary bad and a replacement computer might very well reduce the issue to something I can handle, but Apple wont let me replace it.
Sorry this comment does not really add much to the quite in depth discussion.
I bought my MBP 2 days ago now, and I have to it takes forever to obtain a
wifi network signal, and I often have to manually connect via selecting the network, even though preferences have been set.
Once it is connected it seems to be ok-ish....although if I open a new tab it can take a while to load a page....
Also if I close and then re-open the lid, again it takes a long time to find networks, and once again I have to manually select the network, but it finally connected after a considerable delay
Not sure I am that happy I sold my 2009 MBP and replaced it with this one now.....in my opinion wifi network accessibility and reliability are key.
I bought my MBP 2 days ago now, and I have to it takes forever to obtain a
wifi network signal, and I often have to manually connect via selecting the network, even though preferences have been set.
Once it is connected it seems to be ok-ish....although if I open a new tab it can take a while to load a page....
Also if I close and then re-open the lid, again it takes a long time to find networks, and once again I have to manually select the network, but it finally connected after a considerable delay
Not sure I am that happy I sold my 2009 MBP and replaced it with this one now.....in my opinion wifi network accessibility and reliability are key.
What Anand said is if you have the latest Airport Extreme with a three stream antenna that matches up to the 2011 MBP three stream antenna for greater speed and range.
Thats exactly the wrong thing to use. You are using the public internet when using services like this and the route varies. There is no way you will get a consistent test this way.
You hit the nail on the head there. I'm really sick and tired of all these Apple zealots. My brand-new "winter 2011" 15" MBP has been presenting almost all those issues related here, erratic pings, connection drops etc... and when someone comes to share his experience or alert others about them, one can be sure that almost immediately a bunch of Apple diehards will show-up to summarily dismiss any complaint as whining or offer the most preposterous reasons for the malfunction.
I've been a consumer of Apple products since 1999 and please, don't dare to challenge me to talk about Mac Pro (early 2008) power supply issues as I have a long, long history of bitter disappointment and regret for having bought it.