This post isn't much more than a "me too": early-2011 13" Macbook Pro; 10.6.7; connected to a Netgear WNDR3700 running DD-WRT firmware. Airport connects fine, good connectivity, consistent fast pings, then without warning (possibly after a brief period of not doing much) I'll find the connection is no longer passing data (despite full strength indication in the Airport menu bar icon). Turning Airport off and back on again restores connectivity.
All other devices in the house (earlier Macbooks, Mac Mini, iPhones, iPad) are unaffected.
Update: My MBP 17" 2011 hasn't dropped connection since I changed my router security settings from WPA-PSK only to WPA-PSK(TKIP)+WPA-PSK(AES). I have used that connection for almost 2 weeks with no problems at all. I noticed when I first set my router to WPA (Personal) only, either one of the other devices (PC+Macs+other wireless devices) tend to create IP address conflicts with my MBP 17"-----resulting to either a dropped or very slow connection.
For some reason setting my router to WPA+WPA2 has prevented the issues. I don't know if setting it that way could present security issues, but I wouldn't care for now as long as I feel my MBP's working fine.
I just wanted to add that I am having the same problem with my 17 2.3 2011. I have the same issue on wireless networks at home and around town whole my iPad works flawlessly. I'm using iPad to wrangle my deadlines and send out files. It's a bit ridiculous. The problem started less than a week after purchase. I'm going to return the unit tomorrow as I'm leaving for a trip overseas Friday. I just need a computer with a working wifi signal. It's good to know I am not alone; I am lucky that I'm only 100 miles from an apple store.
I'd love to watch the WWDC keynote by Steve, but my wireless connection keeps going stupid....APPLE, please address this problem. There's ample information and evidence that there's a software or firmware problem. We've been trying work-arounds. We've been stumbling around with all sorts of suggestions of "try this, try that". Fact is there's a problem. We've been suffering long enough. It's time to fix the problem(s).
Update: To resolve this issue, at the Apple Store, we just installed a clean system. I did push my docs and apps over using migration assistant, despite the warning by the genius. I've been up and running for about a couple of hours and so far things are working. I'm leaving for the field next week, and as a precaution I'm taking the install disks and some of the large update files with me.
Note that my initial attempt to roll back the system did not work; I had to do a complete system install.
Its pretty sure that not everyone is facing this problem. As there are tons of new Macbook Owners, and here we can see just a couple of hundreds shouting their grievances, and out of them many are just posting updates and solutions that they think may be right to solve the issue.
The best thing would be to ask for a refund at this stage, after the WWDC 2011 first day yesterday and after what i just spoke to one of the Customer Service representatives online at live chat, they have informed that we will be allowed a free full upgrade to Mac OS X Lion if we purchase the Macbook Pro now. (What they mean by now, is possibly, after the announcement of MAC OS X Lion, I am not that sure about it).
But looking yesterday's great demo by Steve and other Apple Guys it looks far too promising then to having sit with these stupid problems and that too on a new Macbook Pro.
The other reason why I would ask you guys to opt for a refund if possible, is because there is possibly a new Macbook Air launch awaiting, I know many of you might be hating the Macbook Air due to your requirements of Video Editing, heavy photoshop works, etc, but you guys just don't know what might be in store on the new Macbooks? It could be anything from great to awesome to Excellent, but I am pretty sure it won't be awful due to the immense competition Apple and Steve are facing from Intel's Ultrabooks, Windows 8 platform for Tablets and touch screen notebooks, etc.
So if you have that possibility or chance to wait for sometime, it is really worth it.. But if you can't wait, and need a laptop for your daily needs or just because you are too happy being an owner of Macbook Pro, all I can say is,, save your ping statistics while you are experiencing this problem, show it to an Apple Genius at a Apple Store, and try to at least get it replaced with the new one..
Cheers, All the best
I spent the third day of dealing with this issue yesterday. I spoke for a long time with an Apple tech who services macs here in Central Wisconsin, USA. He explained that the issue some of us are seeing probably has to do with older software that gets migrated over on our macs when we use migration assistant. It's definitely a software issue effecting some of us.
The best solution those experiencing this may be as I've done - is to reinstall a clean system, download updates, and then manually migrate work over to your new computer or hard drive. I recommend copying the documents folder directly and then carefully copying mail and other application support files over on an as needed basis. As far as applications go, the recommendations from my creative network all told me to install clean versions of all the apps I use.
That's a tremendous amount of work but it's what I've done. I'm well into the process and so far my internet connection is nice and stable on the 2011 MCBP.
Hopefully Apple will make a hotfix or solve this issue in Lion for us somewhat early adopters. As one recent poster recommended, I would have returned the unit at day 14 but I'm leaving on an international assignment and need the extra horsepower. For those of you in a similar situation as me, I recommend having SuperDuper and 1password (updated via dropbox) as part of your regular routines.
Finally i bought my new macbook pro 13" on sunday. Its awesome, its amazing... Ok its only wednesday but i didnt have any connection problem so far. I can use the maximum internet speed upload and download too. And we dont have the best broadband. Its only 10mbps fibre optic from virgin uk. The router is a Netgear wgr614v9 on wireless G. I downloaded few movies, listening music on youtube and last.fm, i watched the nba finals online...everything was perfect. I bought an intel ssd on the same day so the only thing what i did it was a clean OSx install. The speed of the ssd is unbelivable by the way.
My ping stats to the router:
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=4.037 ms
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=3.916 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=3.989 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=3.994 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=3.875 ms
64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=1.560 ms
64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=3.994 ms
64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=5.263 ms
64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=4.033 ms
64 bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=3.893 ms
--- 192.168.1.1 ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 1.560/3.855/5.263/0.859 ms
Ping has started…
PING www.l.google.com (188.8.131.52): 56 data bytes
64 bytes from 184.108.40.206: icmp_seq=0 ttl=51 time=30.898 ms
64 bytes from 220.127.116.11: icmp_seq=1 ttl=51 time=27.183 ms
64 bytes from 18.104.22.168: icmp_seq=2 ttl=51 time=28.272 ms
64 bytes from 22.214.171.124: icmp_seq=3 ttl=51 time=54.729 ms
64 bytes from 126.96.36.199: icmp_seq=4 ttl=51 time=38.955 ms
64 bytes from 188.8.131.52: icmp_seq=5 ttl=51 time=38.331 ms
64 bytes from 184.108.40.206: icmp_seq=6 ttl=51 time=49.527 ms
64 bytes from 220.127.116.11: icmp_seq=7 ttl=51 time=28.802 ms
64 bytes from 18.104.22.168: icmp_seq=8 ttl=51 time=33.526 ms
64 bytes from 22.214.171.124: icmp_seq=9 ttl=51 time=29.754 ms
--- www.l.google.com ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 27.183/35.998/54.729/8.991 ms
Well, I can understand how MAYBE a clean install would fix the problem Perhaps some hardware driver update, protocol stack software, etc. got corrupted somewhere along the line of upgrade from 10.4 to 10.5 to 10.6, whatever. This would certainly explain how my MBP worked 'back in the day, and now is a POS. HOWEVER, this does NOT explain the numerous MPB users experiencing same problems with new MBP right out of the box from Apple.
Further, application level programs should never, Never, NEVER ever be cognizant of specifics down at the hardware driver level, or the network protocol stack for that matter. To do so would a a violation of some very basic tenants of software/system and networking architectures that have been around for well over 2 decades. If Apple were doing something remotely like this it would be a major no-no, stupid and amateur. I give Apple more credit than that. Thus, any notion that a clean install would fix the problem, then bringing applications and user docs/files would then somehow subsequently corrupt the WiFi networking simply does not hold up to scrutiny. I can't say it couldn't happen (memory leaks, applications corrupting system memory, etc notwithstanding - these being unlikely, again due to OS architectures and protections).
So, the only conclusion(s) I can make from all this:
1. There is a bug in the OS, hardware drivers or WiFi protocol stack (or any/all of the above) that has been introduced since 10.4 (last time I remember my MBP working solidly on WiFi), and seems to be specific to the MBP (otherwise explain side-by-side reports of MBP and iPad, iPhone, etc, with MPB failing, other devices working fine), OR
2. We're victims of mass hysteria. I can't vouch for everyone else on this forum who have reported ongoing problems, but I'm fairly certain I am not imagining the problems on my system, so I think the likelihood of mass hysteria is near zero.
What I do know for certain is:
1. I replaced my WiFi card in my MBP. with an airport extreme board. This improved my RSS levels somewhat, which is good. It did not improve my connectivity/stability much if at all.
2. I can sit in various locations in my home, not very far from the router, with VERY acceptable RSS levels, and the connection is flakey as ****. I can take airport down, up, down, up, and if I do this enough times I can get a connection with good RSS AND good bit rates (36 Mbps or more). Same location, all else the same. This is true in these locations all the while other WiFi devices, including iPhone and a WinDoze laptop working all day, every day, no hiccups.
3. When doing #2, I can get unstable connections from time to time, which start out with good-excellent RSS, and good bit rates, but within a few seconds or perhaps a minute or two degrades to 1 Mbps (which may actually be zero I suspect because I cannot, no way no how get email, send email or surf with Safari). If, on the other hand when doing #2 I get a good connection, say 36 Mbps by trying enough airport on/off/on cycles, it seems to work well for a good amount of time (but not forever).
4. I can sit right next to the router, get good-excellent RSS, get a stable connection which seems to go fast, last a long time and works with email and Safari with no hangs.
What I conclude from this is there MUST be a bug somewhere in software. In areas with somewhat reduced RSS levels (but still WELL within acceptable minimums), the software must be going stupid when it attempts to correct/retry errors, step down the bitrate, SOMETHING like that. I've written enough software, including networking protocol stacks over the years to know what a software bug looks like. I'll point out that my experience is NOT with Apple software or 802.11 specifics. Nevertheless, protocol stacks are protocol stacks, more or less. This problem sure as **** has all the symptoms of error recovery logic going stupid at some operating margin/boundary condition. This is typically where most bugs occur anyway, that's where I would be looking if I was Apple trying to fix this one. I also wouldn't rule out the possibility of an 802.11 protocol incompatibility with non-Apple Airport routers. Another source of software bugs - products that work well with mfgrs. other products, in the lab, all day long. Then they fail in the field in conditions not found in the lab.
Anyway this is my long-winded $0.02 worth. Maybe someone at Apple will take a look and it will trigger something that leads to a solution. I know for certain this is really, REALLY getting to be a PITA and I would appreciate a solution from Apple instead of this constant churning in the forums.
Thanks for you comments. I think there are two things you can do.
1. Provide apple feedback. Look up the feedback link earlier on this same thread. This goes to the developer team.
2. Just do the clean install (I even erased my hard disk). The mcbp's ship with 10.6.6 so see if you have a good wifi connection after the clean install + all the updates. If that is the case, I recommend proceeding with the method I described.
None of my other creative pro friends had this issue. Two techs I spoke with said it was a bug as well - probably something to do with some of the new technology.