Q: Dropping Wi FI Signal

I want to concur with others here that this isn't a problem with the respective network.

My household has two other macs (a G5 iMac and a unibody macbook) plus an older HP laptop running win7 & ubuntu. None of those computer have this problem.

I've been trying to figure out what is happening-because very oddly when the MBP 5,3 15" with 10.6.1 loses connection sometimes the modem goes out briefly then resets.
The MBP doesn't reconnect though AND the modem doesn't always go out or reset either. I've never seen this behavior before using the MBP on my network.

I have tried deleting the specific network in the network manager-and restarting. I have tried many many things. The drop outs still happen.

Bottom line this is a 2,000USD machine all the other computers just work and this doesn't!

< Edited by Host >

out of my 3 macs, only the ibook has this problem. My daughters 2 month old mbp also didn't have this problem. All running 10.5.8. tweaking the wireless settings resolved MY connection issues (or lack thereof)

Fully agree with RADLURE. My 17" MBP cost over $2700. And every time the WiFi drops (maybe 10 minutes or half an hour), I am kind disgusted that why I bought this piece of the junk. And apparently Apple does not care about this while I was waiting for an update to solve this over a month.

As an electrical engineer with Ph.D degree, I don't understand how Apple's internal quality control on their software did not know this problem. It is a disgrace that such a product can be released. And we are tricked to believe Snow Leopard is better than Leopard. Do you see the similar scam that people are led to believe Vista is better than XP here?

If Steve Job sees this forum, he should fire all the engineers in the Snow Leopard team.

Whats the model of the Modem and firmware version on it ? Have you checked if there is an update for it ?

DrVenture wrote:
For those still having issues, please grab a kernel log:

