Minor Airport Client Issue

Hello there folks,
I recently purchased a iMac 12,2 and am fully updated to 10.6.8. The problem I have is that when I turn the iMac on after it being off for many hours, the AirPort connects to my router and I can use it as normal, but after about 30 seconds or so, AirPort suddenly loses throughput but doesn't disconnect from my SpeedTouch 585v7 router, I can no longer ping the router or use the connection at all. According to the system information application, it says the Transmit Rate has been set to 0, also as you can see in the data, it is detecting all other networks fine and working normally. The strangest thing is that I can just turn off AirPort and turn it back on, and the connection is then stable for the rest of the duration the iMac is switched on.
I have tried resetting configuration files, changing encryption settings, channels and checked every other known possibility, but to no avail. All I can assume is that there is some sort of problem with the AirPort client or router firmware/software, which I doubt because the WiFi has always and still does work perfectly on Windows XP/7 systems and my iPad 2 and iPhone 4 for their entire lifetime.
The WiFi router is located literally next to the iMac on my desk.
Any help would be gracefully appreciated.
In this data table, I have replaced MAC addresses and SSID's with <Hidden> to protect privacy.
Software Versions: Menu Extra: 6.2.2 (622.2) configd plug-in: 6.2.5 (625.6) System Profiler: 6.0.1 (601.1) Network Preference: 6.2.2 (622.2) AirPort Utility: 5.5.3 (553.20) IO80211 Family: 3.2 (320.1) Interfaces:en1: Card Type: AirPort Extreme (0x168C, 0x9A) Firmware Version: Atheros 9380: 4.0.35.3 Locale: ETSI Country Code: GB Supported Channels: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 36, 40, 44, 48, 52, 56, 60, 64, 100, 104, 108, 112, 116, 120, 124, 128, 132, 136, 140 Wake On Wireless: Supported Status: ConnectedCurrent Network Information:<hidden>: PHY Mode: 802.11g BSSID: <hidden> Channel: 11 Country Code: GB Network Type: Infrastructure Security: WPA2 Personal Signal / Noise: -27 dBm / -100 dBm Transmit Rate: 0Other Local Wireless Networks:<hidden>: PHY Mode: 802.11g BSSID: <hidden> Channel: 1 Country Code: GB Network Type: Infrastructure Security: WPA Personal Signal / Noise: -59 dBm / -96 dBm<hidden>: PHY Mode: 802.11g BSSID: <hidden> Channel: 1 Network Type: Infrastructure Security: WPA Personal Signal / Noise: -69 dBm / -96 dBm<hidden>: PHY Mode: 802.11g BSSID: <hidden> Channel: 6 Network Type: Infrastructure Security: WPA Personal Signal / Noise: -88 dBm / -96 dBm<hidden>: PHY Mode: 802.11n BSSID: <hidden> Channel: 3 Country Code: GB Network Type: Infrastructure Security: WPA2 Personal Signal / Noise: -84 dBm / -96 dBm<hidden>: PHY Mode: 802.11n BSSID: <hidden> Channel: 1 Network Type: Infrastructure Security: WPA2 Personal Signal / Noise: -85 dBm / -96 dBm<hidden>: PHY Mode: 802.11n BSSID: <hidden> Channel: 1 Country Code: GB Network Type: Infrastructure Security: WPA2 Personal Signal / Noise: -87 dBm / -96 dBm<hidden>: PHY Mode: 802.11b BSSID: <hidden> Channel: 6 Network Type: Computer-to-Computer Security: None Signal / Noise: -88 dBm / -96 dBm

