I'm totally angry, frustrated, tired, bored, disgusted with the neglect of Apple. If I'm being rude, I apologize, but there are no arguments against facts. I see on the Internet a lot of people trying to find a solution to the problem of wifi.
But the questions are: What Apple is doing to solve the problem? Why it does not manifest itself?
For what I see, Apple is COOKing the problem.
Apple had sold 1.000.000 (one Million) licenses of LION on launch day and I guess some millions more since that.
Even if a greater visible amount of people here and elsewhere arguing about problems with wireless, printing, overheating or other problems, the are statistically a minority.
And as I could learn on a couple of colleagues and friends with Lion problems, in most cases, Lion is not always the root of the trouble.
The same storys and problems boiled up every time there is a new OS release from Apple. Remember the roll out of OS X 10, 10.5 and also 10.6
So, each time there is a new OS released, the rumor starts over again, and people blame the messenger for the bad news.
I'm a computer pro since 1993 and have heard those arguments always all times someone released a new OS, regardless if it was Microsoft, Apple, Linux or someone else.
I've learnd in this years:
- Never update a OS if a big step is released. ALWAYS make a clean install instead.
- Never adopt a new OS if you're not a techi or experienced, advanced, user being able to fix some issues without help.
And I ask myself allways: "Why people doesent want to wait a liitle time until the big bugs are fixed by new releases and/or updates?"
Even as I'm a pro and experienced user, I myself always wait until the big bugs where fixed before updating a important system in my environment. Early adopting is only a option for on non-relevant machines, where it is no problem when they fail, stuck or have to reinstalled, rolled back or something like that.
I've learned too: In most cases computer problems are a PEBKAC
Cheers - Lupunus
Way to excuse Apple and blame the guy for having an OS upgrade trash his machine.
If there is one thing I have learned in this industry, there is an endless supply of apologists. All your examples of things you learned are items that many would eviscerate Microsoft over. So, LOL to you.
Still trying to understand how changing the length of my wireless password ended my connection problems under Lion. Too bad the iPad, SL, and Windows machines, in the same house hold never had an issue.
Thats basically not a Lion issue.
I once used to have a AVM wireless router that refused by default to establish a wireless connection until the password had 13 characters to match the HEX deph.
Normally the rules say "The length of the password have to match the chosen encryption depth"
Most modern systems tolerate shorter passwords. Some fill up the missing rest automatically e..g. with 0 (zero) to give the user more convinience.
Maybe in your case the former password contains unususal characters like so called nonprintable ASCI signs (Sample: ^ ) or the existing password in keychain was corrupted for some reason.
Have a nice day
Finaly i try disable WMM mode in wireless router (before is enable).
Today drop again. May by try change security type.
As said before, WMM will not be the problem.
Some additional infos will help.
Multi- or singe band wireless?
Kind of wireless (n, g, wds)?
and so on.
Sorry for delay Kevin, I've been sick. The step by step was on page 38 of this post but now below. Hope it helps but if not call Apple support they seem to be fixing some issues. My problem has remained fixed.
I just spoke to Apple Support after being extremely disappointed that 10.7.1 did not fix my wifi disconnect on boot or restart problem. Tried a couple of things but the solution came after following this process.
1. Open System Preferences, and then Network.
2. Click on Wi-Fi in the left hand column (make sure the padlock in the bottom left corner is Unlocked).
3. Click on Advanced (bottom right)
4. Under the Wi-Fi tab there is a box labeled Preferred Networks. I had many networks in this box. Select them all and then click on the "-" button. This will delete all the preferred networks. Just a side note, I always have "Remember networks this computer has joined" ticked.
5. Click OK.
6. Click on Apply.
7. Close System Preferences.
8. Restart your machine.
9. This is where things got very exciting, as for the first time since upgrading to Lion the wireless connection actually connected. The Apple Rep then asked me to restart again just to check, and it worked again.
NOTE: I did not have a problem with the wi-fi dropping out once the computer was started. This fix was for a problem with the wi-fi not connecting on Start Up or Restart.
I would recommend Apple Support, they rang me back within one minute and he said that there was a list of things that they could try. He was very helpful and the advice was step by step. The link to the US Apple Express Lane is https://expresslane.apple.com/GetproductgroupList.do
(other countries, choose before you start or you will have to repeat the process). Just continue through the process - it only takes a couple of minutes. The articles didn't help me, so I hit continue, got them to call me and now all is well. Now I can update the family computers and use the same fix if there is a problem. The Apple Support guy also said that I can use the case number to call again and get assistance with the other computers, if they have the same problem.
'interference robustness' - checked off
mine is an old domed airport extreme
use 'airport utility' click through airport/wireless/wireless options
my imac has been impotent with near constant 'request timeout for icmp' uhg for a month thus rendered worthless.
i've followed and tried every trick in all the forums & posts relating to the crisis and that bit of hudu worked for me.
weeks of uncertainty and now it's been solid for a day thus i feel much better about my life...
i was thinking the problem was with the atheros wifi chips or kext or something
bumps out to all the suffering and afflicted mac'sters keepin the message alive till we can all delete this thread from our lives like i'm about too...
You say you have seen tons of folks reporting problems but the problems aren't the same. Some folks are having trouble getting their computer to talk to wifi, some it is an issue with updating their actual router and so on. All with different computers, different routers, some might have firewalls on, some don't. Some are running programs like Little Snitch, some aren't. Some updated from Snow Leopard, some did a clean install. Some have manipulated settings like Host files to use pirated software, some haven't. So many variables make nailing down the problem a mess
Something you will learn if you hang around Apple during enough releases is that they never speak until they have an answer. yes it is frustrating but generally by the time they actually speak up or post an update they have the solution for at least 85-90% of folks if not more.
I agree with PJ. So far, the easiest fix I come up with so far is to go into system preferences, click on network. Then turn wifi off. After a few seconds I turn it back on. I seem to stay connected after that. And it beats, restarting the Mac or restarting the router.
But I only have one network listed, and I use Airport. So I don't really have a complex setup either.
As I've posted on another network, I think the best solution is to take a break from the madness, and go make a sandwich or something. I'm not saying that to be clever. Seriously, this will drive you nutty, as it did me for a while, and it's not worth it.
Yes, I know many of us need wifi to work for business (who isn't using their mac for business in some form?). But I agree with PJ. It seems like there are too many variables to this problem for there to be one fix. We might all be talking about seven or eight different problems here that manifests as one result: lost wifi connection.
I have a stable wi-fi-connection since I did an absolutely clean installation (= formatted the HD / installed Lion from dvd / only took music, pictures, videos, documents from my time-machine-backup but NO user-settings / same router/firmware as before...) of Lion at the beginning of August (> which means 4 weeks without problems). Before that I tried all the different solutions recommended in this post e. g. by the Apple`s support unsuccessfuly.
The only small bug which appears from time to time is that my Mac tells me it can`t connect to the preferred network after coming from sleep-mode although it is connected (in this case I just have to press the "cancel-button" and everything`s fine...).
Some facts on my setup:
router: FritzBox 7220
iMac: 21.5 inch - Mid 2010 - i3 3.2 GHz
software: Little Snitch, Sophos Antivirus, iStat Menus, Skype, Firefox, Chrome, TextWrangler, Adobe Photoshop Elements 9, Cyberduck, Handbrake, VLC, Xee, CleanMyMac, AppFresh, iLife+iWork, GoogleEarth, DropBox + various apps from the appstore
The turning off wifi in Sys prefs works for those where the problem is computer to router. But for many folks the trouble is router to cable modem. The router has lost track of the correct IP etc and when you try to fix it, the router doesn't save the new details. Lion, it seems, can't update the settings and doesn't know it can't. this is a problem that is likely only fixable via a Lion update. Annoying but it happens. Probably doesn't help in my case that I have an older cable modem and TWC doesn't send the new one they keep promising. So for now, i'm back on the ethernet.
There is an awfully large amount of armchair diagnosing going on here that is just causing more useless stuff to read and no real help. There are probably several bugs going on here, and I think it would best if people would just post their experiences and leave it to the developers to diagnose based on what people are encountering. Unless you download and peruse the source to Lion and try understand the firmware for the radio(s) and all other other nuances of what software is the same and what software is new/different, it's pretty silly to guess, especially on this list.
The developers are not going to get much out of reading 46 pages of comments unless each comment is short and concise about what works or doesn't work, and what steps you've tried.