1. Open a term
2. cd /usr/libexec
3. sudo ./airportd debug +AllUserland +AllDriver +AllVendor
4. sudo ./airportd logger
5. reproduce the problem
6. open a console
7. find your kernel.log on the left side (expand /private/var/log
8. copy your kernel log for 3 minutes before and after your reproduced the problem and paste it to this thread.

DrVenture:

Here is the copy&paste from the kernel.log, I've only edited out my name for privacy reasons:

Oct 23 18:34:42 -MacBook-Pro kernel[0]: RSC: 00 00 00 00 00 00
Oct 23 18:34:42 -MacBook-Pro kernel[0]: GTK: dd 6b e2 45 4c 1a a4 11 5b c9 bd 41 70 35 ab 2b d2 31 e6 03 fc f0 5c d4 05 91 35 e2 c0 bd 89 a3
Oct 23 18:36:12 -MacBook-Pro kernel[0]: AirPort: Link Down on en1. Reason 4 (Disassociated due to inactivity).
Oct 23 18:36:12 -MacBook-Pro kernel[0]: en1: link down event, informing supplicant.
Oct 23 18:36:19 -MacBook-Pro kernel[0]: Auth result for: 00:25:3c:72:77:d9 MAC AUTH succeeded
Oct 23 18:36:19 -MacBook-Pro kernel[0]: AirPort: Link Up on en1
Oct 23 18:36:19 -MacBook-Pro kernel[0]: en1: Received EAPOL packet (length = 113)
Oct 23 18:36:19 -MacBook-Pro kernel[0]: inputEAPOLFrame: 0 extra bytes present in EAPOL frame.
Oct 23 18:36:19 -MacBook-Pro kernel[0]: inputEAPOLFrame: Received message 1 of 4
Oct 23 18:36:19 -MacBook-Pro kernel[0]: FULL RSN IE FOUND: dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
Oct 23 18:36:19 -MacBook-Pro kernel[0]: storeFullRSNIE: getAPIELIST returned 0
Oct 23 18:36:19 -MacBook-Pro kernel[0]: PMK: 48 9b 37 8f 5f 56 4c fa 7d 4d b1 f4 5c 5f 56 e3 6d f0 eb b5 39 35 7a 11 ab 7c 70 3e 43 ca 80 f7
Oct 23 18:36:19 -MacBook-Pro kernel[0]: TPTK: 69 8e 35 0d 73 4b 5e 58 76 6c 3a b9 7d d3 c8 5f d1 40 37 a6 a1 67 2b 4c dc c2 11 ef 54 63 11 a8 5c 79 39 dc ae 0c 18 de d9 92 8b 27 e0 6d 96 f3 66 dd 7e ad 8d 85 6a b0 78 f5 16 be 74 22 8c b1
Oct 23 18:36:19 -MacBook-Pro kernel[0]: KEY MIC: 5d 21 6d e6 d2 cf 67 01 94 f7 27 6b ef 8f 6a a5
Oct 23 18:36:19 -MacBook-Pro kernel[0]: process1of4: sending replyPacket 137 bytes
Oct 23 18:36:19 -MacBook-Pro kernel[0]: en1: Received EAPOL packet (length = 137)
Oct 23 18:36:19 -MacBook-Pro kernel[0]: inputEAPOLFrame: 0 extra bytes present in EAPOL frame.
Oct 23 18:36:19 -MacBook-Pro kernel[0]: inputEAPOLFrame: Received message 3 of 4
Oct 23 18:36:19 -MacBook-Pro kernel[0]: process3of4: Performing IE check.
Oct 23 18:36:19 -MacBook-Pro kernel[0]: process3of4: sending replyPacket ( len = 113 ).
Oct 23 18:36:19 -MacBook-Pro kernel[0]: ptkThread: Sleeping!
Oct 23 18:36:19: --- last message repeated 1 time ---
Oct 23 18:36:19 -MacBook-Pro kernel[0]: ptkThread: Installing PTK!
Oct 23 18:36:19 -MacBook-Pro kernel[0]: PTK: 5c 79 39 dc ae 0c 18 de d9 92 8b 27 e0 6d 96 f3 78 f5 16 be 74 22 8c b1 66 dd 7e ad 8d 85 6a b0
Oct 23 18:36:19 -MacBook-Pro kernel[0]: en1: Received EAPOL packet (length = 145)
Oct 23 18:36:19 -MacBook-Pro kernel[0]: inputEAPOLFrame: 0 extra bytes present in EAPOL frame.
Oct 23 18:36:19 -MacBook-Pro kernel[0]: inputEAPOLFrame: Received message 1 of 2
Oct 23 18:36:19 -MacBook-Pro kernel[0]: installGTK: setting cipher key (flags = 0x0)
Oct 23 18:36:19 -MacBook-Pro kernel[0]: RSC: 76 00 00 00 00 00
Oct 23 18:36:19 -MacBook-Pro kernel[0]: GTK: dd 6b e2 45 4c 1a a4 11 5b c9 bd 41 70 35 ab 2b d2 31 e6 03 fc f0 5c d4 05 91 35 e2 c0 bd 89 a3
Oct 23 18:36:19 -MacBook-Pro kernel[0]: AirPort: RSN handshake complete on en1
Oct 23 18:38:11 -MacBook-Pro kernel[0]: AirPort: Link Down on en1. Reason 4 (Disassociated due to inactivity).
Oct 23 18:38:11 -MacBook-Pro kernel[0]: en1: link down event, informing supplicant.
Oct 23 18:38:26 -MacBook-Pro kernel[0]: IO80211ScanManager::scanDone: Scheduling cache purge timer in 30 seconds.
Oct 23 18:38:26 -MacBook-Pro kernel[0]: Auth result for: 00:25:3c:72:77:d9 MAC AUTH succeeded
Oct 23 18:38:26 -MacBook-Pro kernel[0]: AirPort: Link Up on en1
Oct 23 18:38:26 -MacBook-Pro kernel[0]: en1: Received EAPOL packet (length = 113)
Oct 23 18:38:26 -MacBook-Pro kernel[0]: inputEAPOLFrame: 0 extra bytes present in EAPOL frame.
Oct 23 18:38:26 -MacBook-Pro kernel[0]: inputEAPOLFrame: Received message 1 of 4
Oct 23 18:38:26 -MacBook-Pro kernel[0]: FULL RSN IE FOUND: dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
Oct 23 18:38:26-MacBook-Pro kernel[0]: storeFullRSNIE: getAPIELIST returned 0
Oct 23 18:38:26 -MacBook-Pro kernel[0]: PMK: 48 9b 37 8f 5f 56 4c fa 7d 4d b1 f4 5c 5f 56 e3 6d f0 eb b5 39 35 7a 11 ab 7c 70 3e 43 ca 80 f7
Oct 23 18:38:26 -MacBook-Pro kernel[0]: TPTK: 68 9f 24 b2 e7 5e c8 ea e9 bb a8 c5 3d 6a 58 87 18 1e d4 47 fb 2d 66 56 f0 1c bb bc be fc 2a ed 19 cc 59 56 61 20 6e 88 e0 94 74 17 79 19 cc ab 2e e1 6d 42 a4 b9 e2 f1 54 60 45 90 0c 61 77 d3
Oct 23 18:38:26 -MacBook-Pro kernel[0]: KEY MIC: d0 1e 64 cb 20 0c bd 07 59 e9 69 40 e6 25 1b 9a
Oct 23 18:38:26 -MacBook-Pro kernel[0]: process1of4: sending replyPacket 137 bytes
Oct 23 18:38:26 -MacBook-Pro kernel[0]: en1: Received EAPOL packet (length = 137)
Oct 23 18:38:26 -MacBook-Pro kernel[0]: inputEAPOLFrame: 0 extra bytes present in EAPOL frame.
Oct 23 18:38:26 -MacBook-Pro kernel[0]: inputEAPOLFrame: Received message 3 of 4
Oct 23 18:38:26 -MacBook-Pro kernel[0]: process3of4: Performing IE check.
Oct 23 18:38:26 -MacBook-Pro kernel[0]: process3of4: sending replyPacket ( len = 113 ).
Oct 23 18:38:26 -MacBook-Pro kernel[0]: ptkThread: Sleeping!
Oct 23 18:38:26: --- last message repeated 1 time ---
Oct 23 18:38:26 -MacBook-Pro kernel[0]: ptkThread: Installing PTK!
Oct 23 18:38:26 -MacBook-Pro kernel[0]: PTK: 19 cc 59 56 61 20 6e 88 e0 94 74 17 79 19 cc ab 54 60 45 90 0c 61 77 d3 2e e1 6d 42 a4 b9 e2 f1
Oct 23 18:38:26 -MacBook-Pro kernel[0]: en1: Received EAPOL packet (length = 145)
Oct 23 18:38:26 -MacBook-Pro kernel[0]: inputEAPOLFrame: 0 extra bytes present in EAPOL frame.
Oct 23 18:38:26 -MacBook-Pro kernel[0]: inputEAPOLFrame: Received message 1 of 2
Oct 23 18:38:26 -MacBook-Pro kernel[0]: installGTK: setting cipher key (flags = 0x0)
Oct 23 18:38:26 -MacBook-Pro kernel[0]: RSC: 94 01 00 00 00 00
Oct 23 18:38:26 -MacBook-Pro kernel[0]: GTK: dd 6b e2 45 4c 1a a4 11 5b c9 bd 41 70 35 ab 2b d2 31 e6 03 fc f0 5c d4 05 91 35 e2 c0 bd 89 a3
Oct 23 18:38:26 -MacBook-Pro kernel[0]: AirPort: RSN handshake complete on en1
Oct 23 18:38:56 -MacBook-Pro kernel[0]: IO80211ScanManager::cachePurge: Firing!

Definitely dropping the signal. I am just now upgrading the SL and it immediately changed. The next day I updated and it lasts a little longer.

I am one who wants things to just work. This is a disaster apple guys. Don't release the thing if it doesn't work. One of my boasts is that it just works. It appears that it seems okay with the iMac systems just replaced. My brother seems to not have a problem. But, uhm ... I can't tell people to upgrade if it doesn't work. I don't know from kernel logs, but I do know from "this piece of junk" and software not ready for prime time.

Please Apple people fix this. Will have to report the bug in Safari every time it happens. -- since september? I think we need to up the visibility of this complaint. OS should just work, otherwise we could get something else for cheaper. I buy to Mac to just work dudes.

I knew I should have read the boards - first.

Marie Wray2 wrote:
I think we need to up the visibility of this complaint.

Marie ~ See this previous post in this thread:

http://discussions.apple.com/message.jspa?messageID=10258916#10258916

Przemek55 has the answer that worked for me:

"Open an Internet Explorer browser page on your wired computer(desktop).In the address bar type 192.168.1.1 and press Enter...Leave Username blank & in Password use admin in lower case...Click on the Wireless tab.Set the Wireless channel to 11-2.462GHz...Click on Advanced Wireless Settings,Change the Beacon Interval to 75,Change the Fragmentation Threshold to 2304, Change the RTS Threshold to 2304 and Click on "Save Settings"...

<<<<

I have a DLINK DI-524 and found the Beacon Interval, Fragmentation and RTS Threshold settings and set them as he suggests. This appears to have fixed the problem. Only once did the computer appear to search for the router, but it connected without intervention from me.
Previously I done all the other suggestions: change the Channel, add a WEP password, etc etc, without good results.
Apple still has an issue they need to address.

Networking on a laptop and especially an Apple laptop should just work and I'm fully in support of people who want to hold Apple's feet to the fire.

Having said that I do see the other side too; which is that most users are not networking experts AND equipment, setup and usage vary greatly. All that makes it hard, for anyone, to determine what's going on. So perhaps consider that before we collectively light the torches and chase "them" up the mountain side.

There is definitely a problem with some networking hardware using OS 10.5.8 through 10.6.1 and the evidence is that there are reports of connection failure including frequent drop outs in both the Apple community forums and all over the web.
It also seems like a good idea to provide those log files. Maybe if Apple techs requested those (and told people specifically what and how) people would consider opening the terminal app and posting them?

My home network, which my MBP kept losing track of, consisted of a Westell 327W (which is a ADSL modem and wireless router combined) on Verizon DSL. I did the setup myself and everything seemed to work. There are plenty of posts on the web about that particular westell model and some do not believe it works well. Networking can be complicated as I intimated previously.

So recently (late last night) I purchased a Belkin N+ router and set it up with the original DSL modem (another Westell, the 6100) that Verizon supplied. It's not fun work and I had to go through a fairly complicated but mostly well documented set up procedure-most of the complication is with bridging the DSL modem (eyes reading this are glazing over I'm sure).
The Belkin N+ set up was pretty easy and I didn't even need to use the provided cd-once that blasted modem was set correctly.