Nothing interesting in the kernel log really as the connection was lost at approximately 09:01 so nor the software or the hardware has not detected that the wireless connection has been lost. Again, I can just reset it and it will operate for the rest of the duration the machine is on.
Jul 7 08:58:40 localhost kernel[0]: npvhash=4095Jul 7 08:58:40 localhost kernel[0]: Darwin Kernel Version 10.8.0: Tue Jun 7 16:32:41 PDT 2011; root:xnu-1504.15.3~1/RELEASE_X86_64Jul 7 08:58:40 localhost kernel[0]: vm_page_bootstrap: 2019761 free pages and 61007 wired pagesJul 7 08:58:40 localhost kernel[0]: kext submap [0xffffff7f80800000 - 0xffffff8000000000], kernel text [0xffffff8000200000 - 0xffffff8000800000]Jul 7 08:58:40 localhost kernel[0]: standard timeslicing quantum is 10000 usJul 7 08:58:40 localhost kernel[0]: mig_table_max_displ = 73Jul 7 08:58:40 localhost kernel[0]: TSC Deadline Timer supported and enabledJul 7 08:58:40 localhost kernel[0]: AppleACPICPU: ProcessorId=1 LocalApicId=0 EnabledJul 7 08:58:40 localhost kernel[0]: AppleACPICPU: ProcessorId=2 LocalApicId=2 EnabledJul 7 08:58:40 localhost kernel[0]: AppleACPICPU: ProcessorId=3 LocalApicId=4 EnabledJul 7 08:58:40 localhost kernel[0]: AppleACPICPU: ProcessorId=4 LocalApicId=6 EnabledJul 7 08:58:40 localhost kernel[0]: AppleACPICPU: ProcessorId=5 LocalApicId=1 EnabledJul 7 08:58:40 localhost kernel[0]: AppleACPICPU: ProcessorId=6 LocalApicId=3 EnabledJul 7 08:58:40 localhost kernel[0]: AppleACPICPU: ProcessorId=7 LocalApicId=5 EnabledJul 7 08:58:40 localhost kernel[0]: AppleACPICPU: ProcessorId=8 LocalApicId=7 EnabledJul 7 08:58:40 localhost kernel[0]: calling mpo_policy_init for TMSafetyNetJul 7 08:58:40 localhost kernel[0]: Security policy loaded: Safety net for Time Machine (TMSafetyNet)Jul 7 08:58:40 localhost kernel[0]: calling mpo_policy_init for QuarantineJul 7 08:58:40 localhost kernel[0]: Security policy loaded: Quarantine policy (Quarantine)Jul 7 08:58:40 localhost kernel[0]: calling mpo_policy_init for SandboxJul 7 08:58:40 localhost kernel[0]: Security policy loaded: Seatbelt sandbox policy (Sandbox)Jul 7 08:58:40 localhost kernel[0]: Copyright (c) 1982, 1986, 1989, 1991, 1993Jul 7 08:58:40 localhost kernel[0]: The Regents of the University of California. All rights reserved.Jul 7 08:58:40 localhost kernel[0]: MAC Framework successfully initializedJul 7 08:58:40 localhost kernel[0]: using 16384 buffer headers and 4096 cluster IO buffer headersJul 7 08:58:40 localhost kernel[0]: IOAPIC: Version 0x20 Vectors 64:87Jul 7 08:58:40 localhost kernel[0]: ACPI: System State [S0 S3 S4 S5] (S3)Jul 7 08:58:40 localhost kernel[0]: PFM64 0xf10000000, 0xf0000000Jul 7 08:58:40 localhost kernel[0]: [ PCI configuration begin ]Jul 7 08:58:40 localhost kernel[0]: AppleIntelCPUPowerManagement: Turbo Ratios 1234Jul 7 08:58:40 localhost kernel[0]: AppleIntelCPUPowerManagement: (built 16:44:42 Jun 7 2011) initialization completeJul 7 08:58:40 localhost kernel[0]: console relocated to 0xf10010000Jul 7 08:58:40 localhost kernel[0]: PCI configuration changed (bridge=16 device=4 cardbus=0)Jul 7 08:58:40 localhost kernel[0]: [ PCI configuration end, bridges 12 devices 17 ]Jul 7 08:58:40 localhost kernel[0]: mbinit: done (96 MB memory set for mbuf pool)Jul 7 08:58:40 localhost kernel[0]: rooting via boot-uuid from /chosen: <hidden>Jul 7 08:58:40 localhost kernel[0]: Waiting on <dict ID="0"><key>IOProviderClass</key><string ID="1">IOResources</string><key>IOResourceMatch</key><string ID="2">boot-uuid-media</string></dict>Jul 7 08:58:40 localhost kernel[0]: com.apple.AppleFSCompressionTypeZlib kmod startJul 7 08:58:40 localhost kernel[0]: com.apple.AppleFSCompressionTypeZlib load succeededJul 7 08:58:40 localhost kernel[0]: AppleIntelCPUPowerManagementClient: readyJul 7 08:58:40 localhost kernel[0]: Got boot device = IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/SATA@1F,2/AppleIntelPchSeriesAHCI/PRT1@1/IOAHCIDevice@0/AppleAHCIDiskDriver/IOAHCIBlockStorageDevice/IOBlockStorageDriver/APPLE SSD TS256C Media/IOGUIDPartitionScheme/NotQuiteMaxDisk@2Jul 7 08:58:40 localhost kernel[0]: BSD root: disk0s2, major 14, minor 2Jul 7 08:58:40 localhost kernel[0]: Kernel is LP64Jul 7 08:58:40 localhost kernel[0]: FireWire (OHCI) Lucent ID 5901 built-in now active, GUID <hidden>; max speed s800.Jul 7 08:58:40 localhost kernel[0]: USBMSC Identifier (non-unique): 000000009833 0x5ac 0x8403 0x9833Jul 7 08:58:40 localhost kernel[0]: systemShutdown falseJul 7 08:58:40 localhost kernel[0]: IOThunderboltSwitch::i2cWriteDWord - status = 0x00000000Jul 7 08:58:40: --- last message repeated 1 time ---Jul 7 08:58:40 localhost kernel[0]: IOThunderboltSwitch::i2cWriteDWord - status = 0xe00002edJul 7 08:58:41: --- last message repeated 1 time ---Jul 7 08:58:41 M1 kernel[0]: Previous Shutdown Cause: 5Jul 7 08:58:41 M1 kernel[0]: DSMOS has arrivedJul 7 08:58:41 M1 kernel[0]: 1.998956: ath_get_caps[4036] rx chainmask mismatch actual 7 sc_chainmak 0Jul 7 08:58:41 M1 kernel[0]: 1.998970: ath_get_caps[4011] tx chainmask mismatch actual 7 sc_chainmak 0Jul 7 08:58:41 M1 kernel[0]: 2.002983: Atheros: mac 448.3 phy 271.82.002991: radio 0.02.002994: Jul 7 08:58:41 M1 kernel[0]: 2.002999: Use hw queue 0 for WME_AC_BE trafficJul 7 08:58:41 M1 kernel[0]: 2.003007: Use hw queue 1 for WME_AC_BK trafficJul 7 08:58:41 M1 kernel[0]: 2.003016: Use hw queue 2 for WME_AC_VI trafficJul 7 08:58:41 M1 kernel[0]: 2.003025: Use hw queue 3 for WME_AC_VO trafficJul 7 08:58:41 M1 kernel[0]: 2.003033: Use hw queue 8 for CAB trafficJul 7 08:58:41 M1 kernel[0]: 2.003041: Use hw queue 9 for beaconsJul 7 08:58:41 M1 kernel[0]: 2.003112: wlan_vap_create : enter. devhandle=0x92e69620, opmode=IEEE80211_M_STA, flags=0x1Jul 7 08:58:41 M1 kernel[0]: 2.003192: wlan_vap_create : exit. devhandle=0x92e69620, opmode=IEEE80211_M_STA, flags=0x1.Jul 7 08:58:41 M1 kernel[0]: AirPort_AtherosNewma40: Ethernet address <hidden>Jul 7 08:58:41 M1 kernel[0]: IO80211Controller::dataLinkLayerAttachComplete(): adding AppleEFINVRAM notificationJul 7 08:58:41 M1 kernel[0]: IO80211Interface::efiNVRAMPublished(): Jul 7 08:58:41 M1 kernel[0]: AirPort: Link Down on en1. Reason 1 (Unspecified).Jul 7 08:58:41 M1 kernel[0]: 2.095294: setDISASSOC from disconnectVapJul 7 08:58:41 M1 kernel[0]: 2.095311: switchVap from 1 to 1 Jul 7 08:58:42 M1 kernel[0]: ** Device in slot: SLOT--1 **Jul 7 08:58:42 M1 kernel[0]: 2.600681: performCountryCodeOperation: Disconnecting from AP Jul 7 08:58:42 M1 kernel[0]: 2.600693: setDISASSOC from disconnectVapJul 7 08:58:42 M1 kernel[0]: 2.604918: setWOW_PARAMETERS:wowevents = 2(1)Jul 7 08:58:43 M1 kernel[0]: AirPort: Link Up on en1Jul 7 08:58:43 M1 kernel[0]: AirPort: RSN handshake complete on en1Jul 7 08:58:43 M1 kernel[0]: BCM5701Enet: Ethernet address <hidden>Jul 7 08:58:43 M1 kernel[0]: ast_pending=0xffffff8000228b0eJul 7 08:58:43 M1 kernel[0]: cpu_interrupt=0xffffff800022f0aeJul 7 08:59:46 M1 kernel[0]: en1: 802.11d country code set to 'GB '.Jul 7 08:59:46 M1 kernel[0]: en1: Supported channels 1 2 3 4 5 6 7 8 9 10 11 12 13 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140

