Q: MacBook Pro constantly losing wireless connectivity

I'm sorry to say that I've joined you folks with wireless misery. I've just completed the upgrade to 10.5.3, which has made no difference, and tried just about every other permutation and combination of anything to do with wireless on the MBP: nothing has made the slightest bit of difference. I still have five bars in the Airport icon, but never even a hint of a webpage. If I had wanted a desktop I'd have bought an iMac. This really *****.

Wow, glad to see I'm not alone in this annoying problem.

I have some similarities- sudden dropping off as of a few weeks ago, but I have not recently updated my OS. Also, my bars do not stay black even when I'm kicked off (I know a few have mentioned their bars stay on). I can see my bars fading. I did download iStumbler and notice that when I can't get on with my Airport, I can't pick up any other neighboring signals either. Guess this rules out interference or an Airport problem? (A Dell laptop in the house still connects to Airport fine.) Also, my connection works fine in the morning, after the MBP has been off all night, but as the day goes on, and it goes in and out of sleep mode, the signal goes down. By 2pm, I'm down to the smallest light on the signal bar and by 8pm, I can't connect at all. Anyone else have these similarities? A friend mentioned replacing the internal wireless card? Sorry if these have been mentioned in previous posts, I haven't had time to read them all, as my internet time is limited to mornings before I'm booted off.

Thanks.

See my possible fix listed in the Macbook Internet forum.

Changing to different encryption helps but does not solve problem completly for me, still using WEP. This problem with wireless card will be a problem outside my home network where I'll unable to tweak router. Updating to 10.5.3 did not solve this problem.

Message was edited by: WebMoskal

Brand new MBP 17", I have the same problem. Setting my router to 'G-only' resolves it, but this is not a fix. I hope the guys at Apple provide us with one VERY soon... Not very happy at the moment...

Little update: now even with my router on 'G-only'-mode the connection is slow at best, it loses connection constantly. Is anyone else still experiencing this problem or did 10.5.3 fix this for all of you? I'd think it made matters even worse for me...

I responded to the other question on the topic, but I wanted to add my name to this one.

Got my Penryn MBP in Feb. Running WinXP and MacOS X (10.5.3 now) on it. Because I need to run certain applications, the machine is running WinXP most of the time. My access point is a Linksys WAP54G which is supposed to do 802.11b and g.

There are a gaggle of machine in the house and only the MBP is having problems with the wifi. The problem does not seem as bad under MacOS. I have a Powerbook G4 (Aluminum) and an Intel Mac Mini using the same wifi with no issues.

The symptom is that the connection will just drop. Sometimes it comes back on its own quickly. Sometimes it comes back after a long wait. Sometimes it does not come back and I have to reboot. Rebooting corrects the problem.

There was a Windows driver update from Apple a month or so ago. Since the driver update, the system suffers less from BSOD (though they still happen), but drops wifi connections more frequently and it takes three times as long to burn DVDs.

I can't believe that Apple doesn't have a fix for this by now.

Just installed 10.5.3. Problem is the same. tried to download a rental from iTunes and the wireless on my MBP dropped 4 times. My other Mac and Windows system all running on the same network with no problems. This is an embarasment for Apple and I am losing my patience.

Same here and I have had it. I am taking this issue public in the newspapers and every tech/computer magazine in the country.) 10.5.3 was suppose to fix this "issue"...
<post edited by host>

I was having a similar problem to the one you all are having. Pinging 4chan.org would look like this:

64 bytes from 66.207.165.166: icmp_seq=27586 ttl=48 time=721.931 ms
64 bytes from 66.207.165.166: icmp_seq=27587 ttl=48 time=48.937 ms
64 bytes from 66.207.165.166: icmp_seq=27588 ttl=48 time=51.848 ms
64 bytes from 66.207.165.166: icmp_seq=27589 ttl=48 time=645.903 ms
64 bytes from 66.207.165.166: icmp_seq=27590 ttl=48 time=448.310 ms
64 bytes from 66.207.165.166: icmp_seq=27591 ttl=48 time=150.926 ms
64 bytes from 66.207.165.166: icmp_seq=27592 ttl=48 time=50.579 ms
64 bytes from 66.207.165.166: icmp_seq=27593 ttl=48 time=215.832 ms
64 bytes from 66.207.165.166: icmp_seq=27594 ttl=48 time=310.341 ms
64 bytes from 66.207.165.166: icmp_seq=27595 ttl=48 time=48.986 ms
64 bytes from 66.207.165.166: icmp_seq=27596 ttl=48 time=66.029 ms
64 bytes from 66.207.165.166: icmp_seq=27597 ttl=48 time=589.417 ms
64 bytes from 66.207.165.166: icmp_seq=27598 ttl=48 time=435.960 ms
64 bytes from 66.207.165.166: icmp_seq=27599 ttl=48 time=58.562 ms
64 bytes from 66.207.165.166: icmp_seq=27600 ttl=48 time=48.648 ms
64 bytes from 66.207.165.166: icmp_seq=27601 ttl=48 time=539.189 ms
64 bytes from 66.207.165.166: icmp_seq=27602 ttl=48 time=567.103 ms
64 bytes from 66.207.165.166: icmp_seq=27603 ttl=48 time=141.387 ms
64 bytes from 66.207.165.166: icmp_seq=27604 ttl=48 time=48.727 ms
64 bytes from 66.207.165.166: icmp_seq=27605 ttl=48 time=338.147 ms
64 bytes from 66.207.165.166: icmp_seq=27606 ttl=48 time=178.393 ms
64 bytes from 66.207.165.166: icmp_seq=27607 ttl=48 time=47.747 ms
64 bytes from 66.207.165.166: icmp_seq=27608 ttl=48 time=47.787 ms
64 bytes from 66.207.165.166: icmp_seq=27609 ttl=48 time=448.751 ms
64 bytes from 66.207.165.166: icmp_seq=27610 ttl=48 time=477.588 ms
64 bytes from 66.207.165.166: icmp_seq=27611 ttl=48 time=47.915 ms
64 bytes from 66.207.165.166: icmp_seq=27612 ttl=48 time=56.028 ms
64 bytes from 66.207.165.166: icmp_seq=27613 ttl=48 time=845.949 ms

