new macbook pro 2011 weak and dropping wireless connection

LMAO i'm so stupid I just did that ping test, got awesome results...Thats cause i'm connected via ethernet *sigh*

My Airport results, I'm guessing the top stuff doesnt matter so i'll just put the bottom bit:

1m from router:

--- ping statistics ---

10 packets transmitted, 10 packets received, 0.0% packet loss

round-trip min/avg/max/stddev = 0.999/28.046/93.832/35.729 ms

next room:

--- ping statistics ---

10 packets transmitted, 10 packets received, 0.0% packet loss

round-trip min/avg/max/stddev = 1.351/33.629/50.458/18.255 ms

I'm currently connected to D-LINK DSL-G604T. Router is in another room about 10 meters away. Wifi analyzer shows: signal strength -54, noise -86, signal to noise 0.625, data rate 54Mbps. Using battery.

Ping flood (-f) with count 10000 to router:

--- 192.168.1.1 ping statistics ---

10000 packets transmitted, 10000 packets received, 0.0% packet loss

round-trip min/avg/max/stddev = 1.264/1.738/14.287/0.234 ms

normal ping with count 100:

--- 192.168.1.1 ping statistics ---

100 packets transmitted, 100 packets received, 0.0% packet loss

round-trip min/avg/max/stddev = 1.611/177.255/403.257/128.968 ms

Hello everyone. My first post here and a first time owner of a Mac. Bought my 17" MBP (early 2011) last month and things were going really well (noslow wireless issues, etc) till last night. I have a DLINK DIR-655 router. Last night, I noticed that I haven’t updated my router firmware for a while. Decided to update from 1.21 to their latest 1.35 NA. That’s where things went south.Horrible wireless connection on my MBP (slow browsing to my NAS shares, cantplay files from my NAS, etc). I thought router does not like the new firmware first, but I started my other windows laptops and everything works fine there. Streamed a 4GB mkv file from my NAS with no issues. Installed bootcamp andWindows 7 (64 bit) on my MBP and same file streams flawlessly. However, MBP with Mac OSX... takes 15 seconds to start playing the file (using VLC) and just get stuck after every few seconds. This is horrible. I just started to love MBP. Was telling my wife that we should start replacing other machines with MacPro or MBP.

If I am reading other posts right.. I could go and buy a AirPort extreme andthat should help? Ohh DIR-655 is not allowing me to downgrade the firmware either.

Would appreciate any suggestions!

Thanks!

Well found a way to downgrade the firmware on my DIR-655. Everything seems to be back to normal.

I think the ping time inconsistencies are a non-issue. My guess is it's power management in the adapter. Try this:

ping 192.168.1.1 (or whatever your router address is) - note the ping times all over the place

now try

sudo ping -i .3 192.168.1.1 - you should see results similar to last test (the -i option sets the ping frequency, in this case the packet is sent every 3/10 of a second)

now try

sudo ping -i .22 192.168.1.1 - same results as above

NOWWWWWW TRY

sudo ping -i .2 192.168.1.1 - great 1ms ping times, and consistent

I think what is happening is once the adapter is idle for 2/10 of a second it enters some sort of low power mode. For gaming, streaming, etc. since data is continually being transferred it shouldn't be an issue. Thoughts?

I got the same result as you... works fine with ping -i .2 (most ping under 2ms)... but not with a delay higher than that...

anyway... I'm really happy to have found this thread... I was thinking that my new router was having some issues...

once it's connected, it seems to be working fine... but sometimes, I'm not even able to use the network while other users on the same network don't have any problem...

I really hope that Apple will fix this issue anytime soon...

Hi,

I got the info from the Apple Support that they are working on a fix for the ping issue, and it will come through a update or an fix via the knowledgebase, it will take some time but they gonna fix it!

That is good news. Hopefully it wont take too long this has already been frustrating enough 😊

I took my MACBOOK PRO (15-INCH, EARLY 2011) to the Genius Bar Sat. They downloaded my log file and escalated to engineering. They guy seem puzzled. I got it to replicate on all the new MBP's in the store and not on any other devices. They called me yesterday and told me that Apple called and told him they were aware of the problem and were addressing it. ???? He did not say if it was software or firmware?

I just wanted to pass this on. I hope it is fixed soon. My return period ends soon........

2011 Macbook Pro. STABLE ping results.

25 packets transmitted, 25 packets received, 0.0% packet loss

round-trip min/avg/max/stddev = 0.609/0.797/1.242/0.159 ms

Router: Netgerar WNDR3700

I think this thread would have been much more vaulable had everyone been posting their ROUTER MAKE & MODEL. I'm about 90% sure that for most people here, the issue is an issue with OS X talking to their current router than an actual problem with the computer hardware (though I retarin that 10% possibility that it IS a hardware issue for some of you). Outside chance it's an OS (driver) issue as well. Fact is, I've found over the years that routers (and their imperfect firmware) can be very finiky...even flaky...with network cards from varying years of computers.

