new macbook pro 2011 weak and dropping wireless connection

Hi,

Try do download iStumbler for Mac OS, the on one of your Windows download Netstumbler, run the software and compare the results.

Remember that WI-FI devices must hav 3 chanales space, ( if your naborers WI-FI use chanal 1, you need to configure your WI-FI to use chanal 3)

istumbler download http://www.istumbler.net/ used whit Mac OS,

Netstumbler download http://www.netstumbler.com/downloads/ run on Windows

!! remember to turn on WI-FI on the MBP.

My Mac 2.8 Ghz Intel Core i7 is running fine on several WF-FI

Ib

PhotoPippi wrote:

Hi,

Try do download iStumbler for Mac OS, the on one of your Windows download Netstumbler, run the software and compare the results.

Remember that WI-FI devices must hav 3 chanales space, ( if your naborers WI-FI use chanal 1, you need to configure your WI-FI to use chanal 3)

That's 2 spaces, do you mean 2 or 3?

Modern Access Pionts autodetect and choose the right channel but as a rule of thumb set, getting the best performance of the Access Points are in same area range for channel 1, 3, 6, 9, 11

To iStumbler can see your neighbors' network make sure that your Access Point if possible is 3 channels "away" from the other Access Points, especially from the Access Point has the strongest signal.

Sorry if I confused anyone 😕, but the short version is that it helps to have as wide a spacing as possible to other Access Points, so if you neighbor run on channel 1 you can chuse channal 11.

Sincerely,

Ib

iStumbler crashes on my MBP with Lion.

I've chosen channel 12 because that doesn't interfere with any other WiFi configs around my house. My router shows both WiFi quality and interferences with other WiFis it sees; also the "hidden" ones. When I switched from 2.4 to the 5 GHz band (nobody there but me), the MBPs wouldn't connect.

Why does the problem "build up" with time? The newer the user is, the less problematic WiFi use is.

This is driving me crazy. Wake up, Apple!

