I followed up with Apple this morning on my trouble report on the WWAN update. The technician said the Apple engineering is investigating a connection between the update and certain models of Intel Macs and wireless routers.
You can help Apple troubleshoot and solve the problem by helping them collect as much relevant information as possible. If you are having Airport connection stability and reliability issues since installing the WWAN update of February 19th, open a ticket with Apple and send them the results of your system profile.
The update *may* be coincidental, or it may be mitigated by other factors.
Have you used a WiFi sniffer to see what other WiFi signals are in your vicinity? Anyone on the same channel? Have you tried other channels? Give channels 1, 6 and 11 a try.
Have you tried running without encryption?
Comment by maurizio — March 6, 2007 @ 12:29 pm
The latest update broke my Wifi too the (002) update. It appears in the Apple Forums, that those with Dl-624 and a few Berkley models of Routers with WPA encryption have the most problems. Turning WPA off or dropping to WEP 64bit usually fixes the broken connection. Should we have to drop our security or Apple make us another patch quick!
This repair does not work for me on my WPA encryption network it only works with security off. Same thing logs in to network. Pops up the window- “There was an error joining the Airport network “my network name here”. Then offers Try again or OK, click OK then after a few seconds the Airport signal strength fades away. The only way it will login in is if I turn WPA off in my Dl-624 router.
Comment by spaguy — March 11, 2007 @ 8:21 pm
I have a DLink DI-624 C revision. I turned off the WPA encryption and turned on WEP 128 ASCII encryption. (Apple’s Wifi iterface calls it “WEP 40/128 ASCII encryption”.) That’s working for me.
On my systems I was checking the logs before the above “fix” and found that the DLink was seeing the Macs, and authenticating then, then DHCP’ing them fine. The macs, however, dropping the authentication and retrying. They were seeing log lines in console.app like the following:
Mar 14 19:12:28 Foobar /System/Library/PrivateFrameworks/Apple80211.framework/Resources/airport: Error: WirelessAssociate2() = 88001006 for network barfoo. The operation timed out.
(Computer and network name changed.)
Comment by Mongo — March 14, 2007 @ 7:46 pm
Mongo:
Unfortunately, Apple has just forced you to reduce the security of your wireless connection to accomodate a failing in their software — a failing that didn’t exist before the WWAN update, mind you.
Mark
Comment by Mark — March 14, 2007 @ 9:15 pm
The same problem seems to appear also in some open network. This is the one I got trying to connect to a 3COM DSL Wifi router: Error: WirelessAssociate2() = 88001006 for open network.
This router doesn’t have any WPA or WEP key, it’s just open with a filter on the MAC address (Which of course was filled in the router).
Ahhh, very very bad!
Comment by Giampaolo — April 3, 2007 @ 2:33 pm
I have MAC and LinkSys router.
The devices were working fine until i enter a wireless network handling 802.1x and using WPA. I enter at this wireless fine and i was working fine, but qhen i came back to mi Linksys a got the error: System/Library/PrivateFrameworks/Apple80211.framework/Resources/airport: Error: WirelessAssociate2() = 88001006 for network
Comment by JLAM — August 14, 2007 @ 3:07 pm
[...] read more | digg story [...]
Pingback by Help Apple solve the WWAN update problem « Airports USA — October 18, 2007 @ 7:46 pm