Temporary workaround for 2007-004 Airport issue (Anecdotal)

After re-installing the Wireless-N enabler on my 17in. MBP 2.33 (post Airport 2007-004), I have not experienced the connection drop for days now. Clearly this is not a fix or anything--just something others might want to try out. The dropping connection was the only issue I had.

OK, after some further experimenting, I changed the multicast rate on my airport express. It was set at 6Mbps, and I changed it to 2Mbps.
I have read that the default multicast rate for previous 802.11g versions of Airport basestations is actually 2mbps. Excellent results so far !! I have set up a terminal command to continuously ping my airport router address every 15 sec, and there have been virtually no dropped packets so far over many hours.
ping -i 15 10.0.1.1
Interestingly, in Apple's Airport Admin software in my MBP there is no option to set the rate at less than 6Mbps (!!!!), so I had to use the Windows XP version of Airport admin software to make this change using a windows machine. Using the XP software you can set the muticast rate as low as 1Mbps.
If you are using Apples airport admin software (Tiger and Leopard) and you commit any sort of change in settings, the multicast rate will be re-set at a minimum of 6Mbps. My understanding of the multicast rate is that setting it too high is similar to shrinking the coverage area of the basestation, and limiting access only to clients who can transmit at the required multicast rate.
So my new theory is that the dropouts are caused by the MBP dropping off the airport due to not being able to achieve the set multicast rate. (this could be due to factors such as low signal strength, excessive interference or noise).
If you are using Apples more recent Airport admin software, you are having a minimum 6mbps muticast rate set, and this might be too high for your particular environment.
Just a theory.
(oh yeah, I enabled interference robustness on the MBP and the basestation just for good measure)

Similar Messages

Issues with 2007-004 AirPort Software Update

Hello - I saw some threads around this re: other updates.. however, I have a MacBook Pro 15.4" with version 10.4.10. This weekend, Auto Software Updates updated the Mac OS with the 2007-004 AirPort patch. Prior to this, I had perfect 801.11NG connectivity with my router (D-Link DIR-655 N-Extreme) - all 4 bars lit up no matter where I was in the house. However, since this patch, my connectivity has become very flaky. Sometimes I'll have strong connectivity for a few hours, then it will suddenly drop (will go from 4 bars to 3 - then will have performance drag on my applications or drop completly).
I notice while watching my router statistics page that throughput drops from 50-60mb down to 11 when it drops.
We have an iMac in the house which is NOT experiencing this issue (it is on 2007-003). I also have 2 Apple-Tv's, neither of which are having this issue either.
This is extremely frusterating - as not having stable wireless on a laptop is very painful. I've noticed threads where this patch was suppose to fix this problem for people who had 2007-003 patch. For me, it has caused the reverse.
Any recommendations or thoughts? I'd like to roll-back to 2007-003, but it's not clear how to do this - but if I could, I could at least isolate it to the patch, and not some other coincidence.
Thanks, Ed

The light sometimes remains on, even if i lock the keypad. Beside this, i noticed take my battery lasts like 1 hour while the light is on. This happens few times, but is really annoying.. Also, i now that the theme effects are not essential, but i want to keep my phone fully functional, so i'd like to know what's this issue about..
@metalfan I didn't expected a quick answer, i was only preoccupied for these problems
How can i to restore the original firmware?
I tried to remove my sim(also i don't use a memory card), but nothing changes...

[svn:fx-trunk] 10526: Temporary workaround for A+ bug SDK-23387.

Revision: 10526
Author:   [email protected]
Date:     2009-09-22 21:48:33 -0700 (Tue, 22 Sep 2009)
Log Message:
Temporary workaround for A+ bug SDK-23387.
The LinkNormalFormat, LinkHoverFormat, and LinkActiveFormat classes have been removed from FXG, and the FXG compiler was autogenerating static vars of these types (for linkage reasons?) that no longer compiled. I've commented out the offending lines in FXGCompiler.java, but we need a correct fix to cope with the fact that the way hyperlinks are formatted in FXG has changed.
Instead of formatting hyperlinks by writing
tag) but at least it can once again compile FXG as long as it doesn't involve styled hyperlinks.
QE notes: None
Doc notes: None
Bugs: SDK-23387
Reviewer: Carol
Tests run: ant checkintests
Is noteworthy for integration: No
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-23387
    http://bugs.adobe.com/jira/browse/SDK-23387
Modified Paths:
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/fxg/FXGCompiler.java

error dateField not selecion date 27/11/2002 ?
This is bug flex 3 ?
thanks

[svn] 4910: Implementing workaround for history manager rendering issue ( Firefox/Mac) caused by a long standing player bug.