All, on my Macbook the connection drop outs seemed to be linked to proxy configuration. I had proxy discovery and auto proxy setup (http://wpad/wpad.dat) on my Macbook pro 13" (a 2011 i5 bought in July) so that I can access internet when connected to my works corporate VPN. The other day i decided to disable that at home just to see what happens. Voila, my connection drops have disappeared.

I have been surfing and using the internet for over 2 hours now without any problems now. Earlier every 15/20 mins or so my internet connection would simply drop. The browser (both firefox and safari) would just hang on a website, with waiting to connect. WIFI signal would always be at max during this btw, so it was not an issue with actual WIFI connectivity (i can easily access the router console over wifi for example even when outside internet access has hung).

So atleast for me, the proxy setup seems to be a factor here.

All, for those who have Lion installed, Apple just released 10.7.1

Within that it contains one line that says:

"Improve the reliability of Wi-Fi connections."

Now, I haven't had an issue with mine since I got a new router a while back, so I'm not looking for a 'fix' but it may help some of you out.

EDIT: Airport firmware has gone from: 5.100.98.75.6 -> 5.100.98.75.10

I'm getting 24MB/s transfers from my NAS box over a 5Ghz wireless network (showing as connected at 270Mbps...but obviously transferring at more like 190Mbps). This is via the AFP protocol. Via Samba it's more like 12MB/s.

Still getting dropouts on the ping tests whilst transferring large files though. (Not that it seems to have much of an impact to my file transfer).

The Lion Update changes, but doesn't really improve, the situation. Basically I think Apple raised the bar for the system thinking that it's offline. Take a look at my ping readouts:

64 bytes from 192.168.2.1: icmp_seq=434 ttl=64 time=71.960 ms

64 bytes from 192.168.2.1: icmp_seq=435 ttl=64 time=93.848 ms

64 bytes from 192.168.2.1: icmp_seq=436 ttl=64 time=177.108 ms

Request timeout for icmp_seq 438

64 bytes from 192.168.2.1: icmp_seq=437 ttl=64 time=2067.323 ms

64 bytes from 192.168.2.1: icmp_seq=438 ttl=64 time=1073.292 ms

64 bytes from 192.168.2.1: icmp_seq=439 ttl=64 time=185.026 ms

64 bytes from 192.168.2.1: icmp_seq=440 ttl=64 time=45.218 ms

64 bytes from 192.168.2.1: icmp_seq=441 ttl=64 time=105.932 ms

64 bytes from 192.168.2.1: icmp_seq=442 ttl=64 time=79.745 ms

64 bytes from 192.168.2.1: icmp_seq=444 ttl=64 time=100.956 ms

64 bytes from 192.168.2.1: icmp_seq=445 ttl=64 time=7.909 ms

64 bytes from 192.168.2.1: icmp_seq=446 ttl=64 time=234.812 ms

64 bytes from 192.168.2.1: icmp_seq=447 ttl=64 time=929.078 ms

64 bytes from 192.168.2.1: icmp_seq=448 ttl=64 time=290.683 ms

64 bytes from 192.168.2.1: icmp_seq=449 ttl=64 time=331.388 ms

64 bytes from 192.168.2.1: icmp_seq=450 ttl=64 time=183.219 ms

64 bytes from 192.168.2.1: icmp_seq=451 ttl=64 time=130.450 ms

64 bytes from 192.168.2.1: icmp_seq=452 ttl=64 time=11.624 ms

64 bytes from 192.168.2.1: icmp_seq=453 ttl=64 time=93.928 ms

64 bytes from 192.168.2.1: icmp_seq=454 ttl=64 time=230.625 ms

64 bytes from 192.168.2.1: icmp_seq=455 ttl=64 time=162.973 ms

64 bytes from 192.168.2.1: icmp_seq=456 ttl=64 time=278.333 ms

64 bytes from 192.168.2.1: icmp_seq=457 ttl=64 time=275.460 ms

64 bytes from 192.168.2.1: icmp_seq=458 ttl=64 time=896.808 ms

64 bytes from 192.168.2.1: icmp_seq=460 ttl=64 time=10.781 ms

64 bytes from 192.168.2.1: icmp_seq=461 ttl=64 time=143.466 ms

64 bytes from 192.168.2.1: icmp_seq=462 ttl=64 time=11.126 ms

64 bytes from 192.168.2.1: icmp_seq=463 ttl=64 time=195.700 ms

64 bytes from 192.168.2.1: icmp_seq=464 ttl=64 time=8.070 ms

64 bytes from 192.168.2.1: icmp_seq=465 ttl=64 time=13.950 ms

64 bytes from 192.168.2.1: icmp_seq=466 ttl=64 time=3.943 ms

Request timeout for icmp_seq 467

64 bytes from 192.168.2.1: icmp_seq=468 ttl=64 time=661.993 ms

64 bytes from 192.168.2.1: icmp_seq=469 ttl=64 time=16.030 ms

64 bytes from 192.168.2.1: icmp_seq=470 ttl=64 time=33.658 ms

64 bytes from 192.168.2.1: icmp_seq=471 ttl=64 time=116.047 ms

64 bytes from 192.168.2.1: icmp_seq=472 ttl=64 time=129.273 ms

64 bytes from 192.168.2.1: icmp_seq=473 ttl=64 time=20.678 ms

64 bytes from 192.168.2.1: icmp_seq=474 ttl=64 time=152.724 ms

Just surfing. No other active users in my WiFi. And while typing this … offline again.

Apple & WiFi & MBP = EPIC FAIL.

Same problems here! imposible to play wow online

i don't think apple will fix this ever though.. i've seen in other forums that this problem existed couple of years back. if apple is dead serious in fixing this problem then they should have corrected this years ago.

problem is still popping up now and best they could do is "improve" reliability of wifi connections with their os update. notice that in other fixes they put "resolve" instead of improve. goes to show that a) they're not that serious about the fix or b) they can't figure out how to fix it

am a new mbp user for less than a month and very disappointed with the experience. will be selling this machine to someone who doesn't have/use wifi

"a) they're not that serious about the fix or b) they can't figure out how to fix it"

Good points, jef_512.

There are many good journalists specialized in the field of computers. If this issue can be brought to their attention, They may be able to write an article(s) on Apple's Achilles Heel and embarrass them enough into devoting energy to solving the problem.

Then again, notebooks are not the future of computing, especially at the mobile level. Sales of notebooks will be flat very soon and as we all know Apple is all about the future.

I've said it once, I'll say it again, if you have an MBP, make sure you travel with a long ethernet cable.

Cheers to all fellow sufferers.

I am so dissapointed, my new machine is way faster than my 1st gen Unibody MBP, but the wifi problem makes impossible to play online games, I got the top model because the graphic card is good for that, but I get disconnected every 5 min, big lag spikes, nothing to do with video card, only wifi.

They could solve this so easily....(hope)

Machine: i7 2.2 qc, standard 15"

Devastating really....

I never had problems until recently (the last few days). There is literally zero answers to this solution, which I find to be completely ludicrous.

At first, I was giggling when people were complaining about how much money they spent on the MBP - and getting problems, but after a week of this, i'm feeling the exact same.

Such a frustrating problem. It's driving me insane.

The thing that really ****** me off is that people have been having this problem for years now. What the f*ck.

There may actually be a solution to this issue.

And Apple (debatably the richest company in America) can and should find a solution.

Let's ramp it up, everybody. Let's keep the pressure on Apple

I think "b) they can't figure out how to fix it" is the answer.

There are also tons of threads like this about iPads randmoly dropping off from WiFi.

This is becoming an interesting part of 'history'. I can imagine reading a Wikipedia article about this years later.