Randomly, about half of the time, my computer would lag out and be unable to load anything. Every 10 minutes or so, it would lose about 40 packets, then reconnect and go back to this sporadic mix of 50ms pings and 800ms pings.

After changing my Airport Extreme from 802.11g/b compatible to 802.11g only, pinging 4chan.org looks like this:

64 bytes from 66.207.165.166: icmp_seq=0 ttl=48 time=51.958 ms
64 bytes from 66.207.165.166: icmp_seq=1 ttl=48 time=68.150 ms
64 bytes from 66.207.165.166: icmp_seq=2 ttl=48 time=54.859 ms
64 bytes from 66.207.165.166: icmp_seq=3 ttl=48 time=53.700 ms
64 bytes from 66.207.165.166: icmp_seq=4 ttl=48 time=56.317 ms
64 bytes from 66.207.165.166: icmp_seq=5 ttl=48 time=52.704 ms
64 bytes from 66.207.165.166: icmp_seq=6 ttl=48 time=65.489 ms
64 bytes from 66.207.165.166: icmp_seq=7 ttl=48 time=51.982 ms
64 bytes from 66.207.165.166: icmp_seq=8 ttl=48 time=54.519 ms
64 bytes from 66.207.165.166: icmp_seq=9 ttl=48 time=50.833 ms
64 bytes from 66.207.165.166: icmp_seq=10 ttl=48 time=54.294 ms
64 bytes from 66.207.165.166: icmp_seq=11 ttl=48 time=54.016 ms
64 bytes from 66.207.165.166: icmp_seq=12 ttl=48 time=48.198 ms
64 bytes from 66.207.165.166: icmp_seq=13 ttl=48 time=50.007 ms
64 bytes from 66.207.165.166: icmp_seq=14 ttl=48 time=52.387 ms
....
64 bytes from 66.207.165.166: icmp_seq=89 ttl=48 time=62.198 ms
64 bytes from 66.207.165.166: icmp_seq=90 ttl=48 time=49.212 ms
64 bytes from 66.207.165.166: icmp_seq=91 ttl=48 time=79.124 ms
64 bytes from 66.207.165.166: icmp_seq=92 ttl=48 time=47.470 ms
64 bytes from 66.207.165.166: icmp_seq=93 ttl=48 time=55.527 ms
64 bytes from 66.207.165.166: icmp_seq=94 ttl=48 time=49.640 ms
64 bytes from 66.207.165.166: icmp_seq=95 ttl=48 time=50.280 ms


Works perfectly, and has been up for about an hour now with no drops.

If you haven't tried this, try it now. It very well might work.

Been doing that for quite awhile now. G only network. Same problem.

I have been having this same problem as well with my old 15" MacBook Pro. I also have a PowerBook and a new iMac 24" that don't have this problem at all. One note is that it seem that if I am really close to the hub (a Linksys b/g in this case) then I don't have the problem (or at least not as often). I need to be basically in the same room though. If I move a little bit away, even though I still have all the bars on the signal, then it starts to drop the connection periodically. The PowerBook and iMac don't have this problem at all.

I also figured it would be fixed for sure in 10.5.3, but to no avail. Also, I don't remember this happening at all prior to 10.5 (and I'm sure I would have remembered it).

I'm no more than 2 feet from my Airport Base Station. Using only G network. Still happens occasionally.

Try switching your router from WPA or WPA2 to WEP encryption that did make diff for me.

Message was edited by: WebMoskal

I'm cautiously optimistic..... I had the Apple store replace my wireless card ($190 part/labor) and it's been working perfectly for almost 12 hours now.