Revision: 4910
Author: [email protected]
Date: 2009-02-10 11:51:58 -0800 (Tue, 10 Feb 2009)
Log Message:
Implementing workaround for history manager rendering issue (Firefox/Mac) caused by a long standing player bug.
Bugs: SDK-17020.
QE Notes: None
Doc Notes: None
Reviewer: Alex
Tests: DeepLinking
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-17020
Modified Paths:
flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/managers/BrowserManagerImpl.as
flex/sdk/branches/3.x/templates/html-templates/client-side-detection-with-history/history /history.js
flex/sdk/branches/3.x/templates/html-templates/express-installation-with-history/history/ history.js
flex/sdk/branches/3.x/templates/html-templates/no-player-detection-with-history/history/h istory.js

This is a workaround for the MBP wireless issue

There have been many topics on the MBP wireless issues already, but I thought some people might find this workaround helpful.
Firstly, my system is a 2.2Ghz MBP, running 10.4.10, and also airport extreme update 2007-04. I am using an airport express base station. My previous Powerbook never had any wireless problems, so I really couldn't blame the basestation for the MBPs poor wireless.
Warning - The workaround requires a little bit of work in the terminal. A little bit of understanding of how networks work is assumed here as well. So it is probably not for everyone ...
What I have observed - whenever the MBP loses connection, the airport basestation IP and MAC addresses are missing from the ARP table.
- To view the ARP table, type (in a terminal window) arp -a.
So, when the MBP wireless hangs, open up the terminal and type that in.
Do a Cntrl-C if the arp command is hanging and not returning anything.
In normal situations, a list of IP addresses and MAC addresses will show up.
As others have already noted, clicking on the airport icon in the menubar, will magically bring the wireless back to life. When this happens, the ARP table also gets magically populated correctly. Coincidence? I think not!
So, the workaround is to store a PERMANENT entry in the ARP table for the airport basestation IP and MAC address. In my case, I can use the Airport Utility software to confirm what the basestation IP and MAC addresses are (note MAC address = Airport ID in Airport Utility). I found the basestation IP=10.0.1.1 and the MAC=0:11:24:07:d7:f
To create a permanent ARP table entry for my airport basestation, I opened up a terminal window, and did the following -
1) login to my administrator account
2) type in the following command sudo arp -s 10.0.1.1 0:11:24:7:d7:f
3) type in my administrator password to authorise the change
4) type in (to confirm the changes have been made) arp -a
5) logout of my administrator account (from the terminal)
Ever since I did this, my MBP wireless performance has been flawless.
Note, if you shutdown or restart your computer, the arp entry disappears. This is ok for me as I hardly ever power down my MBP. As insurance I have added an account startup item to remind me to do the arp table entry.
This workaround is great for me because I don't have a need to use multiple wireless networks. It might not be practical for people who roam around onto different networks.
Give it a go and see if it works for you.
Message was edited by: michael louey

OK, after some further experimenting, I changed the multicast rate on my airport express. It was set at 6Mbps, and I changed it to 2Mbps.
I have read that the default multicast rate for previous 802.11g versions of Airport basestations is actually 2mbps. Excellent results so far !! I have set up a terminal command to continuously ping my airport router address every 15 sec, and there have been virtually no dropped packets so far over many hours.
ping -i 15 10.0.1.1
Interestingly, in Apple's Airport Admin software in my MBP there is no option to set the rate at less than 6Mbps (!!!!), so I had to use the Windows XP version of Airport admin software to make this change using a windows machine. Using the XP software you can set the muticast rate as low as 1Mbps.
If you are using Apples airport admin software (Tiger and Leopard) and you commit any sort of change in settings, the multicast rate will be re-set at a minimum of 6Mbps. My understanding of the multicast rate is that setting it too high is similar to shrinking the coverage area of the basestation, and limiting access only to clients who can transmit at the required multicast rate.
So my new theory is that the dropouts are caused by the MBP dropping off the airport due to not being able to achieve the set multicast rate. (this could be due to factors such as low signal strength, excessive interference or noise).
If you are using Apples more recent Airport admin software, you are having a minimum 6mbps muticast rate set, and this might be too high for your particular environment.
Just a theory.
(oh yeah, I enabled interference robustness on the MBP and the basestation just for good measure)

After Software Update 2007-004 airport card stopped working after wakeup

Hi,
I have a powerbook G4 - DVI running 10.3.9. After I have installed Software Update 2007-003, when my computer goes to sleep and then wakes up, airport card stops working. I had to open the back of the computer, unplug and plug the airport card, then it starts working again. But next time the computer goes to sleep, it stops working again.
Does anyone have a similar problem? Any work arounds?
Thanks in advance.
Also following is the logs from Software Update. Looks suspicious:
Mac OS X Version 10.3.9 (Build 7W98)
2007-04-28 18:56:03 -0400
2007-04-28 18:56:03.190 loginwindow[181] FSResolveAliasWithMountFlags returned err = -43
WirelessScan timeout waiting for first scan result
WirelessScan timeout waiting for first scan result