Since I did that I've had no drop outs. This of course is just my specific experience, but it points out that networking is still too complicated and that my MBP with OS 10.6.1 is also very fussy about the network parameters. We need an app that shows clearly what's happening with our networks!

Apple isn't doing itself any favors by having this network "fussiness" in leopard and snow leopard. Finding out what is happening in the OS should be a priority.

Well I have changed my router to a Buffalo and still it is dropping I have one DHCP server. I agree with the comment it should just work this is what I tell people when they ask why I use a MAC. I am fed up with having no internet half the time I am the Head of Customer support and it is a pain in the rear to loose the connection to a corporate servers whilst trying to manage customer issues and a team. APPLE for heavens sake save my sanity and fix this

Let me add myself to the list of those having this problem. My difference is that it didn't start until earlier this week. I had upgraded to 10.6.1 over a month ago. All worked flawlessly (at least networking wise) until then. Tried the old approaches listed on MacFixIt (resetting PRAM & SMC), but that hasn't helped. Distance from router doesn't make a difference. Turning Airport off and on works for a short time (<5 min). Have deleted preferences, but that didn't work as well.

Next I will delete the airport connection and reinstall it (thru network preferences).

G

TSYYYY wrote:
Fully agree with RADLURE. My 17" MBP cost over $2700. And every time the WiFi drops (maybe 10 minutes or half an hour), I am kind disgusted that why I bought this piece of the junk. And apparently Apple does not care about this while I was waiting for an update to solve this over a month.