Similar Messages

AirPort Client Update 2009-002 Issues!

ok so i installed the AirPort Client Update 2009-002 and all seemed well.
However, after not using the mac for a day i turned it on and the clock had gone back to jan 1st 2008 and the laptop would not pick up our wi-fi.
After allowing some incoming connection boxes for some gobbldygook programme names the clock reset itself to the correct time and i retyped my wi-fi password and reconnected.
After a reboot the clock was behaving but the wifi still did not pick up. after retyping the network password, making sure the computer was remembering the network and applying the settings it picked up the signal on reboot.
I am yet to try again.
has anyone else had similar problems after the AirPort Client Update 2009-002?

ok so i installed the AirPort Client Update 2009-002 and all seemed well.
However, after not using the mac for a day i turned it on and the clock had gone back to jan 1st 2008 and the laptop would not pick up our wi-fi.
After allowing some incoming connection boxes for some gobbldygook programme names the clock reset itself to the correct time and i retyped my wi-fi password and reconnected.
After a reboot the clock was behaving but the wifi still did not pick up. after retyping the network password, making sure the computer was remembering the network and applying the settings it picked up the signal on reboot.
I am yet to try again.
has anyone else had similar problems after the AirPort Client Update 2009-002?

OS X 10.5.x AirPort Dropout Issue - Problem with Apple

