thewhitehartI think this is embarrassing that Apple has not solved this issue yet. With so many intel mac users having problems, it makes me think that Apple refuses to acknowledge a faulty chipset with the airport cards in the early intel Core Duo iMac models. As far as I'm concerned, a fix should be out for this ASAP - it is a serious problem that seems to occur almost randomly.
I have exhausted numerous methods to correct this issue - following Apple's instructions precisely to delete and re-add WPA2 networks. I have tried it from both administrator and standard accounts, applying the change, and quitting System Preferences before turning on Airport. I have tried the so called fix with airport on and off, I have tried hard resetting the mac after re-adding the WPA2 networks, I have tried 'Automatic' and 'Preferred Networks' settings, I have tried adding only one WPA2 network and adding many - I have tried every method possible will an exhaustive list of variables without resorting to the Terminal and UNIX, which I am not skilled enough to do. The problem has occurred only after the 10.4.8 update, and even after the firmware updates and the 10.4.8 security fix. After following Apple's recommended fix and then shutting down the computer, the iMac often freezes and power needs to be cut from it. Using a G4 ibook as a control group has narrowed it down to an intel only problem, but I suppose Apple already knows that - so why aren't they fixing it?
Airport won't connect after startup or after sleeping. I can't seem to pinpoint the steps I've taken that have actually affected a successful reconnection to my router. It seems to be totally random when airport finally decides to stay connected. I've tried resetting the router too, which is an airport express, but it didn't help. Nor did checking the box under 'Options...' that tells airport to disconnect after I log out. While logged in, airport will suddenly lose connection, and will drop and reconnect to my preferred network several times. It never successfully receives an IP address from the router, though, and ends up assigning itself an IP address. Once in a while, it cannot find my network at all, and all attempts to shut airport on and off to see if the network reappears resulted in failure. The airport express light is green and running at all times, as my G4 ibook can successfully hold a connection. As for the poster who asked about my signal, yes; it does drop to one bar and becomes very slow on occasion. I have ruled out interference from other radio sources and it seems to be tied to the existing airport problem.
I am now connected to my router and receiving an IP address from it, but it may lose connection at any time. The circumstances at which it is connected now are the same as the circumstances as when the connection problems occur as far as I can tell. It's driving me nuts - not only am I unable to pinpoint the cause of the disconnections, but I am unable to identify the exact solution to keeping it connected. It seems to have a mind of its own.
