New Airport Extreme Crashes Wireless Tiger Clients

I've spent most of Christmas Day trying to figure a way out of this mess. I even downgraded my old Powerbook G4 to Panther, only to discover that it--initially--had no support for WPA security (doing the normal upgrades to it now via Ethernet). Not sure why it seems that every time I buy a new piece of Apple gear, it doesn't cooperate very well with older Apple gear. I understand that time moves on (and Apple wants us to as well), but one expects things like basic wireless in a working Mac to continue working with newer Apple wireless routers. But no.

I initially thought the problem might be my new WDS setup, but that's not the case. The kernel panics persisted, whether I disengaged WDS or not.

The Airport Extreme Base Station in its current firmware incarnation (7.5) causes kernel panics on ALL wireless clients running Tiger 10.4.11. This is confirmed by multiple users on the Apple Support Boards:

My Apple Tech confirmed (early November) that there is a known problem with the new Airport Extreme Dual Band Base Station causing kernel panics on computers running Tiger (only when connecting wirelessly via an Airport card -- not when connected via Ethernet cable). Apple Engineering has been notified and has not -- as yet -- released a software update to Tiger. Based on some customers' reports, we tried disabling the Guest Network on the base station, but that didn't work for me. Has anyone figured out a work-around besides 1) the ethernet cable and 2) upgrading to Leopard?

[From Apple - Support - Discussions - Kernel Panic when Running Tiger ...]

One user managed to get Apple to send him a Leopard install to address the issue:

Here's my experience. Ran two iMacs with Tiger 10.4.11 and a new iMac Intel Core Duo with an Airport 801.g Extreme. Alls well. I upgraded to an Airport 801.n and all **** broke loose with Unresolved Kernel Traps (UKT) on both Tiger machines. I managed to obtain Leopard from Apple and will upgrade each Tiger machine a couple of days apart to be sure I don't have any more UKTs. Then I will reinstall the Airport 801.n and see what happens. If I can believe what Apple Support has told me my problems should be solved. I should know by end of this coming weekend.

[From Apple - Support - Discussions - Kernel Panic when Running Tiger ...]

So I put in a service call to Apple and spoke with a rep today; the rep didn't offer a Leopard install like they did for the other user, and they didn't even admit that there was a known problem:

No dice. Just got off the phone with Apple and their solution for me was to go into the Apple Store. He said it was a computer issue...not the AEBS. I even brought up this thread (i.e., Tiger incompatible with new AEBS) and that other users said that Apple had acknowledged this problem. He said he had not heard that and that it was my computer?

Keep in mind that I told him that both my G4 machines are running Tiger (Powerbook and Mac Mini) and both are kernel panicking with the new AEBS.

So, I obviously didn't get the good support that you received...

[From Apple - Support - Discussions - Kernel Panic when Running Tiger ...]

I've basically tried everything (including doing Leopard installs using Target Disk mode), and nothing is really working (the G4 versus Intel architecture creates problems--i.e., the GUID versus APM). I either must get a Leopard Retail disc from Apple or wait for them to officially acknowledge the problem and issue a firmware update. Arggggghhh! My Powerbook is now running 10.3.9 (Panther) after the updates and is doing fine on the new AEBS, so this PROVES it's Tiger that is not compatible with the new Airport Extreme Base Station (802.11n). The Mac Mini is dead in the water at the moment in terms of wireless connectivity (I have the Airport turned off...and no more panics). I have ordered some cheap Cat-5 cable, which should be here soon and keep the Mini running until the firmware update shows up. Apple, your users really shouldn't have to go through such nonsense.

FOLLOW-UP on 26 DEC 2009:

As a follow-up, my issues were solved by installing Leopard on my G4 machines, which was not easy. See my post below on the Apple Discussions thread:

I can confirm now--as have others here--that it is definitely the Airport Extreme Base Station (802.11n) that is causing the kernel panic problem with Tiger. It will also not cooperate with Panther 10.3.9, IF you install the AirPort Extreme Driver Update 2005-001 update:

http://support.apple.com/kb/DL426

I downgraded my Powerbook G4 Aluminum 15" to Panther and had it working well at 10.3.9 until I installed the above driver update, so this driver (or some code within it) is the culprit; obviously, it hung around in Tiger but changed in Leopard and Snow Leopard (hint, hint, Apple).