Deleting AppleAirPort2.kext solved the problem for some...
http://discussions.apple.com/thread.jspa?threadID=934370&tstart=0
While others had to rollback the AppleAirPort.kext to version...
http://discussions.apple.com/thread.jspa?messageID=4310165&#4310165
Installing the Security update 1.0.1 from 5/01/2007 helped others. Reapplying the Combo Update again helped a couple of people.

Workaround for LineBreakMeasurer thread safety issues?

Basically, we have a servlet that returns a png in response to a GET request containing a String, and info on the font, size, size of area the text needs to fit in, and color to render it in. Periodically the webserver locks up as requests get stuck in the servlet!
After digging around, I found out that Graphics 2D ops are safe, as long as each thread has it's own instance. No problem there!
The problem is, we want to break the string, and make it fit inside the area given. And it turns out, LineBreakMeasurer eventually calls the method getEngine() on SunLayoutEngine, and threads lock up in there.
Here's the code from SUN:
SunLayoutEngine extract listed below
public final class SunLayoutEngine implements LayoutEngine, LayoutEngineFactory {
    private static native void initGVIDs();
    static {
     initGVIDs();
    private LayoutEngineKey key;
    private static LayoutEngineFactory instance;
    public static LayoutEngineFactory instance() {
        if (instance == null) {
            instance = new SunLayoutEngine();
        return instance;
    private SunLayoutEngine() {
        // actually a factory, key is null so layout cannot be called on it
    public LayoutEngine getEngine(Font2D font, int script, int lang) {
        return getEngine(new LayoutEngineKey(font, script, lang));
// !!! don't need this unless we have more than one sun layout engine...
    public LayoutEngine getEngine(LayoutEngineKey key) {
        HashMap cache = (HashMap)cacheref.get();
        if (cache == null) {
            cache = new HashMap();
            cacheref = new SoftReference(cache);
        *HERE IS WHERE WE LOCKUP VVV*
        LayoutEngine e = (LayoutEngine)cache.get(key);
        if (e == null) {
            e = new SunLayoutEngine(key.copy());
            cache.put(key, e);
        return e;
    private SoftReference cacheref = new SoftReference(null);
    private SunLayoutEngine(LayoutEngineKey key) {
        this.key = key;
    public void layout(FontStrikeDesc desc, float[] mat, int gmask,
                       int baseIndex, TextRecord tr, boolean rtl, Point2D.Float pt, GVData data) {
        Font2D font = key.font();
        FontStrike strike = font.getStrike(desc);
        nativeLayout(font, strike, mat, gmask, baseIndex, tr.text, tr.start, tr.limit, tr.min, tr.max, key.script(), key.lang(), rtl, pt, data);
    private static native void nativeLayout(Font2D font, FontStrike strike, float[] mat, int gmask, int baseIndex,
                                            char[] chars, int offset, int limit, int min, int max,
                                            int script, int lang, boolean rtl, Point2D.Float pt, GVData data);
}Even though each thread is using it's own LBM instance, they will often lock up inside SunLayoutEngine.
Note the factory method always returns the same instance, which will be shared by all threads!
I've filed a bug against sun. I am open to any workarounds you may have.
And for those of you using various java based report generators, and getting lockups, I think this may be related. :)
Edited by: djoyce on Oct 16, 2007 2:12 PM
Edited by: djoyce on Oct 16, 2007 2:15 PM

Okay, this class is it's own factory, and only one instance is ever created. GlyphLayout calls instance(), and getEngine on that, and then all the threads pile up in the weakref'd hashmap.
at java.util.HashMap.get(HashMap.java:348)
at sun.font.SunLayoutEngine.getEngine(SunLayoutEngine.java:113)
at sun.font.GlyphLayout$EngineRecord.init(GlyphLayout.java:565)
at sun.font.GlyphLayout.nextEngineRecord(GlyphLayout.java:439)
at sun.font.GlyphLayout.layout(GlyphLayout.java:371)
at sun.font.ExtendedTextSourceLabel.createGV(ExtendedTextSourceLabel.java:267)
at sun.font.ExtendedTextSourceLabel.getGV(ExtendedTextSourceLabel.java:252)
at sun.font.ExtendedTextSourceLabel.createCharinfo(ExtendedTextSourceLabel.java:522)
at sun.font.ExtendedTextSourceLabel.getCharinfo(ExtendedTextSourceLabel.java:451)
at sun.font.ExtendedTextSourceLabel.getLineBreakIndex(ExtendedTextSourceLabel.java:397)
at java.awt.font.TextMeasurer.calcLineBreak(TextMeasurer.java:313)
at java.awt.font.TextMeasurer.getLineBreakIndex(TextMeasurer.java:548)
at java.awt.font.LineBreakMeasurer.nextOffset(LineBreakMeasurer.java:340)
at java.awt.font.LineBreakMeasurer.nextLayout(LineBreakMeasurer.java:422)
at java.awt.font.LineBreakMeasurer.nextLayout(LineBreakMeasurer.java:395)

Is there a workaround for the thumbnail regeneration issue in CS5?

Hullo.
A friend uses my old version of CS5 and she is stuck with ACR 6.7, because this is the last version available in CS5.
She seems to have huge problems in Bridge with the thumbnail regeneration bug described here, for instance: Cropping to an edge confuses Adobe Bridge?
Concretely, although she has a relatively powerful machine, she is unable to work because there are always tens and tens of thumbnails being generated and her eight virtual cores completely fill the disk bandwidth, making Bridge impossible to use. I am not 100% sure that it is exactly this bug, but everything seems to correspond perfectly well: hundreds of DNG files with lens correction activated and very many cropped manually.
Now, this is a confirmed bug of ACR 6.7 until ACR 8.2. She cannot switch to the latter without purchasing a newer version of Photoshop/Bridge.
Does Adobe provide any fix for this bug in CS5? Could someone kindly point me to it? Her version of Bridge is simply unusable as is....
If the answer above is no, I would be interested to know if this seems legal (not to say ethical...) to anybody: she is (otherwise) pretty happy with CS5 and she would need to buy a new licence for the sole and exclusive reason that the product Adobe sold me has a known and proven bug which makes it virtually useless in her setting.
Thanks,
p.

There are two similar bugs:
The LPC+crop bug started with ACR 6.1 and was fixed in 8.2.
The LPC mystery bug started with ACR 7.3 and was fixed in 8.6.
Both bugs cause repeated thumbnail extractions in Bridge on some images with Lens Profile Corrections enabled.
As you are on ACR 6.7 it can only be the first bug. The only workaround I know is to ensure that the crop does not touch the edge of the corrected image. A few pixels gap will do it. Also, it helps to keep less images in a folder--but this can't be avoided when using Collections or Finds.
I'd imagine that Adobe won't fix CS5 just for this. Presumably there's something in the smallprint which admonishes them from responsibility after the shelf life of the product ends. To be fair, it's not like they fixed it straight away in CS6, unlike the Bridge CS5 database bug (thanks, Adobe). They were only able to reproduce the fault in summer 2013.

Is there a workaround for Facetime Apr 16th issue than upgrading to latest IOs ??

Hi,
I have IPad2 and I am facing the Facetime issue due to certificate expiry on Apr 16 as reported by Apple.
I dont want to upgrade to latest IOS because I think it would slow down the performance and ruin a good working IPad just to resolve this issue.
Is Apple going to provide some other alternative and/or fix the issue rather than forcing people to upgrade?

Folks choices are to either update or move to a different app such as skype or some other video chat program.

AirPort Extreme Update 2007-004 did not solve my reliability problems.

The latest update from Apple did not fix the problem on my system, and now I don´t know what I should do, is there anything I can do to somehow fix it?
I can´t use the computer like this, it´s very annoying, for example I can´t browse the web with Safari(constant "Failed to open page" or "You´re not connected to the internet" messages), ethernet is not an option, besides, what´s the point of a laptop if I cannot connect to the network wirelessly?
This is my first MacBook by the way, I like its look & feel, easy of use and integration, but this AirPort issue completely took away the "just works" image I had of Apple´s products.
Don´t get me wrong though, I knew the Mac was not going to be perfect, and that there would be problems(as usual), but I would never have expected something like this.
I´d really like to get this thing to work, the Mac pretty much offers the kind of integration that I´ve always wanted in Linux.
Anyway.. am I the only one whose system is still having problems with AirPort?
What can I do to fix this?
Should I just wait until Apple releases another bug fix for this? how long would this take?
Should I return this MacBook to an Apple store?
I bought this in the U.S. and there is no store on my country(Uruguay), there´re however some Apple Authorized Service Providers, should I take it to them? would they give me a brand new Mac or repair this one for free if I´m covered by the warranty?
I read(http://www.apple.com/support/contact/) that since I´m still within the 90 days of ownership I can call Apple Technical support, but since they don´t have a number for my country, is there an alternative way of contacting them?(via email?).
I don´t know.. what do you people think I shoud do?
+Please don´t recommend me to install an older version, I really don´t want to, besides how do I know it will fix the issue?+
About the problem:
Symptoms:
AirPort signal level randomly decreases until connection is lost, and there is no automatic reconnection.
Manual reconnection is required and might not always succeed, and even if it does, it doesn´t last long(usually less than 3 minutes).
Sometimes the network is missing from the menu(when clicking the wifi icon on status bar) and turning off and on AirPort is required.
Judging from what I´ve read here and found on google, this is a known common problem that dates back to at least april 2007(see [1]).
*Some (useful?) Information:*
0) It might have worked better before updating (10.4.9 is the version of my Installation discs, I didn´t reinstall) to 10.4.10, but I can´t say for sure.
1) According to [1] this seems to be a software problem in OS X, since the atheros driver works fine under Windows.
2) It doesn´t matter if the laptop is running from battery or not, and it doesn´t seem to be related to waking from sleep state since it happens on a clean restart too.
3) Once in a while, the OS asks me to enter the WPA passphrase again to connect to the network, why does it do this if the passphrase is already stored inside the default login keychain?. (entering the passphrase again does not fix the problem)
4) Wireless router is a speedtouch modem, it´s properly configured and it´s known to work, its leds indicate that everything is ok.
5) The MacBook is approx. 6m away from the speedtouch router(walls in between), electronic devices: headless computer next to the speedtouch modem, printer, radio, tv (note: not that it matters since the laptop has worked from this location before).
6) System Info: (forums display issues, does not show ok)
Hardware:
+Mac OS X 10.4.10+
+Model Identifier: MacBook2,1+
+Processor Name: Intel Core 2 Duo+
+Processor Speed: 2 GHz+
+Number Of Processors: 1+
+Total Number Of Cores: 2+
+L2 Cache (per processor): 4 MB+
+Memory: 1 GB+
+Bus Speed: 667 MHz+
+Boot ROM Version: MB21.00A5.B06+
+SMC Version: 1.17f0+
+Serial Number: W87190VFYA2+
+Sudden Motion Sensor:+
+State: Enabled+
Network:
AirPort:
+Type: AirPort+
+Hardware: AirPort+
+BSD Device Name: en1+
+IPv4 Addresses: 192.168.1.68+
IPv4:
+Addresses: 192.168.1.68+
+Configuration Method: DHCP+
+Interface Name: en1+
+Router: 192.168.1.254+
+Subnet Masks: 255.255.255.0+
DNS:
+Domain Name: lan+
+Server Addresses: 192.168.1.254+
+DHCP Server Responses:+
+Domain Name: lan+
+Domain Name Servers: 192.168.1.254+
+Lease Duration (seconds): 0+
+DHCP Message Type: 0x05+
+Routers: 192.168.1.254+
+Server Identifier: 192.168.1.254+
+Subnet Mask: 255.255.255.0+
Proxies:
+Proxy Configuration Method: Manual+
+ExcludeSimpleHostnames: 0+
+FTP Passive Mode: Yes+
+Auto Discovery Enabled: No+
Ethernet:
+MAC Address: 00:1b:63:08:c0:87+
+Media Options: +
+Media Subtype: autoselect+
+AirPort Card Information:+
+Wireless Card Type: AirPort Extreme (0x168C, 0x87)+
+Wireless Card Locale: USA+
+Wireless Card Firmware Version: 1.1.9.3+
+Current Wireless Network: SpeedTouch824916+
+Wireless Channel: 1+
7) logs (not good debug info, but maybe it helps...)
Before last update (from /var/log/system.log)
+Aug 1 01:36:21 Federico-Zagarzaz-s-Computer mDNSResponder: Repeated transitions for interface lo0 (127.0.0.1);+
+delaying packets by 5 seconds+
+Aug 1 01:39:14 Federico-Zagarzaz-s-Computer ntpd[158]: sendto(17.254.0.26): Can't assign requested address+
+Aug 1 01:39:31 Federico-Zagarzaz-s-Computer /System/Library/PrivateFrameworks/Apple80211.framework/Resources/ai+
+rport: Error: WirelessAssociate2() = 88001006 for network SpeedTouch824916. The operation timed out.+
+Aug 1 01:39:39 Federico-Zagarzaz-s-Computer /System/Library/PrivateFrameworks/Apple80211.framework/Resources/ai+
+rport: Error: WirelessAssociate2() = 88001006 for network SpeedTouch824916. The operation timed out.+
+Aug 1 01:39:39 Federico-Zagarzaz-s-Computer /System/Library/PrivateFrameworks/Apple80211.framework/Resources/ai+
+rport: Error: WirelessAssociate2() = 88001003 for network SpeedTouch824916. errWirelessKernelError.+
+Aug 1 01:39:39 Federico-Zagarzaz-s-Computer /System/Library/PrivateFrameworks/Apple80211.framework/Resources/ai+
+rport: Error: WirelessCreateScanResults() = 8800100b+
+Aug 1 01:39:50 Federico-Zagarzaz-s-Computer configd[35]: Error: Failed to join most recent network "SpeedTouch8+
+24916", err=88001006 (will search for any others)+
+Aug 1 01:39:50 Federico-Zagarzaz-s-Computer /System/Library/PrivateFrameworks/Apple80211.framework/Resources/ai+
+rport: Currently connected to network SpeedTouch824916+
After last update:
+Aug 1 07:01:37 Federico-Zagarzaz-s-Computer configd[60]: Error: Failed to join most recent network "SpeedTouch824916", err=88001006 (will search for any others)+
+Aug 1 07:01:48 Federico-Zagarzaz-s-Computer /System/Library/PrivateFrameworks/Apple80211.framework/Resources/airport: Could not find "SpeedTouch824916" on any channel (directed scan)+
+Aug 1 07:01:48 Federico-Zagarzaz-s-Computer /System/Library/PrivateFrameworks/Apple80211.framework/Resources/airport: Could not find "SpeedTouch824916" on channel(s) 1+
+Aug 1 07:02:20 Federico-Zagarzaz-s-Computer /System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Resources/air port: Error: WirelessAssociate2() = 88001006 for network SpeedTouch824916. The operation timed out.+
+Aug 1 07:02:29 Federico-Zagarzaz-s-Computer /System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Resources/air port: Error: WirelessAssociate2() = 88001006 for network SpeedTouch824916. The operation timed out.+
+Aug 1 07:02:38 Federico-Zagarzaz-s-Computer /System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Resources/air port: Error: WirelessAssociate2() = 88001006 for network SpeedTouch824916. The operation timed out.+
8) Settings: (forums display issues, does not show ok)
+unknown-00-1b-63-08-c0-87:~ fede$ cat /Library/Preferences/SystemConfiguration/com.apple.airport.preferences.plist+
+<?xml version="1.0" encoding="UTF-8"?>+
+<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">+
.+<plist version="1.0">+
.<dict>
. <key>AllowEnable</key>
. <integer>1</integer>
. +<key>Always remember new networks</key>+
. <integer>1</integer>
. +<key>Default 802.1X Configurations</key>+
. <array>
. <dict>
. <key>AcceptEAPTypes</key>
. <array>
. <integer>25</integer>
. <integer>21</integer>
. <integer>43</integer>
. </array>
. <key>Description</key>
. <string>Automatic</string>
. <key>EAPFASTProvisionPAC</key>
. <integer>1</integer>
. <key>EAPFASTUsePAC</key>
. <integer>1</integer>
. <key>TLSVerifyServerCertificate</key>
. <integer>1</integer>
. <key>TTLSInnerAuthentication</key>
. <string>MSCHAPv2</string>
. </dict>
. <dict>
. <key>AcceptEAPTypes</key>
. <array>
. <integer>21</integer>
. </array>
. <key>Description</key>
. +<string>TTLS - PAP</string>+
. <key>TLSVerifyServerCertificate</key>
. <integer>1</integer>
. <key>TTLSInnerAuthentication</key>
. <string>PAP</string>
. </dict>
. </array>
. +<key>Disconnect on logout</key>+
. <integer>0</integer>
. +<key>Fallback Preference</key>+
. <integer>0</integer>
. <key>InterferenceRobustness</key>
. <integer>0</integer>
. <key>JoinMode</key>
. <integer>0</integer>
. +<key>List of known networks</key>+
. <array>
. <dict>
. <key>AuthPasswordEncryption</key>
. <string>SystemKeychain</string>
. <key>SCAN_CHANNELS</key>
. <array>
. <integer>1</integer>
. </array>
. <key>SSID</key>
. <data>
. U3BlZWRUb3VjaDgyNDkxNg==
. </data>
. <key>SecurityType</key>
. +<string>WPA Personal</string>+
. <key>WEPKeyLen</key>
. <integer>32</integer>
. <key>_timeStamp</key>
. <date>2007-07-02T07:49:11Z</date>
. <key>authMode</key>
. <integer>2</integer>
. <key>capability</key>
. <integer>16</integer>
. <key>channel</key>
. <integer>1</integer>
. <key>cipherMode</key>
. <integer>2</integer>
. <key>isIBSS</key>
. <integer>0</integer>
. <key>isWPA</key>
. <integer>1</integer>
. <key>multiCipher</key>
. <integer>3</integer>
. <key>name</key>
. <string>SpeedTouch824916</string>
. <key>scanWasDirected</key>
. <true/>
. </dict>
. </array>
. +<key>Require Admin for IBSS creation</key>+
. <integer>0</integer>
. +<key>Require Admin for network change</key>+
. <integer>0</integer>
. <key>Version</key>
. <integer>5</integer>
.</dict>
.</plist>
9)
.+unknown-00-1b-63-08-c0-87:~ fede$ /System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Resources/air port -I+
. +commQuality: 0+
. +rawQuality: 10+
. +avgSignalLevel: -89+
. +avgNoiseLevel: -96+
. +linkStatus: ESS+
. +portType: Client+
. +lastTxRate: 2+
. +maxRate: 54+
.+lastAssocStatus: 1+
. +BSSID: 00:14:7f:30:56:75+
. +SSID: SpeedTouch824916+
. +Security: WPA PSK cipher: TKIP+
10) Software Update.log
+2007-07-02 01:17:51 -0300: Installed "Pages Update" (2.0.2)+
+2007-07-02 01:17:54 -0300: Installed "Keynote Update" (3.0.2)+
+2007-07-02 01:18:04 -0300: Installed "iPhoto Update" (6.0.6)+
+2007-07-02 01:18:24 -0300: Installed "QuickTime" (7.1.6)+
+2007-07-02 09:57:07 -0300: Installed "iTunes" (7.3)+
+2007-07-02 09:57:09 -0300: Installed "Security Update 2007-006 (Universal)" (1.0)+
+2007-07-02 09:59:26 -0300: Installed "Mac OS X Update (Intel)" (10.4.10)+
+2007-07-26 21:56:29 -0300: Installed "QuickTime" (7.2)+
+2007-07-26 22:21:30 -0300: Installed "iTunes" (7.3.1)+
+2007-07-26 22:21:34 -0300: Installed "Audio Update 2007-001" (1.0)+
+2007-08-01 02:53:00 -0300: Installed "AirPort Extreme Update 2007-004" (1.0)+
Don´t know if it helps or not, but that is all I could find.
Thank you for taking the time to read this.
Best Regards,
Federico
References:
[1] http://www.macfixitforums.com/showflat.php?Cat=&Board=wireless&Number=823491&For um=&Words=&Match=Entire%20Phrase&Searchpage=0&Limit=25&Old=1day&Main=810572&Sear ch=true
[2] http://www.appletell.com/apple/comment/unconfirmed-airport-issues-with-mac-os-x- 10410/
[3] http://discussions.apple.com/thread.jspa?threadID=1008143&tstart=0
[4] http://www.macfixitforums.com/showflat.php?Cat=&Board=wireless&Number=823491&For um=&Words=&Match=Entire%20Phrase&Searchpage=0&Limit=25&Old=1day&Main=810572&Sear ch=true
Message was edited by: fzagarzazu (forums display issues)

