Same problem here with my Mini. After upgrading to leopard this aiport not reconecting started happening. I am not even using encryption either. Every time it sleeps and I re-start, I need to "turn off wireless network", then turn it back on again. What a pain. This is a direct result of upgrading to leopard. I upgraded my G5 iMac at the same time and it doesn't have the issue. Makes me think it is a hardware specific anomaly. I hope there is a patch for it. It is getting old and I really used to enjoy starting up my Mini. Now its just a pain
I'm pulling my hair out.
My Tiger-running 17" Powerbook connects beautifully to my airport network.
My newly installed iMac with Leopard completely refuses to connect automatically to it.
I have to connect manually every time, by selecting it in the airport menu.
I've tried deleting all relevant keychains, plists etc., nothing seems to help. Tell me this isn't a leopard bug?
Any other ideas?
Thanks,
Jestyn
My problem seemed to be with WEP. I have a nintendo DSLite and was using WEP64 to be able to connect my DS to my network. Once I switched the router to either WPA or WEP128 it connects every time with no problems. Hope this helps someone.
deleting(or moving out and renaming) /system/Library/Extensions/AppleAirPort.kext worked for me as well. Finally! Thank you for the answer in this post. Its strange that Apple is not recognizing or putting out a fix for this. It was clearly the Leopard upgrade and this problem is completely repeatable.
Once again I'm having problems keeping a connection with 10.5.1. I've tried everything posted so far. I don't have the AppleAirPort.kext file. What creates that file? I have the newer Airport Extreme.
I can't even use my Apple TV anymore...airport disconnects before a movie can be transferred. When I reconnect...the movie has to start syncing from the very beginning.
This is so frustrating! And Apple still insists it's an unknown problem??!!!
I stand corrected. I did not fix the problem. It fixed it if I put the mini to sleep from the apple menu and start it up again. But, if I leave it unattended for a while and it goes to sleep, it still does not reconnect. That gets old after a while.
Model Name: Mac mini
Model Identifier: Macmini1,1
Processor Name: Intel Core Duo
Processor Speed: 1.83 GHz
Number Of Processors: 1
Total Number Of Cores: 2
L2 Cache: 2 MB
Memory: 2 GB
Bus Speed: 667 MHz
Boot ROM Version: MM11.0055.B08
SMC Version: 1.3f4
System Software Overview:
System Version: Mac OS X 10.5.1 (9B18)
Kernel Version: Darwin 9.1.0
Boot Volume: Macintosh HD
Boot Mode: Normal
I have the same symptoms except the airport says it's connected. If I go to network preferences and turn the airport off then on I can see it connect. It's all there, the default route, DNS servers, and the IP address is as it should be. I can't even ping the default route and you can't ping into the box either. The only way I have found to fix this is a reboot.
This is my first Mac. I bought it because I just didn't want to deal with Vista. but I'm beginning to think that it's six of one and half dozen of the other.
I've seen this problem with several different accounts now.
I now have a procedure which appears to fix it, but I'm not sure it is the minimal procedure. Folks who try this may find they can eliminate one or more steps and still get the good result.
Symptom: Airport won't reconnect to a known network, and turning Airport off and then back on again does NOT make the connection to the known network happen.
Solution: Do the following steps in order
-- Turn off Airport
-- Go to System Preferences / Network. Click on the lock and authenticate with an administrator password if necessary.
-- Select Airport in the column on the left.
-- CLEAR the check box for "Ask to join new networks"
-- Click on Advanced.
-- CLEAR the check box for "Remember any network this computer has joined"
-- Click on the known network in the list if it is already in there. Click on "-" to delete it from the list.
-- Click OK to exit the Advanced pane. Click Apply in the main Network pane to make these changes take effect.
-- Now turn on Airport. The network will not be selected of course since it is no longer "known".
-- Click on the Airport indicator in the Menu Bar to open the drop down menu.
-- Click on "Join Other Network". Do this EVEN IF the network you wish to join is not "closed, i.e., is already showing in the list.
-- In the dialogue panel, enter the name of the network, the type of password, and the password itself. Also *VERY IMPORTANT* click to check the box to "Remember This Network". Connection should now be established.
-- Return to the System Preferences / Network pane. Click on Advanced again and confirm that this network is once again in the list. Click on Cancel to return back to the main Network pane without making any changes.
-- Click on Assist Me. Click on Diagnostics.
-- Even though the early test will likely say that everything is fine, click Continue to go through the rest of the tests ANYWAY. The Airport network you are connected to should show up in the list when you are asked to choose which network to join. Click on it. If it is not in the list for some reason, select Other and type in its name.
-- You should now be presented with a panel asking you to AGAIN enter the password for this network. Do so. And *VERY IMPORTANT* click to check the box to remember this password in the keychain.
-- Diagnostics should now complete and tell you everything is fine.
At this point, your account should now reliably and automatically rejoin this network either on restart or on waking from sleep. If the system ever misses the network on restart or waking due to weak signal or some transmission timing glitch on startup, simply turning Airport off and back on again (using the indicator in the menu bar) should suffice to get you connected again. This procedure for remembering the network should work with both open (visible names) and closed (non-visible names) networks.
Presumably there is something going on in this procedure that causes the key bits of information to be saved in the right places.
It SHOULD be easier than this of course. But at least this seems to work until Apple sorts this out.
Please note that this appears to be a PER-ACCOUNT problem. I.e., you will likely need to fix this in EACH account that's having trouble remembering the network and re-connecting automatically.
I have a similar problem though only occasionally. I wake my computer and it can't find my Airport network although it finds some other one. At least so far, if I again close my computer and put it to sleep; wait a moment for it to sleep; then reawaken, my computer now finds the network.
BobP1776, your "Solution"
was a solution. *It did it!!* Airport is FINALLY back up! (text of solution here: [http://discussions.apple.com/thread.jspa?messageID=6002656#6002656)|http://dis cussions.apple.com/thread.jspa?messageID=6002656#6002656]
Like so many others, I'd had no problems with Airport connectivity under 10.4; but after a CLEAN INSTALL of 10.5/10.5.1, I have had 10 days of misery. All of the typical problems and failed attempts to solve them: can't connect, try different security protocols, "Broadcast" on-"Broadcast off"--even NO security; and all the flukey behavior relating to Airport/Network Prefs/Keychain having somehow been "lobotomized" in Leopard. I had tried several of the steps you described, but never
all of them and
not in the precise order you defined.
Well, it's going on 2+ hours of Airport connected at pre-Leopard performance levels. Sure, it could all still go "kerplooey"; and then I'll just post my experience and continue to watch the forums for new ideas.
You know, if forum post time-stamps are "localized" for the recipient, it's been close to 18 hours since you posted this suggestion ... I cannot
believe I might be the first to give you the *major
kudos"* and *many thanks* you deserve!
Have you seen BobP1776's recommended solution to clean up the Airport/Leopard connection issue near the end of this thread? Give it a look here: [http://discussions.apple.com/thread.jspa?messageID=6002656#6002656|http://disc ussions.apple.com/thread.jspa?messageID=6002656#6002656].
His specific series of steps is the ONLY suggestion that's worked for me in 10 days of trying
everything (I posted a reply to his, explaining.)
You started the thread ... check it out and see if BobP deserves some credit.
This worked for me also. I've been running clean now for about 10 hours with 6-8 sleep/wake cycles and all is well. I'll post again in a couple of days.