I have now managed to update my old G4s (through much effort) to Leopard and both are cooperating nicely now with the Airport Extreme Base Station. I suspect Apple will update the driver eventually, but if you're having issues...go back to Panther (w/o the aforementioned driver update) or upgrade to Leopard if your system will install/run it.

FWIW, I installed Leopard on my old G4 Mac Mini (with 512 MB RAM) using Target Disc mode from the Powerbook running the install DVD. Leopard would not install any other way on that machine. Good luck all!

[From Apple - Support - Discussions - Re: Kernel Panic when Running Tiger ...]

Extend New Airport Extreme With Old Airport Express

So maybe you're like me and bought a new Airport Extreme Base Station (802.11n) and want to extend your wireless network through an older Airport Express (802.11 b/g). After Googling this, I discovered I wasn't the only frustrated user. Apple wants you to buy a newer Airport Express with 802.11n to make extending your network easier. However, you can still use the older Airport Express with a little work and a hidden trick.

For some reason, this took me SEVERAL hours to figure out. It didn't JUST WORK. LOL! Fortunately, I learned that using the Option key while selecting the Wireless Mode popup menu in the Airport Utility (Version 5.5 (550.29)) returns to the user the ability to set up a WDS (wireless distribution system).

A nice user named Bob on the Apple Discussion forums confirmed the Option trick I had learned elsewhere. However, I still had trouble getting the WDS to work properly. Here's what I tried that seems to do the trick:

Thanks Bob. Yes, I found that trick elsewhere. Still had trouble, even though I went through all the proper motions (i.e., making the AEBS(n) the WDS base station and the APX the WDS remote...including entering the correct MAC addresses for each).

However, I think I've discovered the fix that allowed my old APX [Airport Express] to work with the new AEBS [Airport Extreme Base Station] in a WDS network: I set the radio mode on the APX to 802.11g ONLY! The radio mode on the base station was kept at AUTOMATIC. And I used Channel 1 for the 2.4 GHz frequency on both and left the 5 GHz frequency channel selection at AUTOMATIC on the base station. WDS wasn't working until I made those changes (don't know if one or more of those steps is important...but it's working now).

[From Apple - Support - Discussions - WDS set up problem ...]

Airport Extreme Freezes and Connection Slowness

