I suspect the problem is that we are fighting multiple issues here -- only one of which is the inability of Leopard to correctly record info for a known network unless you do things in a specific order.
A connection timeout SHOULD leave an error message in the Console (Applications / Utilities -- select All Messages). The error message may give an idea as to what part of the protocol got unhappy.
It would also be wise to revisit your network settings and make sure you don't have anything funky turned on by default. One easy way to do this is to create a new "location" in System Preferences / Network. The new "location" gives you a fresh area to record a set of network settings, and starts (or is supposed to start) from the standard default settings. If a new "location" works for you -- perhaps in conjunction with the steps I posted -- compare the network settings you ended up with in the new location with what you happened to have in the "Automatic" location. That may tell you what you need to correct in "Automatic" to get it working.
--Bob
OK, I've done a lot more testing. The problem appears to be the Leopard operating system and issues with some wireless basestations. I tested with my old Draytek Vigor 2600We which only has 802.11b and WEP security. I tested a range of combinations and found the mac mini would connect fine after waking from sleep with this unit. However, once I enabled WEP it would in most cases automatically connect after waking from sleep mode. About 10-20% of the time it would have the same problem of waking from sleep (ie. Airport remaining in the ON mode, but not then changing to the Connected mode)
The system log reports things like "Could not find preferred networksl trying broadcast requests.." then "Broadcast requests failed.."
With my Billion BiPAC 7401VGP with 802.11 b&g modes, I tried turning broadcasts (SSID on), setting the 802.11b only, different Channel ID's. However, in all cases when the mac wakes up it won't automatically connect. Like I said above, I never had this problem with Tiger.
So I'll ask on the Billion forums if they have started to see this problem. It's going to be hard to get Apple and Billion to work on this, but maybe Apple's wireless reconnect problem with Leopard is generic enough that with future updates it fixes the problem for me...
I created a new location yesterday, and at first I thought it helped. I logged out and back in, and the connection resumed, but only for a few seconds. The same happened after a restart.
I took the machine home with me and connected to my home network. I am also using WEP at home, but with a broadcast SSID. The MacBook established and maintained a connection without issue. At this point, I am assuming the non-broadcast SSID at work is a major factor in this.
We are using Cisco 1200 series access points in the schools, and have had no significant connection issues up to this point, with hundreds of Mac and Windows workstations in use.
Does anyone have any other ideas? Wish apple support used this site to reply to us all...
think i may just go and demand money back for Leopard as this is the biggest problem in the world for me i love leopard but i love the internet more. I cant have both!
I have gone through and followed Bob's fix-it steps but when I go into assist me/Diagnostics, my network status' are as follows:
AirPort = Green Light
AirPort Settings = Green Light
Network Settings = Green Light
ISP = Green Light
Internet = RED LIGHT FAILED
Server = RED LIGHT FAILED
We have a mac book pro here that is also running on Leopard that is connecting just fine.
Any suggestions?
Did you get a live connection at the earlier step where you Joined Other Network from the icon in the menu bar? You can test this by having Safari open and seeing if you can get to a web page at that point.
The indications from Diagnostics appear to mean that your router can not complete the connection through your ISP. Is your router talking to your ISP with DHCP (automatic request for IP address and such) of with PPPoE (a name and password have to be exchanged between your router and your ISP to activate the connection?
If PPPoE do you have a PPPoE service in the column on the left of System Preferences / Network. If you select it, is it configured correctly with your ISP account name and password? As I recall the PPPoE service also has to be associated with the Airport connection you are using to talk to your router -- as opposed to a wired ethernet connection to your router. You may be able to connect to the router, but it is not receiving the PPPoE info.
I have not tried the steps I posted earlier on a PPPoE setup -- only in DHCP setups. It is possible that when you discard the known network in Network preferences, and before you go to first activate it by turning Airport back on, you need to do an intermediate step to reset the settings in the PPPoE portion of your Network preferences.
--Bob
Have had the very same thread of problems with the internet losing it's connection everytime the computer moves, sleeps wakes or whatever! I have now copied BOB'S solution to a sticky and sent it to all the macs (2) in the house so repairs can happen without frustration. Thank you! I do hope an upgrade and fix from Leopard is in the works. HUGE KUDOS to BOBP1776!
Total kudos to BobP from me too. Even though at the end of the procedure my network was still not responding at all - I then restarted and it has worked since then. I think my heart palpitations are beginning to subside slightly.
What I do sincerely want is for Apple to acknowledge that they have caused havoc here, and for an apology to be issued as in this day and age working without the internet is just not an option.
Jon,
Check your Console (Applications / Utilities / Console -- select "All Messages") to see if any helpful error messages are being thrown.
I suspect you are fighting a combination of problems some of which may be revealed in the error messages relating to network services (DNS etc.).
--Bob
