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?

Similar Messages

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-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.

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 client update 2009-002

I just downloaded the Airport update from software update and restarted,(took quite awhile) etc. all is working well I guess I had no problems before but now boot time was 23 seconds it is now 32 seconds even after I restarted and shut down a couple times.I did a permissions also what could be causing such a long boot time. I have a very clean system no 3rd party only apple apps no login items etc I even have a very basic installation no printer drivers no addl. fonts or languages so I have exceptional boots but now this just bugs me any sugestions.

32 seconds is a pretty good time for a cold startup or even a restart. I wouldn't worry about it at all. I'm sure that is faster than my MBP is, as well as much faster than any Windows PC.
Were I you though I wouldn't even shut down the machine under regular use. Close the lid when you're done using it, then open it again when you need it. I rarely, if ever, shut down my MBP. In fact, I'm quite sure it hasn't been shut down for more than 2 days time (total) in the year that I've owned it. As a result, boot time isn't really important to me at all, nor should it be to any Mac user. The only time you really should shut it down is if you won't be using it for at least a few days. The only reason to there would be to preserve the battery and/or save yourself some (very small amount of) energy. Otherwise there is no reason to.
--Travis

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.

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-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.

Massive wireless connection problems since airport client update 2009-001

Hi,
I have a brand new MacBook Unibody 2 GHz with 4 GB RAM and an OSX installation up to date. Since the update of the airport client software 2009-001 on March 4th, I have MASSIVE problems to establish a working wifi network connection.
I use as APs a D-Link 614+ with up to date router firmware, a ZyXel Wireless Lan Router 100 (some ISP bulk router from my provider) with up to date router firmware and an AVM 7170 Wireless LAN router with up to date firmware. The last one is extremly expensive and state of the wifi art.
First of all, I can not establish a stable connection to no one of my wifi routers. After entering the passphrase for WPA, an established connection fades out in 20seconds-3minutes. And trying to establish a connection lasts minutes! Mostly OS X is telling me "Out of time". But in wireshark there is in due to my research mostly no packet transfer over the en1 wifi device at all! The airport card sometimes is fooling around with me!
I tried serveral configurations with all my routers differing in encryption (Wep->Wpa->Wpa2) or TTL of the packets or whatever the router is configurable. But I could not solve this problem for me.
Wifi is like dead.... not working reliable... or not working at all.
I have also used Wireshark to get into this problem. With start of an connection with EAPOL, it lasts serveral seconds till the airport card replies to the AP. Airport should response in milli seconds.... but no!
Then DHCP handshake sometimes finishes succesfully, but the airport card turns the correct ip address into a wrong ip address.
MacBook: 0.0.0.0 to 255.255.255.0 Request "give me an ip"
AVM Router: 10.255.128.1 to 255.255.255.0 ACK "TAKE 10.255.128.25"
You would think the airport card would take the given 10.255.128.25, but no it takes 192.168.0.100 and can not establish an internet connection, OF COURSE!
What the **** is the airport client firmware doing while takeing the wrong IP adress, which is not given by the DHCP Server?
And I have also discovered, that the airport card is sending out tons of ARP requests like:
MacBook: MacBookMacAdress to Broadcast ARP "who has 10.255.128.1?" (my avm router)
AVM Router: AVMMacAddress to MacBookMacadress ARP "I am at ....."
But hey, the airport card seems not be able to understand the avm reply and requests again immediately uncountable times!
Apple, please fix your airport client software. It seems to me the parser within the firmware for packet parsing has some kind of dead locks or sth else.
This are just three hints for the firmware developers.
PLEASE FIX THAT!

I don't know if this will fix your problem or not but it fixed my airport from self assigning ip's instead of taking the proper one.
Florida dude from this thread http://forums.macosxhints.com/showthread.php?t=24540&page=5 says
"I've been having the "self assigned IP" problem now for a bit. It all started when I let the battery run down, and I've been working with it now for a couple of weeks (except it affects ethernet AS WELL as airport).
I've found a temporary workaround. Go to Security in network preferences, and select firewall. Then select "allow all incoming connections". Go back to the preference pane, and select network. After about 15-20 seconds, it DHCP should assign a good IP. Then go back and reset your firewall.
Works ok, but if your Mac goes to sleep, you need to repeat."
Give it a shot, it worked for me.

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.

Installing 2009-001 Airport Client Update - very poor wireless performance

After installing the 2009-001 Airport Client update I cannot reliably connect using wireless. I have an early Core Duo Black Macbook running 10.5.6. Up until this point I have had zero problems with wireless (even with 10.5.6).
At home I can sometimes connect if I right by my wireless access point.
At work I can connect in some places but not in others.
Often I can connect for 1 minute and then the connection drops and nothing I do after that will restore it.
I have tried many many different things to no avail. Please do not ask me to reset PRAM, delete plist preferences, add a new location, turn off IPv6 etc etc.
I have tried them all!
My console log reports:
Error: Apple80211Associate(0 failed -6
Error: airportd MIG failed = -g (null) (port=67087)
Error: processcommanddict() failed
My suspicion is that multiple wireless networks in the same place is maybe part of the problem.

Replacing my Airport Extrreme card seems to have fixed the problem.
I can't explain why my old Airport Extreme would suddenly break after the 2009-001 Airport client update. But after a complete reinstall of Leopard my Macbook still wouldn't connect reliably. I even took the Airport card firmware back to 1.2.2 and it still made no difference. It looks as if the 2009-001 update did something permanent or stressed some component so that it no longer works reliably.

After Security Update 2009-002 no connection to server

After running Security update 2009-002 I can not connect to a server, e.g. a webdisk with Apple+K command. Rebooting does not help, nor entering fresh login data.
Does anybody have a clue?
thanks in advance,
Flip

Hello Flip, and a warm welcome to the forums!
One way to test is to Safe Boot from the HD, (holding Shift key down at bootup), run Disk Utility in Applications>Utilities, then highlight your drive, click on Repair Permissions, Test for action in Safe Mode...
PS. Safe boot may stay on the gray radian for a long time, let it go, it's trying to repair the Hard Drive.
Open Keychain Access in Utilities, use Keychain First Aid under the Window Menu item, then either check the Password under that item, change it, or delete it and start over.
Also remove it from the CMD+k window by highlighting it and clicking the little minus button.
Resetting your keychain in Mac OS X...
If Keychain First Aid finds an issue that it cannot repair, or if you do not know your keychain password, you may need to reset your keychain.
http://support.apple.com/kb/TS1544
Reboot, test again.

PPC Security Update 2009-002

May be of some use to other or could be we just had a bad day.
Installed Security Update 2009-002 (last update was 2008-003) and find that amavisd will not run. Seems that MIME::Base64 is missing which stops amavisd from running. Reinstalled MIME::Base64, and all fine now.
As I say, could be a one off.

Tim,
the Perl issues were present in Security Update 2009-001. Since you did not update to that version, 2009-002 installed those changes as well.
As a rule of thumb, if you skip an update, you always need to go back and read its release notes together with the ones belonging to the current update. Same applies to combo updaters.
Alex
Message was edited by: pterobyte

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.

AirPort Client Update 2009-002 Issues!

Similar Messages

Maybe you are looking for