Hi,
Well I don´t know what to think now.. I installed the last security update, restarted, went to sleep and now it seems to be working much better, at least there doesn´t seem to be so many drop outs.
I find it a little strange that the airport icon on the status bar that shows signal strength keeps changing, but maybe this is normal behaviour?, don´t know..
I can´t say that the problem is fixed either since I didn´t start to experience airport issues immediately after I updated to 10.4.10, so who knows?
Maybe it works for two days in a row and then it suddenly starts malfunctioning for no apparent reason.
It could be very well be a combination of little problems here and there(some even caused by me editing system preferences) that add up and manifest as a bigger problem, I´ve no idea how to trace it, and as long as it works, I don´t care..
I doubt this will help anyone, but anyway.. the last thing I remember doing before restarting was executing:
# System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Resources/airp ort --updateprefs
which examines network preferences and repairs them if necessary.
Then I went into System Preferences > Network, AirPort´s options and restored default settings, after that I configured it to require administrator password to "Create Computer-to-Computer networks".
I´m hoping that the whole airport issue not working after the last airport update was a weird glitch or even better, caused by me.
If it starts malfunctioning again, I´ll simply call AppleCare and let them deal with it, by the way, it kind of ***** that the only way of contacting them is via phone and no phone number is listed for my country.. no email address? ...
Best Regards,
Federico