I am posting this as a new topic in the hope that Apple will take urgent action to resolve these AirPort dropout issues with OS X 10.5.x.
Yesterday, I installed setup a new 40GB partition on my firewire drive and installed OS X 10.5.2 (from my original installation dvd) and did all updates (via Software Update) to arrive at an up-to-date OS X 10.5.5. Only stock standard OS X 10.5.5 installed now.
Some interesting observations along the way:
1. After installing 10.5.2 the AirPort network kept dropping out or stalling.
2. Installed following updates:
- AirPort Utility (5.3.2)
- QuickTime (7.5.5)
- iLife Support (8.3)
- iTunes (8.0)
- Remote Desktop Client Update (3.2.2)
- Java For Mac OS X 10.5 Update 1 (1.0)
I did not update to OS X 10.5.5 at this time.
3. Restarted and AirPort network stable and fast.
4. Ran Software Update again - installed:
- Front Row Update (2.1.6)
- Mac OS X Update Combined (10.5.5)
5. Restarted and AirPort network stable and fast.
6. Ran Software Update again - all software up to date.
7. Repaired permissions with Disk Utility.
Everything has been going fine with connections to the internet with Safari - until this morning.
My 'clean' OS X 10.5.5 installation is now suffering from the same AirPort network dropouts - no 3rd party applications installed. Ran OK for a day, but after being shutdown for 5 or 6 hours, the problem arose following startup this morning.
Conclusion:
1. AirPort problem with OS X 10.5.x; or
2. AirPort problem with new 17" MBP; or
3. Problem with AEB 802.11n (gagabit ethernet); or
4. Problem with DSL modem or ISP connection.
Comments on item 1 - think I have conclusively eliminated 3rd party software.
Comment on item 2 - no problems indicated by TechTool Delux or TechTool Pro 4; works OK via ethernet connection.
Comment on item 3 - previously did factory reset and textbook setup on AEB. Connection via AEB 802.11g relay and remote work fine.
Comment on item 4 - fact that other computers connect OK and this computer can connect OK via ethernet rules out problems with DSL modem and ISP.
Draw your own conclusions, but I am now certain the problem is clearly with Apple.

Hello,
looks same to me.
the log says:
kernel AirPort: Link Down on en1
kernel unable to collect channel list from hal;(...)
my AEB is just 2 ms away from the MacBookPro, the AEB is brand new.
In the moment I have an ethernet cable going from the router through the house, because the AEB is unrelyable. I used all the tricks people posted and said it would solve the problem, which is not the case for me. Dropouts just continue.
With the old ufo-style extreme there was no problem at all.
So please Airport developers put effort to solve the problem and suffering of users.
thanks

Has anyone got the AirPort Client Update 2009-00 to work

As I have frequently posted here SL has killed my Airport.
Having waited patiently for FOUR MONTHS Apple have finally issued AirPort Client Update 2009-00.
It makes no difference to me.
Has this actually worked for anyone?

In my case, I bought my MBP with Tiger then upgraded to SL and it made my airport behave randomly soo I opted to roll back the OS until a fix is made to the issue.

Airport client Update 2009-02 buggy?10++min system start, OS bogged down

I installed the Airport Client update a little over a week ago via Software Update. Since then I've had intermittent problems with the airport connection being dropped, but a larger problem is that the system (especially Safari) seems to slow down to the point that I have to force quit programs and reboot. The reboot brings up white screen with the grey apple and a progress bar - AND it takes between 10 and 15 minutes for the OS to load.
This massive time to boot started when the Airport client update was installed and happens now to my iMac on every startup.
3 days before the Airpot update there was also a Java update. I'd love to know what the problem is - it's more than a minor nuisance . I also notice that I can hear the the hard drive running nonstop the same time the system is freezing up. This seems to be at it's worst when the screen saver has been running for a while.