Not even a year ago, we replaced our old Netgear Ethernet Router and old Airport Express with a nice, shiny, new Apple Airport Extreme. Lot's o' promise. The main problem (apart from other minor hiccups you'll find on here) has been that we typically have had to soft reset the unit daily, because the connection would become completely unresponsive--including Ethernet and wireless connections. So, it was either the cable modem (which worked fine with our old router) or the Airport Extreme, which judging from a Google search is giving more users than just me fits. So, I've played with all sorts of settings, including turning off IPv6 in the unit and on all the computers in the house; that didn't seem to fix anything.

However, I may have just made some changes that greatly improved my download speed while also eliminating the need to reset the AEBS each day! We'll see if my "fix" holds up. But the speed improvement is a plus.

First, I changed from "Automatic" to 100 Mbps/Full Duplex in the Airport Utility and restarted the AEBS:

Next, I changed similar settings in System Preferences->Network ("Automatic" to "Manually"):

Speeds via speedtest.net showed a dramatic improvement for download:

Then, I finally found the culprit: The automatic MTU!!
I couldn't believe it. Such a stupid, basic cause of such a big problem. This is most certainly a BUG.

To fix the MTU:

1. Apple Menu > System Preferences... then Network.

2. On the left, choose Ethernet , then Advanced... on the bottom.

3. Choose Ethernet tab:
. . . Configure: Change from Automatically to MANUALLY.
. . . MTU: Change from Standard to CUSTOM. Put 1452 then click OK. Then Apply at the bottom.

[From Apple - Support - Discussions - A fix for random, slow, intermittent ...]

Use Only One Partition for AirPort Extreme (802.11n) Disks

Turns out that using more than one volume per disk connected to an Airport Extreme isn't a good idea. May explain some of my issues.

The AirPort Extreme (802.11n) and Time Capsule work with most disks that are not software RAID volumes (no more than one volume per physical disk).

[From AirPort Extreme (802.11n) and Time Capsule: USB storage device supported formats and protocols]

mDNSResponder Constantly Doing "Something"

I noticed my mDNSResponder connecting constantly to opendns (didn't always happen but when it did it was constant). Found the links below. It basically requires a bit of under-the-hood tweaking.

1. Make a back up copy of the mDNSResponder.plist file as a precaution.
2. Open the mDNSResponder.plist file in Terminal using your preferred text editor. Here is a sample command:
   

   sudo nano "/System/Library/LaunchDaemons/com.apple.mDNSResponder.plist" 
   

3. Add "<string>-NoMulticastAdvertisements</string>" to the array in the "ProgramArguments" section.
   
   In other words:
   

     <key>ProgramArguments</key>
           <array>
               <string>/usr/sbin/mDNSResponder</string>
               <string>-launchd</string>
           </array>    
   

   becomes...
   

           <key>ProgramArguments</key>
           <array>
               <string>/usr/sbin/mDNSResponder</string>
               <string>-launchd</string>
          <string>-NoMulticastAdvertisements</string>
     </array>
   

4. Save the file.
   
   Important: If you edited the file using emacs, you must remove the emacs backup file (the file with a tilde at the end of the name, "/System/Library/LaunchDaemons/com.apple.mDNSResponder.plist~") or your Mac will not start up.
   
5. Restart your Mac.

****

UPDATE 12 June 2010: The problem, as it turns out, was listing my OpenDNS servers in both my Airport Extreme (for the entire home network) and my Mac Pro. As soon as I deleted the OpenDNS servers from Network Preferences on my Mac Pro, everything returned to normal...no more constant outgoing connections. The above method worked too, but it was at the cost of losing Bonjour connectivity on my home network (not acceptable).

[From Snow Leopard disabling mDNSResponder/Bonjour drops internet - Mac Forums]

Mac OS X v10.6 uses the mDNSResponder process for unicast DNS (Domain Name System) functions, as well as Bonjour functions. Disabling the mDNSResponder process will also disable unicast DNS resolution, and without unicast DNS resolution, Mac OS X v10.6 cannot resolve hostnames such as www.apple.com.

In some network environments, administrators may prefer that Mac OS X v10.6 not transmit Bonjour service advertisements. You can use this advanced article if you are a network administrator who needs to disable Bonjour advertising service without disabling Bonjour queries and DNS.

[From Mac OS X v10.6: Disabling mDNSResponder will disable DNS]

Orwellian Apple Censorship

Here's my comment on the story about Apple censoring its Discussion Boards over Consumer Reports refusal to recommend the new iPhone 4 based on reception issues. Part of the reason for this blog is document my own troubleshooting efforts and problems I've had with Apple hardware and software.

Apple discussion boards have done this for years. They have devoted stormtroopers on there who will edit or delete your posts in a flat second, if they deem the posts unflattering to their products.

What’s unfortunate is that I’ve had several negative things to write in those forums, usually about hardware. My Powerbook’s lower memory slot went out and I never got it fixed because mine wasn’t in the “range of serials” that Apple deemed to be the problem; no one told my Powerbook that. My current Airport Extreme has to be reset usually once each day…again, Apple’s response to me is to make an appointment and bring it in to the Genius Bar (not sure how they are going to replicate my issue there, since it’s random). If you Google it, however, you’ll see that it’s a common problem, and people get inconsistent help (some get products replaced straightaway while others don’t).

Same sort of censoring happened when Apple decided to remove pdf manuals and hardcopy manuals from Logic Studio and replace them with the cumbersome Apple Help system. Apple finally relented and quietly brought back the pdf files after all the complaints. But they never acknowledged the complaints.

I think Apple would do well to have a revamped hardware testing division: A group of folks to test a product for six months thoroughly, before Apple releases it. They’ve always relied on users and developers to QC their software just before and right after release, but it’s a mistake to use that model on hardware. There are certain things in hardware that simply can’t be fixed after the genie is out of the bottle. I’m afraid what happens is that users end up being guinea pigs for the hardware a lot of the time; Apple simply (quietly) fixes the issues discovered in the next iteration, but the original buyers are left out in the cold.

[From Apple Censoring Discussion Forums Ref. Consumer Reports | Cult of Mac]

Slow iPhone YouTube Over WiFi Workaround

I discovered this problem on my iPhone too and it's annoying. Fix it Apple! Changing my Airport Express settings each time isn't an option.

Currently, the wireless network is set to G-Only since this was the best setup for our office. It was only when I switched the Wireless Network Mode to B-Only that YouTube videos began watchable again. None of the other settings had any effect.

[From YouTube Slow on iPhone through Wi-Fi - RESOLVED » Media and Internet Marketing Blog]

iTunes 6.0.2. goes clandestinely adware with MiniStore

Okay, there’s a lot of hoopla out there about iTunes 6.0.2 software having the new “MiniStore feature,” which, if open, will send info to Apple about what songs you click or listen to in your library and then present songs in the MiniStore pane similar to those songs clicked or listened to in your library.

First of all, you can disable this feature easily by clicking the button below the Mini-Store pane or select Edit > Show MiniStore (↑-⌘-M) to turn it off. No data are sent out once it’s disabled. Remind others who use your computer and have their own accounts to also disable this feature, because it will open for them as well; I’m sure Apple is counting on someone in the household not knowing how to turn the crap off.

The problem with this mess is that Apple doesn’t explicitly state anywhere they’re going to monitor your habits; they’re not forthcoming with information on turning it off; and they have it set to activate automatically when you first open iTunes after upgrading, which means until you figure out what the hell is happening you’re being watched. Regardless of whether you’re staunchly defending Apple (like many of the zealots over at the Apple Discussion boards), Apple has been less than honest by sneaking in this “new feature.”

I’m really not too concerned if Apple knows what I’m listening to (as I’m a faithful customer who has bought many tunes on iTMS--and I own 3 Macs, an Airport Express, and an iPod), but they’re also sending data to some 3rd party company called Omniture, Inc. Apple unofficially has claimed to dispose of data instantly (info used to target the advertisements to you in iTunes), but what does Omniture have to do with it? Why are they also getting the data? Are they also instantly disposing of the data? Something in me says NO!

Others on the net have found that your Apple ID is also sent with this data if you’re logged in, and though Apple may not store any data sent, there are some cookies and other info stored on YOUR computer. So in this regard, it is arguably spyware and at the very least adware. So users be-WARE!

Other reads on the subject:

http://since1968.com/article/154/itunes-update-update

http://www.boingboing.net/2006/01/11/itunes_update_spies_.html

http://www.plasticbag.org/archives/2006/01/cynicism_and_stupidity

http://www.rc3.org/2006/01/spytunes.php

My Gear

It’s nice to talk about what comprises your Apple setup. Here’s what I have:

Hardware Overview (G4 AGP):

Machine Model: Power Mac G4 (AGP graphics) CPU Type: PowerPC G4 (3.3) Number Of CPUs: 2 CPU Speed: 1.2 GHz L2 Cache (per CPU): 256 KB L3 Cache (per CPU): 2 MB Memory: 1.19 GB Bus Speed: 100 MHz Boot ROM Version: 4.2.8f1

Capacity: 9.57 GB Model: QUANTUM FIREBALLP LM10.2

Capacity: 114.5 GB Model: Maxtor 6Y120P0

Capacity: 233.76 GB Manufacturer: ATA Model: Maxtor 6Y250P0

Capacity: 57.27 GB Manufacturer: ATA Model: IC35L060AVV207-0

Capacity: 4.11 GB Manufacturer: PIONEER Model: PIONEER DVD-RW DVR-107D Revision: 1.18 Drive Type: CD-RW/DVD-RW

ACARD,6280M (to allow running the huge 233 GB Maxtor): Name: ACARD,6280M Type: scsi Bus: PCI

ATY,Rage128Pro (driving a MAG Innovision monitor): Type: display Bus: AGP Slot: SLOT-A VRAM (Total): 16 MB

ATY,Rage128 (driving a ViewSonic A75s monitor): Type: display Bus: PCI Slot: SLOT-D VRAM (Total): 16 MB

That’s the studio Macintosh. Our network consists of a Netgear router and an Airport Express. The network has a Mac Mini and Powerbook Aluminum 15. Finally, a nice 3G 20GB iPod to top it off!! Other studio stuff can be seen here.