Airport icon grey after installing software update Security Update 2007-004

Yesterday I installed Security Update 2007-004 (10.3.9 Client)(April 19, 2007) and since then when I wake-up my iBook (which was functioning fine prior to closing it and puting it to sleep) the airport icon is greyed out. The only way to get the airport icon to be black (functioning)is to restart the iBook.
Has anyone else had this issue or does anyone have any ideas. I an running 10.3.9 on a 2 USB port G3 iBook with a snow airport.
Thanks.

Have you tried the simple solution posted by quovadis?
http://discussions.apple.com/thread.jspa?threadID=934593
I hope it works for you.

Airport Problems after Security Update 2007-004

Ever since I've installed Security Update 2007-004 my Airport connection has been dropping about every 15 to 30 minutes. Sometimes Airport will stay connected but will stop working until I renew my DHCP lease (I get the same IP though). When it drops I click on the Airport icon to reconnect but my network doesn't always show up. Sometimes I have to turn Airport off and back on again to make it show up, and a few times I've had to reset my computer to make it show up.
I have a MacBook Pro with an 802.11n card. I'm using two different routers; one at work, and one at home. The work router is a Linksys N router while the one at home is a Linksys G router.
I've tried all the tricks. Repairing Permissions, deleting the extension caches, installing the standalone updater, but nothing is working.