Sorry if I missed it...which of your computers is acting up?
Did you update via Software Update or did you download the combo? If you used Software Update, get the Combo updater instead and re-apply:
http://support.apple.com/kb/DL959
As well, try resetting some of the hardware involved (PRAM~NVRAM). See this Apple KB for details, etc.:
http://support.apple.com/kb/HT1379
Be sure to make another permission repair pass as well.

Leopard 10.5.6, Kernel Panic after Airport Client Update 2009-001

Hi Mac users,
Actually I'm working for an international school and we have a lot of students with Mac computers. Since 2 weeks now, all Mac crashed (Kernel Panic) several times per day. This issue seems arrived just after the Airport Client Update 2009-001.
As we didn't perform any change on our wireless infrastructure, we think it's an Airport issue.
Here a sample of Kernel Panic:
Fri Mar 20 10:22:50 2009
panic(cpu 0 caller 0x001A9C68): Kernel trap at 0x008d7055, type 0=divide error, registers:
CR0: 0x8001003b, CR2: 0x00f63000, CR3: 0x01892000, CR4: 0x00000660
EAX: 0x00036036, EBX: 0x00000003, ECX: 0x00000000, EDX: 0x00000000
CR2: 0x00f63000, EBP: 0x56a37ca8, ESI: 0x07af7d70, EDI: 0x000000a2
EFL: 0x00010246, EIP: 0x008d7055, CS: 0x00000008, DS: 0x06d00010
Error code: 0x00000000
Backtrace (CPU 0), Frame : Return Address (4 potential args on stack)
0x56a37a48 : 0x12b4f3 (0x45b13c 0x56a37a7c 0x1335e4 0x0)
0x56a37a98 : 0x1a9c68 (0x464700 0x8d7055 0x0 0x463de0)
0x56a37b78 : 0x1a038d (0x56a37b90 0x2e723 0x56a37ca8 0x8d7055)
0x56a37b88 : 0x8d7055 (0xe 0x48 0x56a30010 0x380010)
0x56a37ca8 : 0x8dd421 (0x6ddb700 0x7af7800 0x56a37ec0 0x1)
0x56a37dc8 : 0x8ad8ab (0x6ddd800 0x7af7800 0x5275a700 0x56a37ec0)
0x56a37e88 : 0x8f2233 (0x42a23000 0x56a37ec0 0x9a0 0x0)
0x56a37ee8 : 0x85ec55 (0x42a23000 0x0 0x0 0x15)
0x56a37f18 : 0x4224ff (0x6da2800 0x6db00c0 0x1 0x19eb5b)
0x56a37f68 : 0x42165c (0x6db00c0 0x80f8404 0x56a37fc8 0x3df460)
0x56a37f98 : 0x42133e (0x6cf7a00 0x50b058 0x73b1c3c 0x1)
0x56a37fc8 : 0x1a017c (0x6cf7a00 0x0 0x1a30b5 0x80f8be0)
Backtrace terminated-invalid frame pointer 0
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AirPortBrcm43xx(362.27.0)@0x856000->0x996fff
dependency: com.apple.iokit.IO80211Family(215.1)@0x837000
dependency: com.apple.iokit.IOPCIFamily(2.5)@0x61e000
dependency: com.apple.iokit.IONetworkingFamily(1.6.1)@0x821000
BSD process name corresponding to current thread: kernel_task
Mac OS version:
9G55
Kernel version:
Darwin Kernel Version 9.6.0: Mon Nov 24 17:37:00 PST 2008; root:xnu-1228.9.59~1/RELEASE_I386
System model name: MacBook5,1 (Mac-F42D89C8)
What can we do to solve this ? Can we find a solution without saying to the students "+please reinstall with the archive option but avoid the Airport Client Update 2009-001+" ? We tried to downgrade the wireless kernel extension to the previous version, without success.
Thanks in advance for your help and your advices.
Best Regards