Things to try (if you haven't already):

1.) Change the wireless security type. First of all, never use WPA2 (TKIP). Use the AES variant. If that's what you've been using, switch to WEP and test your pings. If you've been using WEP, switch to WPA2 (AES) and test the ping again.

if that doesn't help...

2.) Make sure there are no firmware updates for your router. Just visit the manufacturer's website and search for drivers for your specific make & model of router. Try step 1 again.

If all is indeed updated and you've done #1 again and still no dice...

3.) Reset the router. Hold the little button in the pinhole down for 10-20 seconds and release. The settings will be lost, so be sure to back up any special configurations you have going on. Then repeat step #1.

If still no dice...

4.) Consider buying a new router, even if only to test the theory. If you buy from a business like Best Buy, you can simply return it later if you don't want it or if it doesn't solve the problems. Worst thing that could happen is it does't work and you wasted time visiting Best Buy...while the best thing that could happen (likely) is that a new router resolves your problem.

I'd recommend the Netgear WNDR3700 (and I assume Airport Extreme is a safe bet too?). I doubt you guys will get too many hits from people who aren't having any problem because they're not looking for threads like this to discuss things in, you know? Alas, I'm here...and I can affirm with great confidence that my pings are excellent from my new Netgear WNDR3700 and my old Netgear WNR2000. I only upgraded because I wanted dual bands (highly recommended if you stream movies inside your home).

Whatever you do...from now on, you guys be sure to POST YOUR ROUTER MAKE AND MODEL. You never know...we might see a pattern form there...

it's not a router issue for sure!!!!

I have the same problem on 4 different router/access point.

Linksys E3000 with the latest Linksys and Tomatousb firmware... brand new with all default settings.

Asus RT-N16 with the latest tomatousb firmware

Trendnet TEW-453APB access point with the latest firmware.

and one unknown brand router/access point

except for the Trendnet access point that is configured for WPA/TKIP, all others are using WPA2/AES.

I can not and will not configure my access point to see if wep is working...

Clearly, there is an issue with the wireless card on the new macbook pro... Apple should fix it.

here's another set:

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=64 time=0.726 ms

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

64 bytes from 192.168.1.1: icmp_seq=21 ttl=64 time=0.834 ms

64 bytes from 192.168.1.1: icmp_seq=22 ttl=64 time=0.715 ms

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

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

--- 192.168.1.1 ping statistics ---

25 packets transmitted, 25 packets received, 0.0% packet loss

round-trip min/avg/max/stddev = 0.613/0.781/1.909/0.243 ms

==============================================================

and since some of done 100 ping tests:

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=64 time=0.673 ms

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

64 bytes from 192.168.1.1: icmp_seq=21 ttl=64 time=0.936 ms

64 bytes from 192.168.1.1: icmp_seq=22 ttl=64 time=0.768 ms

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

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

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

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

64 bytes from 192.168.1.1: icmp_seq=27 ttl=64 time=0.665 ms

64 bytes from 192.168.1.1: icmp_seq=28 ttl=64 time=0.831 ms

64 bytes from 192.168.1.1: icmp_seq=29 ttl=64 time=0.673 ms

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

--- 192.168.1.1 ping statistics ---

100 packets transmitted, 100 packets received, 0.0% packet loss

round-trip min/avg/max/stddev = 0.606/0.786/1.651/0.140 ms

Ever couple of tests, I'll get a few outlier pings, but this is to be expected in networking. It's really all about the observed stability of your connection. To that end, I've never dropped connection with my new Netgear router. My old router would drop the connection every so often and pick it back up. maybe once a month I might have had to power cycle it to bring it back to optimum performance. No issues after about a month with the new Netgear. No reboots needed. Intranet (inside my home, computer to computer) transfer speeds have reached a max of 14.5MB/s in, 14.7MB/s out. Internet (out to the rest of the world) have reached the max speeds my ISP provides me (about 3.3MB/s). Again, never a drop, never a lost signal. Netgear WNDR3700.

@ the last poster: I've seen and had problems with Trendnet and Linksys routers. In both cases, using a better/different router was resolved my situation. Also, surely temporarially switching to WEP for 10 minutes to test the theory wouldn't break your universe. But if waiting and hoping Apple does something about this is a better option for you than trying some of the suggestions, then carry on waiting. Might be days. Might be weeks. Might be months. Hey...a "fix" may never actually come because it just may be that there's a simple lack of compatability with certain router firmware. I'll continue enjoying my consistency and blazing speeds, just about 100% sure that the problem is not your hardware.

Good luck, all. Do what you feel you should do (and if that means "do nothing", then by all means, suit yourself).

$0.02

Its good to know your macbook is fine but many have done everything you've suggested and do have a problem, why would you assume we have been sitting on our hands?