Deleting AppleAirPort2.kext solved the problem for some...
http://discussions.apple.com/thread.jspa?threadID=934370&tstart=0
While others had to rollback the AppleAirPort.kext to version...
http://discussions.apple.com/thread.jspa?messageID=4310165&#4310165
Installing the Security update 1.0.1 from 5/01/2007 helped others. Reapplying the Combo Update again helped a couple of people.

No joy from AirPort Extreme Update 2007-004

Anyone else in the same boat?
My specs:
MBPro, 17" Core 2 2.33 GHz.
Worked fabulously prior to 10.4.10 update.
No kernel panics or crashes after 10.4.10 update.
After 10.4.10 update, wireless flakes nearly continuously whether on battery or AC.
Tried many hacks, the only one that worked was IAmNobody's.
Had trouble installing AirPort Extreme 2007-004 update, even though I restored the kernel files. (Perhaps I goofed -- I tried many things before I got a working system)
I figured I'd just bite the bullet and do a clean, from scratch re-install.
Unfortunately, I'm now back to exactly the same problem I was having before. Anyone else in the same boat?
I guess tomorrow I'm back off to re-apply the old 10.4.9 drivers...
Major, major suckage here, Apple.
-p.

The update has not fixed my problems either. (Macbook Core duo can basically no longer connect to any wireless network after 10.4.10).
As an avid Apple lover, investor, converter of countless pc users, and purchaser of basically every computer and Apple product made since the mid 80's, I have to say that Apple's handling of this long standing problem is just repugnant.
To those Apple reps who may be reading this, please get your **** together on this and fix it once and for all (or at least make **** sure it is fixed in Leopard). The Macbook is perhaps your most important core product at this point.