"My issues have mostly disappeared"
Do you still have issues?. I just spent all Sunday and half morning until I found it was paragon. Not only It panicked every time I logged in, also screwed my time capsule disk (couldn't restore from it). With so many restarts I had a really corrupted RAID disk so since this is my second full reinstall with no time machine, I don't want to get even close to Paragon unless it runs flawless.
I hope this may help: My solution now is Parallels over a NTFS bootcamp partition. I have a full NTFS disk which I use to bootcamp, since parallels allows you run over it instead of a virtual disk NTFS on HFS+. You can read and write back and forth.

AirPort Client Update 2009-002 broke Wireless-n!

After applying AirPort Client Update 2009-002 on Snow Leopard 10.6.2, I lost wireless-n capability! I am able, however, to connect to "g" networks without problems.
I have tried repairing permissions, deleting .plist files mentioned here but nothing seems to help.
I have a simultaneous dual radio Linksys WRT610N router and prior to the update it worked fine (on 5GHz band), now it detects the "n" network on 5GHz band, but is not able to connect.
System profiler shows the following (I am connected to "g" network for now):
Software Versions:
Menu Extra: 6.2 (620.24)
configd plug-in: 6.2 (620.15.1)
System Profiler: 6.0 (600.9)
Network Preference: 6.2 (620.24)
AirPort Utility: 5.4.2 (542.23)
IO80211 Family: 3.1 (310.6)
Interfaces:
en1:
Card Type: AirPort Extreme (0x14E4, 0x88)
Firmware Version: Broadcom BCM43xx 1.0 (5.10.91.26)
Locale: FCC
Country Code: MK
Supported PHY Modes: 802.11 a/b/g
Supported Channels: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 36, 40, 44, 48, 52, 56, 60, 64, 100, 104, 108, 112, 116, 120, 124, 128, 132, 136, 140
Wake On Wireless: Supported
Status: Connected
Network Utilty shows:
Wireless Network Adapter (802.11 a/b/g/n)
Any ideas?

UPDATE:
Still having the same issue... I'm really despirate here because my school library is wireless only.
I read that some people were fixing problems by replacing the IO80211family.kext file with a previous one. I tried what I think was the 10.6.1, the 10.5.2, and the 10.5.8.
I was able to replace the 10.6.1 with no problems, (and no fix, and I think the 10.5.8 too) but as soon as I tried the 10.5.2, I got the "no airport card installed" when I clicked on it. Even when I put the 10.6.2 one back in, same message. had to revert to my latest time machine backup and start over with the problem. I did repair permissions once so maybe that triggered all kinds of problems in there...
For some reason I got my 10.5.8 system to booted up off my external to work upstairs (my SL never works upstairs). It was a one time thing though I think. I'm just lost now... I may just try to time machine back to my 10.6.1 machine and take the data loss hit. For some reason I don't think it will work though.
We'll see. Please help if anybody has any more ideas.

Airport Client Update 2009-02...

... seems to have broken my connection. It's either that or the recent combined OS update causing my connection problem. I installed the OS update yesterday and the Airport Client Update today and at first I didn't notice any difference until tonight when it broke down. Now my computer won't find my Airport Express even when the LED- light's green. I've tried hard resetting it, reinstalling the client update, the one time it found my airport I tried to load up the previous setting which it did but still I can't go online wirelessly. At the moment I'm using the ethernet cord to access the net but that won't do in the long run, I need my wireless connection. As it is I'm starting to fear any update from Apple whatsoever because every time there's something in it that screws things up badly and especially when it comes to the Airport issue.
Please, tell me there's some one with a pocketful of solutions for this. I'm pretty tired of swearing because I just did the stupid thing called updating my computer.

Michael Gullbrandson wrote:
... seems to have broken my connection. It's either that or the recent combined OS update causing my connection problem. I installed the OS update yesterday and the Airport Client Update today and at first I didn't notice any difference until tonight when it broke down. Now my computer won't find my Airport Express even when the LED- light's green. I've tried hard resetting it, reinstalling the client update, the one time it found my airport I tried to load up the previous setting which it did but still I can't go online wirelessly.
Please, tell me there's some one with a pocketful of solutions for this. I'm pretty tired of swearing because I just did the stupid thing called updating my computer.
You might try resetting your connection settings using the steps listed in this message:
http://discussions.apple.com/thread.jspa?messageID=10695921&start=1
They're not guaranteed to solve the problem, but they'll only take you a minute or so to try.

Reverting from AirPort Client Update 2009-002 to anything else.

I never update Airport because it seems every time I do, something goes a miss. Everything was perfect, no issues at all. By mistake, I did update to Airport Update 2009-02.
Now connections randomly drop to AP, can't disable WiFi, when it does reconnect have to force IP renew, then moments later connection drops again.
I want to revert. Yes, I know, there is no way to do that.
I will not accept:
+ Try fussing with my AP (SSID, Security, etc) that's not the problem - the problem is clearly the driver - it worked fine until the dumb update.
+ Try deleting \ adding networks.
+ Archive and Reinstall.
+ TimeMachine restores.
Perhaps there are some files I could extract from the package and replace on my machine?
That's my line of thought.. Any ideas are appreciated, except for the ones excluded above. Thanks
<Edited by Host>

rferrentino wrote:
Just extracting the 2009-01 pkg file only has only the IO80211Family.kext file …
If you mean AirPort Client Update 2009-001, it has much more than a single file in it. The installed IO80211Family.kext appears to be a single file, but like many items it is actually a package (a special kind of folder) containing many files.
In Finder, right-click on the installed version in /System/Library/Extensions & choose "Show package contents" to see what I mean. Likewise, you can use Pacifist to fully expand the package contents of the download & see something similar.
Just replacing this file + fixing permissions did not work.
No surprise there -- it is what my "hard way" comment alluded to. To understand why it didn't work, consider first that a package is actually a structured group of related files containing resources designed to work together as a unit. The files often have internal references to one another & other mutual dependencies in their code. Thus, you can't simply substitute one file with another from a different package -- the files won't have fully compatible resources & won't work properly as a unit.
But there is more to it than that. An installer doesn't just replace files. In fact, although the package contents of an installer & the installed package look similar, they are actually quite different. (Comparing the two as suggested above with Pacifist & Finder will show that.) You can think of an installer package as the raw ingredients of the installed package plus the recipe to make it, housekeeping instructions for tidying up beforehand & afterwards, & the resources the process requires to do all of that. (Check the "Resources" tab in Pacifist to show the resource files.)
Often there is even more to it than that. Many OS packages have mutual dependencies on one another, just as their contents do. The "family" name isn't an arbitrary one -- just as with any family there are parents & children in the IO (input/output) extension family. Mixing members of different families leads to conflicts, often ones that interfere with more than the functionality of the 'foreign' member. Apple's software update mechanism & the installers themselves are designed to prevent this mismatch; when you bypass that it is up to you to manually do everything they do if you expect everything to work together without problems.
The root of the problem? The old driver worked, the new one has issues. How much simpler could it be?
As I hope the above makes clear, it isn't as simple as it seems. You can think of the OS as a very complex machine with thousands of precision parts, each of which must be undamaged & compatible with the others. One bad part can cause problems seemingly quite unrelated to its function, making the job of finding & replacing it much less straightforward than you might imagine. And if you don't do that, the damage will spread, especially when you 'overhaul' (update) the machine with new parts but miss the bad one.
That's why you so often see the advice to reinstall the OS. In effect, that replaces the machine with a brand new one with known-good parts, sparing you the usually very tedious task of tracking down & replacing just the original bad part & any others it has damaged.
But you said in the beginning that you don't want to do that. That seriously limits your choices, mostly to those that require substantial knowledge of the OS & its internal interdependencies to achieve success.
In short, it isn't a simple machine. Treating it as if it is won't get the job done.

Airport DHCP Issues

Hello,
Multiple Apple clients are experiencing issues on our WLAN. The symptoms are:
- Client remains associated with access point (Airport icon never shows disconnect and AP logs never show disassociation)
- No access to internet and local IPs (demonstrated through browser, email, and pinging IPs)
- Access can be restored by turning Airport on and off or sometimes just waiting a while
- On the server, the Airport issues correspond with multiple DHCPREQUEST/DHCPACK pairs, for example:
Oct 2 08:55:58 server dhcpd: DHCPREQUEST for 10.1.45.179 from 00:34:f5:15:a2:f5 via eth0
Oct 2 08:55:58 server dhcpd: DHCPACK on 10.1.45.179 to 00:34:f5:15:a2:f5 via eth0
Oct 2 08:55:58 server dhcpd: DHCPREQUEST for 10.1.45.179 from 00:34:f5:15:a2:f5 via eth0
Oct 2 08:55:58 server dhcpd: DHCPACK on 10.1.45.179 to 00:34:f5:15:a2:f5 via eth0
These multiple requests never coincide with T1 on the DHCP lease--the DHCPREQUEST from the Airport client always comes before T1.
While it appears that there may be reception/interference issues (a situation where the DHCPACK packet from the server never reaches the client and the client is forced to resend, this NEVER (and I truly mean never) occurs with Windows clients of any flavor.
Configuration Info:
Clients: running MacOS 10.4.11 through 10.6.1 (but always the most updated of their particular OS)
Server: Latest version of CentOS.
Access Points: HP Procurve 420s: SSID is broadcast and security is WPA/WPA2-PSK (AES).
Hardware: iBook G4s through the latest MacBook Pros.
This has continued to occur despite the following changes on the APs:
- moved from TKIP to TKIP+AES to AES
- moved from exclusively WPA2 to exclusively WPA to WPA/WPA2
- Halving the beacon interval
- Halving the fragmentation threshold
This has also continued to occur despite the following changes on the clients:
- moving Airport to the top in "Set Service Order" under Network Preferences
- deleting the Airport preferences .plist file
This has also continued to occur regardless of whether Spanning Tree is enabled on the network switches.
If anyone is familiar with this issue and the solution any assistance would be greatly appreciated.

Reception/interference issues have nothing to do with the operating system, so saying Windows clients don't experience reception/interference issues doesn't help narrow things down.
If for some reason the DHCPACKs aren't getting back to the clients, you'll see continued requests.
What IP address, if any, do the Macs hold while they cannot ping local hosts? The address they're requesting? A self-assigned IP address? A former IP address on the same subnet?
While it's not your particular issue, you may also want to read this article:
http://www.net.princeton.edu/multi-dhcp-one-interface.html

Airport Client Monitor for Intel

It appears that the ever-useful Airport Client Monitor does not work on Intel Macs. Am I wrong - is there a universal version?
I've just found a donationware utility "AP Grapher" that may be a useful substitute available here:
http://www.chimoosoft.com/products/apgrapher/
I've been testing for a day so far. It looks good - I think a donation is deserved. I've only glanced at the "stumbler" function, but that looks good too.
From the Macreviewcast
"AP Grapher is a freeware tool for plotting the strength of a network as a function of time. AP Grapher has received a recent (Dec 06) update to Universal Binary along with some performance enhancements. It now does all the stuff that the Airport Client Monitor does as well as what MacStumbler does in one tool. The most valuable part is the time domain plot of Airport link characteristics. The plot will record data for as much as half an hour."

this would appear to the the problem.
Actually, NONE of the older tools that report on wireless networks or status work anymore.
iStumbler has been fixed. I imagine that the rest will get fixed in time.
- gws

Airport client to hp wap

I am trying to connect an ibook g4 to a campus wireless network that uses hp procurve waps supporting 802.11b&g.
The network uses no encryption and authenticates wap access based on MAC address ONLY (as in the hexadecimal adapter address, not "MAC"intosh) - no WEP, no WPA, etc.. The campus IT department has already entered the airport client MAC address into the authenticaion server. ALSO, the wap's SSID is cloaked/not broadcast, so the Airport will not automatically see the network without being "told" of the cloaked SSID in advance.
The way the airport client configuration process is designed, I don't even know which field constitutes the SSID, etc., so I'm failing to get it configured right.
Any help on what to enter where would be appreciated.

Thanks. The problem was actually due to a stupid mistake on my part. When I submitted the airport mac address to be used on the authentication server, I handwrote a small "b" so that it looked like a 6. As your note confirms, I had everything else configured correctly. Consequently, as soon as the mac address was corrected on the authentication server, the wireless connection came up fine.

AirPort Client Update 2009-002 Connection Lost

I just installed the AirPort Client Update 2009-002 and now when my computer goes to sleep it loses the internet connection. It reconnects when it awakes from sleep but I need the connection to stay alive even when the computer is in sleep mode.
Was something wrong before or is something wrong now? How can I get the old functionality back? I've looked for an option but can't find anything. Thanks for your help!

I think I'm having the exact same problem, so I'm posting here instead of starting a new topic.
Before a few days ago I was only using a PB G4 with 10.4.11 and an Airport Extreme 801.11n and didn't have any troubles with this set up. I could close the Powerbook, open it up later and almost immediately have access to my wifi. Or, I could leave it open and it would maintain a connection even when no activity (by me, physically) was going on.
I recently got a new MBP (and thus 10.6, which I updated to 10.6.2). If I close the MBP, putting it to sleep, and then open it, I can not access my network. I get the connection timeout message you mentioned. But here's the thing, I also can't get online with my older Powerbook.
I also also tried this: having both side by side and working. I close the MBP, leaving the PB open. I wait a few minutes and try reloading a page on the PB and it says I'm not connected and it refuses to connect.
The only solution I've found so far seems to be to pull the power plug out of the base station, plug it in, and wait a minute or two. I'm then able to access my wifi again.
Did the software update somehow mess with my base station? It's running version 7.3.2.
Do I need to trash some setting? Do I need to tweak some network setting in 10.6 that I don't know about?
I wish I knew if I was having the problems in the few hours between using 10.6 out of the box and updating to 10.6.2 (and a few other things), but I don't think I ever put it to sleep during that time.

Airport client update

I notice a new airport client update out, and is says it is for early MBP's 2008. Software Update doesn't want to see it. Any ideas what models this is for really?

Software update doesn't see it. I am assuming that SU is what would tell me if I needed it (meaning this is isn't something that is user decided). I have an Early 2008 MBP 15", but SU doesn't see it at all. I do have 10.5.8 installed.

Airport client update 01

i installed the Airport client update 01 last night and now i can't access the internet. It keeps asking for a password, all of which do not work. Is there any way to solve this problem? can i go back and uninstall?
i've read some of the other posts about Airport client update 02 but i don;t really understand what to do!

I'm having the same problem. I cannot be sure the problem is incorrect password since it only throws 'connection timeout'. I've tried changing the password, using AES instead of TKIP, using 802.11b instead of 802.11g and even all the available channels in my wifi base station.

Minor Airport Client Issue

Similar Messages

Maybe you are looking for