As an electrical engineer with Ph.D degree, I don't understand how Apple's internal quality control on their software did not know this problem. It is a disgrace that such a product can be released. And we are tricked to believe Snow Leopard is better than Leopard. Do you see the similar scam that people are led to believe Vista is better than XP here?

Probably because, oh, there are millions of Snow Leopard users using AirPort and their Mac portables with no issues whatsoever?

I've got an older MacBook Pro and a newer unibody one, and neither has dropped a connection, at all, for over a year. Not at home to my dual-band Time Capsule. Not in hotels. Not at my employer. Zero. In fact, not since Mac OS X 10.4 Tiger, the release many here rhapsodize about having "perfect" Wi-Fi drivers.

But sure, it's all Snow Leopard's fault.

Those of you having issues, I sympathize, I really do, I've been there myself.

But if you honestly think Apple doesn't test their software or that it's just "broken," you're very mistaken.

Here's a little test - if you have an Apple Store nearby, play with their demo computers; 99% of them are connected via AirPort and I've never seen an in-store system drop a connection.

Better yet, if you take your own system in, and it drops its connection on the Apple Store network, you now have a reproducible condition you can force the folks at the Genius Bar to address given the in-store demo machines don't exhibit the issue.

Hey guys, I just want to also add my voice and few things I have tried.