Complicated possible workaround for Keynote to Quick Time issues etc.??

I've been experiencing many of the issues already presented here. This is obviously a major issue that Apple may already be trying to fix for an update, but they never tell anyone what they are doing. My project contains .mov files with audio and they just don't behave, the audio is off and movie files either play with disjoionted audio, or, freeze on the first frame. Also, half the transitions don't export to quick time, idvd or any other format I've tried.
For those with 2 computers and a little extra hardware, I've got a possible workaround that "may" at least get the project rolling again. I hooked my MacBook Pro into my Eye TV 250 and switching to AV input, simply played the presentation I'd recorded with all my timings and transitions through the Eye TV box into my desktop computer. I then exported the live recording through the Eye TV software to a .mov file and all the transistions and audio seemed to be the way I set them up. I then brought this movie into Garage Band and added a backing track.
Eye250 is not ideal for commercial projects because I seem to have some quality loss, BUT, I was importing to a G4 mac Mini so maybe that's an issue as well. If anyone else has an external digital video input device and two Intel machines, could they please try this out and see if the quality is HD.
If this works, it would at least be a workaround for guys with commercial projects on deadline until Apple fixes their software. Appreciate any input!!!!

Sadly, IP printing is not a feasible solution for me. When I configure it as you've described, the print job goes to the queue and stalls with this message--
Network host '192.168.0.187' is busy; will retry in 10 seconds...
This print-once-then-never-again issue is very frustrating. Airport express has been an unreliable print server from the get-go. The firmware hasn't been updated in two years and Apple has never published a list of supported USB printers. It's one of those things they want reps in the apple store to be able to verbally tell people that the product will do, but in writing, "good luck with that."
I'm getting on Amazon right now to find a real print server. AE is a burner of time.
Seth

Airport Extreme- anybody have a workaround for the lack of Wake on LAN ?

I've read in a number of places that the Airport Extreme (and other Apple routers) don't allow for the standard Wake on LAN packet to wake a sleeping Mac.
Does anybody know of a workaround for the Airport Extreme that might allow for waking a sleeping Mac on the LAN remotely ?
Thanks,
Ed

Does anybody know of a workaround for the Airport Extreme that might allow for waking a sleeping Mac on the LAN remotely ?
There isn't any easy solution, but one possible method was posted here.
(41986)

Temporary workaround for 2007-004 Airport issue (Anecdotal)

Similar Messages

Maybe you are looking for