I am having the same problem... it does pick up but the signal is significantly weaker than leopard. So on my snow leopard I would get very slow signal than my other macbook with same specs leopard. Also something that I don't understand is the fact that when I boot to windows side to connect, the signal is weaker as well!! so hardware?? I am not sure...

I pretty much gave up and now I am waiting for apple to respond.

Well this my update. Thanks for reading

William Kucharski wrote:

Probably because, oh, there are millions of Snow Leopard users using AirPort and their Mac portables with no issues whatsoever?

I've got an older MacBook Pro and a newer unibody one, and neither has dropped a connection, at all, for over a year. Not at home to my dual-band Time Capsule. Not in hotels. Not at my employer. Zero. In fact, not since Mac OS X 10.4 Tiger, the release many here rhapsodize about having "perfect" Wi-Fi drivers.

But sure, it's all Snow Leopard's fault.

Those of you having issues, I sympathize, I really do, I've been there myself.

But if you honestly think Apple doesn't test their software or that it's just "broken," you're very mistaken.

Here's a little test - if you have an Apple Store nearby, play with their demo computers; 99% of them are connected via AirPort and I've never seen an in-store system drop a connection.

Better yet, if you take your own system in, and it drops its connection on the Apple Store network, you now have a reproducible condition you can force the folks at the Genius Bar to address given the in-store demo machines don't exhibit the issue.

That all sounds great BUT can you explain as easily why an Apple iMac, a macbook and an HP laptop never loss the wireless connection-while the MBP constantly lost it?
Yeah it must be the fault of the afore mentioned computers-all working hard to make the MBP look bad. You can be a fanboy for Apple all you want but it doesn't convince me something isn't going on!

radlure wrote:
That all sounds great BUT can you explain as easily why an Apple iMac, a macbook and an HP laptop never loss the wireless connection-while the MBP constantly lost it?

Could be a hardware issue with the MBP or the MBP's AirPort card, interference with the MBP, or different reception characteristics affecting the MBP.

Then there are just plain hardware issues that may be at play if, say, the other three machines had Atheros-based Wi-Fi chips and the MBP uses a Broadcom.

Finally of course there are possible issues with plists and keychains.

There are a wide variety of debugging steps that can be undertaken before accusing Apple of not testing their software before releasing it.