-
All replies
-
Helpful answers
-
Dec 23, 2011 8:07 AM in response to mazstarby apple_boy_ut,I have the same issue like yours after upgrading to ox lion on my iMac. Annoying. I'm wondering if getting an airport or aiport extreme by apple would fix the issue. I have a ActionTec cable internet/wireless box that is old; could getting an apple wireless box fix the issue???
-
Dec 23, 2011 8:08 AM in response to apple_boy_utby Allan Eckert,I would suggest as a test see if your Mac runs any better with a wired connection to your network.
Allan
-
Dec 23, 2011 8:10 AM in response to Allan Eckertby mazstar,reading thru the responses prior - I don't think using an Apple modem/router would or does make a difference.
I just tried a suggestion to update to latest software, restart modem, create new location under TCP/IP (call it whatever) and then renew DHCP lease.
Will see if makes a difference.
-
Dec 23, 2011 8:12 AM in response to mazstarby apple_boy_ut,Did all that stuff and i stil have the issue. nothing resolved. any one here had issue with wired connection? i haven't tried that as suggested by allan eckert. my wired location isn't in the location i have my imac. But thought the issue was limited to wireless only?
-
Dec 23, 2011 8:18 AM in response to apple_boy_utby Allan Eckert,The iMac can be moved for a test.
It is better to test alternatives then to guess.
Allan
-
Dec 23, 2011 8:48 AM in response to lhaleby Richie Arendsee,Since trying to use my Apple Express for the last 2 months it is a 4 to 6 times a day drop in WIFI - the router is < 1 foot away. Renewed experience with Lion - thanks.
Had the same issue when first bought this MacBook Pro but a release in Snow managed to fix it within a month. Lion has been junk since release and nothing has been fixed.
-
Dec 23, 2011 9:18 AM in response to Richie Arendseeby JNNichols,I'm having the same issues as others here, but one observation I can offer is that it sure doesn't seem to be a HW problem (sorry of this has been mentioned, btw; I only read about 6-8 pages of the thread, not all 69). I run Win 7 via Bootcamp, and while I prefer working in the Lion environment, when this wifi problem crops up, I reboot with Win 7, and have no connectivity problems whatsoever.
I've tried a few of the suggestions here with little to no success. What has worked best for me to stay in Lion is switching back and forth between the HOMEWIFI and HOMEWIFI-5G networks, i.e., when Lion starts connecting and dropping, switch to the other. Don't know why this would work, but meh.
-
Dec 23, 2011 12:05 PM in response to Allan Eckertby galefromthousand oaks,Agree! Make sure you test the ethernet connection as well. If ethernet doesn't work, then it's not really a wifi issue.
-
Dec 23, 2011 9:59 PM in response to Oxygen70by tutpugpeter,ISSUE SOLVED! thanks Oxygen70...that post had this link..http://www.youtube.com/watch?v=TtxRfFAh8Pg which solved the issue for me. i've had this issue of wifi droppping with lion ever since it was installed. i'm no techie but it's pretty straight forward in the vidoe as to what has to be done. i followed the instructions on the video 4 days ago and no dropping at all since. previously the wifi would drop evey few hours. no kidding, this really worked for me!
-
Dec 25, 2011 5:06 PM in response to lupunusby leon-geyer,Reply to Lupunus Page 53
Seems to me that some cases, which probably haven't any relation to the mentioned driver upgrade, are due to the use of Arris Routers. I have a Arris Router and since upgrade to Lion I loose conection of a late 2008 macbook pro and a 2006 mac book pro, and even an 2ndG iPodTouch and iPhone. For example everytime I plug (due to loosing Wifi) the cable to mi newer macbookpro, all others loose conection! I knew that I can move myself 5 meters without loosing it, but it was kind of constant timeout (even trying your recomendations, lupunus, thnx). So I got another router (linksys), and conected with cable to my arris router to use it as antenna. Since then, I have no issues with signal dropping in any machine.
-
Dec 25, 2011 5:44 PM in response to lhaleby The Quas,I have tried every solution in this post. All of them are hack garbage that doesn't work. NOTHING WORKS. Don't waste ur time. I bought an airport extreme and everything works fine now. Working solution = throw ir router in the garbage + buy airport extreme.
-
Dec 25, 2011 11:46 PM in response to The Quasby ferkijel,Sadly I did the same thing. Tired of waiting for Apple to come up with a solution I purchased a used D-Link DWL-G810 wireless bridge, placed it beinh my iMac table, and wired it. At least now my connection is stable and don't have to pull my hair 10 times a day. I still wonder if anyone understands the error messages I was getting upon connection/disconnection in the kernel.log:
Dec 22 15:10:01 unknown045453001cd8 kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).
Dec 22 15:10:07 localhost kernel[0]: en1: BSSID changed to 00:24:c9:6a:4b:00
Dec 22 15:10:07 localhost kernel[0]: AirPort: Link Up on en1
Dec 22 15:10:07 localhost kernel[0]: en1: BSSID changed to 00:24:c9:6a:4b:00
Dec 22 15:10:08 localhost kernel[0]: AirPort: RSN handshake complete on en1
Dec 22 15:10:35 unknown045453001cd8 kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).
Dec 22 15:10:37 localhost kernel[0]: en1: BSSID changed to 00:24:c9:6a:4b:00
Dec 22 15:10:37 localhost kernel[0]: AirPort: Link Up on en1
Dec 22 15:10:37 localhost kernel[0]: en1: BSSID changed to 00:24:c9:6a:4b:00
Dec 22 15:10:38 localhost kernel[0]: AirPort: RSN handshake complete on en1
Dec 22 16:03:08 unknown045453001cd8 kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).
Dec 22 16:03:11 localhost kernel[0]: en1: BSSID changed to 00:24:c9:6a:4b:00
Dec 22 16:03:11 localhost kernel[0]: AirPort: Link Up on en1
Dec 22 16:03:11 localhost kernel[0]: en1: BSSID changed to 00:24:c9:6a:4b:00
Dec 22 16:03:11 localhost kernel[0]: AirPort: RSN handshake complete on en1
Dec 22 16:03:31 unknown045453001cd8 kernel[0]: en1: BSSID changed to 00:24:c9:6a:4b:00
Dec 22 16:03:56: --- last message repeated 1 time ---
Dec 22 16:03:56 unknown045453001cd8 kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).
Dec 22 16:03:59 localhost kernel[0]: en1: BSSID changed to 00:24:c9:6a:4b:00
Dec 22 16:03:59 localhost kernel[0]: AirPort: Link Up on en1
Dec 22 16:03:59 localhost kernel[0]: en1: BSSID changed to 00:24:c9:6a:4b:00
Dec 22 16:03:59 localhost kernel[0]: AirPort: RSN handshake complete on en1
Dec 22 16:04:24 unknown045453001cd8 kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).
Dec 22 16:04:27 localhost kernel[0]: en1: BSSID changed to 00:24:c9:6a:4b:00
Dec 22 16:04:27 localhost kernel[0]: AirPort: Link Up on en1
Dec 22 16:04:27 localhost kernel[0]: en1: BSSID changed to 00:24:c9:6a:4b:00
Dec 22 16:04:28 localhost kernel[0]: AirPort: RSN handshake complete on en1
Dec 22 16:04:45 unknown045453001cd8 kernel[0]: en1: BSSID changed to 00:24:c9:6a:4b:00
Dec 22 16:05:19: --- last message repeated 1 time ---
Dec 22 16:05:19 unknown045453001cd8 kernel[0]: en1: BSSID changed to 00:24:c9:6a:4b:00
Dec 22 16:05:27 unknown045453001cd8 kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).
Dec 22 16:05:44 localhost kernel[0]: en1: BSSID changed to 00:24:c9:6a:4b:00
Dec 22 16:05:44 localhost kernel[0]: AirPort: Link Up on en1
Dec 22 16:05:44 localhost kernel[0]: en1: BSSID changed to 00:24:c9:6a:4b:00
Dec 22 16:05:44 localhost kernel[0]: AirPort: RSN handshake complete on en1
Dec 22 16:05:53 unknown045453001cd8 kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).
Dec 22 16:05:56 localhost kernel[0]: en1: BSSID changed to 00:24:c9:6a:4b:00
Dec 22 16:05:56 localhost kernel[0]: AirPort: Link Up on en1
Dec 22 16:05:56 localhost kernel[0]: en1: BSSID changed to 00:24:c9:6a:4b:00
Dec 22 16:05:57 localhost kernel[0]: AirPort: RSN handshake complete on en1
Dec 22 16:06:15 unknown045453001cd8 kernel[0]: en1: BSSID changed to 00:24:c9:6a:4b:00
Dec 22 16:06:29 unknown045453001cd8 kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).
Dec 22 16:06:39 localhost kernel[0]: en1: BSSID changed to 00:24:c9:6a:4b:00
Dec 22 16:06:39 localhost kernel[0]: AirPort: Link Up on en1
Dec 22 16:06:39 localhost kernel[0]: en1: BSSID changed to 00:24:c9:6a:4b:00
Dec 22 16:06:40 localhost kernel[0]: AirPort: RSN handshake complete on en1
Dec 22 16:07:06 unknown045453001cd8 kernel[0]: en1: BSSID changed to 00:24:c9:6a:4b:00
Dec 22 16:07:23 unknown045453001cd8 kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).
Dec 22 16:07:26 localhost kernel[0]: en1: BSSID changed to 00:24:c9:6a:4b:00
Dec 22 16:07:26 localhost kernel[0]: AirPort: Link Up on en1
Dec 22 16:07:26 localhost kernel[0]: en1: BSSID changed to 00:24:c9:6a:4b:00
Dec 22 16:07:26 localhost kernel[0]: AirPort: RSN handshake complete on en1
Dec 22 16:07:52 unknown045453001cd8 kernel[0]: en1: BSSID changed to 00:24:c9:6a:4b:00
Dec 22 16:08:04: --- last message repeated 1 time ---
Dec 22 16:08:04 unknown045453001cd8 kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).
Dec 22 16:08:07 localhost kernel[0]: en1: BSSID changed to 00:24:c9:6a:4b:00
Dec 22 16:08:07 localhost kernel[0]: AirPort: Link Up on en1
Dec 22 16:08:07 localhost kernel[0]: en1: BSSID changed to 00:24:c9:6a:4b:00
Dec 22 16:08:07 localhost kernel[0]: AirPort: RSN handshake complete on en1
Dec 22 16:08:26 unknown045453001cd8 kernel[0]: en1: BSSID changed to 00:24:c9:6a:4b:00
Dec 22 16:08:47: --- last message repeated 1 time ---
Dec 22 16:08:47 unknown045453001cd8 kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).
Dec 22 16:08:50 localhost kernel[0]: en1: BSSID changed to 00:24:c9:6a:4b:00
Dec 22 16:08:50 localhost kernel[0]: AirPort: Link Up on en1
Dec 22 16:08:50 localhost kernel[0]: en1: BSSID changed to 00:24:c9:6a:4b:00
Dec 22 16:08:50 localhost kernel[0]: AirPort: RSN handshake complete on en1
Dec 22 16:09:17 unknown045453001cd8 kernel[0]: en1: BSSID changed to 00:24:c9:6a:4b:00
Dec 22 16:09:23 unknown045453001cd8 kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).
Dec 22 16:09:26 localhost kernel[0]: en1: BSSID changed to 00:24:c9:6a:4b:00
Dec 22 16:09:26 localhost kernel[0]: AirPort: Link Up on en1
Dec 22 16:09:26 localhost kernel[0]: en1: BSSID changed to 00:24:c9:6a:4b:00
Dec 22 16:09:27 localhost kernel[0]: AirPort: RSN handshake complete on en1
Dec 22 16:09:49 unknown045453001cd8 kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).
Dec 22 16:09:52 localhost kernel[0]: en1: BSSID changed to 00:24:c9:6a:4b:00
Dec 22 16:09:52 localhost kernel[0]: AirPort: Link Up on en1
Dec 22 16:09:52 localhost kernel[0]: en1: BSSID changed to 00:24:c9:6a:4b:00
Dec 22 16:09:52 localhost kernel[0]: AirPort: RSN handshake complete on en1
Dec 22 16:10:11 unknown045453001cd8 kernel[0]: en1: BSSID changed to 00:24:c9:6a:4b:00
Dec 22 16:10:17 unknown045453001cd8 kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).
Dec 22 16:10:21 localhost kernel[0]: en1: BSSID changed to 00:24:c9:6a:4b:00
Dec 22 16:10:21 localhost kernel[0]: AirPort: Link Up on en1
Dec 22 16:10:21 localhost kernel[0]: en1: BSSID changed to 00:24:c9:6a:4b:00
Dec 22 16:10:21 localhost kernel[0]: AirPort: RSN handshake complete on en1
Dec 22 16:10:39 unknown045453001cd8 kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).
Dec 22 16:10:42 localhost kernel[0]: en1: BSSID changed to 00:24:c9:6a:4b:00
Dec 22 16:10:42 localhost kernel[0]: AirPort: Link Up on en1
Dec 22 16:10:42 localhost kernel[0]: en1: BSSID changed to 00:24:c9:6a:4b:00
Dec 22 16:10:42 localhost kernel[0]: AirPort: RSN handshake complete on en1
Dec 22 16:11:02 unknown045453001cd8 kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).
Dec 22 16:11:05 localhost kernel[0]: en1: BSSID changed to 00:24:c9:6a:4b:00
Dec 22 16:11:05 localhost kernel[0]: AirPort: Link Up on en1
Dec 22 16:11:05 localhost kernel[0]: en1: BSSID changed to 00:24:c9:6a:4b:00
Dec 22 16:11:05 localhost kernel[0]: AirPort: RSN handshake complete on en1
Dec 22 16:11:41 unknown045453001cd8 kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).
Dec 22 16:11:55 localhost kernel[0]: en1: BSSID changed to 00:24:c9:6a:4b:00
Dec 22 16:11:55 localhost kernel[0]: AirPort: Link Up on en1
Dec 22 16:11:55 localhost kernel[0]: en1: BSSID changed to 00:24:c9:6a:4b:00
Dec 22 16:11:55 localhost kernel[0]: AirPort: RSN handshake complete on en1
Dec 22 16:12:14 unknown045453001cd8 kernel[0]: en1: BSSID changed to 00:24:c9:6a:4b:00
Dec 22 16:12:44: --- last message repeated 3 times ---
Dec 22 16:12:44 unknown045453001cd8 kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).
Dec 22 16:12:47 localhost kernel[0]: en1: BSSID changed to 00:24:c9:6a:4b:00
Dec 22 16:12:47 localhost kernel[0]: AirPort: Link Up on en1
Dec 22 16:12:47 localhost kernel[0]: en1: BSSID changed to 00:24:c9:6a:4b:00
Dec 22 16:12:47 localhost kernel[0]: AirPort: RSN handshake complete on en1
Dec 22 16:13:09 unknown045453001cd8 kernel[0]: en1: BSSID changed to 00:24:c9:6a:4b:00
Dec 22 16:13:39: --- last message repeated 2 times ---
Dec 22 16:13:46 unknown045453001cd8 kernel[0]: en1: BSSID changed to 00:24:c9:6a:4b:00
Dec 22 16:14:08 unknown045453001cd8 kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).
Dec 22 16:14:11 localhost kernel[0]: en1: BSSID changed to 00:24:c9:6a:4b:00
Dec 22 16:14:11 localhost kernel[0]: AirPort: Link Up on en1
Dec 22 16:14:11 localhost kernel[0]: en1: BSSID changed to 00:24:c9:6a:4b:00
Dec 22 16:14:11 localhost kernel[0]: AirPort: RSN handshake complete on en1
Dec 22 16:14:34 unknown045453001cd8 kernel[0]: en1: BSSID changed to 00:24:c9:6a:4b:00
Dec 22 16:15:04: --- last message repeated 2 times ---
Dec 22 16:15:14 unknown045453001cd8 kernel[0]: en1: BSSID changed to 00:24:c9:6a:4b:00
Dec 22 16:15:33: --- last message repeated 1 time ---
Dec 22 16:15:33 unknown045453001cd8 kernel[0]: AirPort: Link Down on en1. Reason 16 (Group Key Handshake timeout).
Dec 22 16:15:37 localhost kernel[0]: en1: BSSID changed to 00:24:c9:6a:4b:00
Dec 22 16:15:37 localhost kernel[0]: AirPort: Link Up on en1
Dec 22 16:15:37 localhost kernel[0]: en1: BSSID changed to 00:24:c9:6a:4b:00
Dec 22 16:15:37 localhost kernel[0]: AirPort: RSN handshake complete on en1
Dec 22 16:15:54 unknown045453001cd8 kernel[0]: en1: BSSID changed to 00:24:c9:6a:4b:00
Dec 22 16:16:08: --- last message repeated 1 time ---
Dec 22 16:16:08 unknown045453001cd8 kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).
Dec 22 16:16:11 localhost kernel[0]: en1: BSSID changed to 00:24:c9:6a:4b:00
Dec 22 16:16:11 localhost kernel[0]: AirPort: Link Up on en1
Dec 22 16:16:11 localhost kernel[0]: en1: BSSID changed to 00:24:c9:6a:4b:00
Dec 22 16:16:13 localhost kernel[0]: AirPort: RSN handshake complete on en1
Dec 22 16:16:26 unknown045453001cd8 kernel[0]: en1: BSSID changed to 00:24:c9:6a:4b:00
Dec 22 16:16:46 unknown045453001cd8 kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).
Dec 22 16:16:49 localhost kernel[0]: en1: BSSID changed to 00:24:c9:6a:4b:00
Dec 22 16:16:49 localhost kernel[0]: AirPort: Link Up on en1
Dec 22 16:16:49 localhost kernel[0]: en1: BSSID changed to 00:24:c9:6a:4b:00
Dec 22 16:16:50 localhost kernel[0]: AirPort: RSN handshake complete on en1
Dec 22 16:17:02 unknown045453001cd8 kernel[0]: en1: BSSID changed to 00:24:c9:6a:4b:00
Needless to say the log is endless.
Now that I have a less cluttered log I noticed I am getting this "new" error, which I need to work out with the help from another thread:
12/26/11 8:37:00.000 AM kernel: IOSurface: buffer allocation size is zero
-
Dec 26, 2011 12:51 AM in response to The Quasby Froggy Grodkin,@ The Quas
The Quas wrote:
I have tried every solution in this post. All of them are hack garbage that doesn't work. NOTHING WORKS. Don't waste ur time. I bought an airport extreme and everything works fine now. Working solution = throw ir router in the garbage + buy airport extreme.
Note your input, highlighted in the quote from your Post above, suggests that the ONLY thing you have tried is ‘buying’ an Airport Extreme?
You obviously have not even READ all of this Thread never mind trying everything suggested in it!
If you list, and post below, ALL the different solutions-workarounds-or attempts at resolution mentioned above then I will eat humble pie and sincerely apologise for my outburst.
Anyone who cares to read this thread is likely to draw the conclusion that this issue is not the result of one single root cause, so throwing money at the problem in the manner you are suggesting is not the solution for everyone. It may well be a solution for someone with a Router that has come to the end of it’s working life, but that is not to say that your choice is necessarily the best for everyone in that situation.
Having ‘thrown’ money at the issue just hope that your Wi Fi stays connected for a decent period of time.
I ‘found’ this thread when it was on page 39, I read all the existing pages and tried most of the the items that seemed reasonable to me.
I still follow the progress here closely.
The most significant attempt I made lasted 6 weeks before the dreaded ‘dropping’ started again.
Incidentally I also bought a new Router Modem but that was for completely unrelated reasons.
My ‘dropping’ issue was resolved several months ago by temporarily making alterations to my DNS Addresses.
I switched them to those provided free by OpenDNS and experienced immediate success, other sources were tried but without success.
After a few days I switched back the Addresses supplied by my ISP, which were previously in use when I had the ‘dropping’ issue, but now the wireless connection is rock solid. This seems to imply the issue was nothing more than a glitch?
Sadly this is only one solution for one case, but if you never attempt to find a solution perhaps you never will.
I will not repeat the process for applying the DNS ‘trick’, it has already been well documented above, sadly buried in the mess of ‘me too’ posts and other pointless input.
Please do take note of what has been written above:
Anyone who cares to read this thread is likely to draw the conclusion that this issue is not the result of one single root cause
IMO there is a solution for everyone, if it were as straightforward as an OS Upgrade Apple would have reacted by now, this means affected users need to do something about their problems other than just complaining.
It is hard work trawling through the mass of input in this and other similar, in subject and size, threads.
There are members frequenting this thread offering help, by suggesting the affected user inputs code and subsequently publishes the results in these pages, but very few take up those offers because seemingly they are prepared to await an automatic cure or other miracle.
Many users could, if they wished, connect using a cable and if that does not resolve their dropping issue perhaps start looking for the root of the problem outside of the Wi Fi area?
It would be really great if some of the long departed early posters in this thread returned to update their experiences, either reporting resolutions or failures.
Please do not post ‘cures’ unless they have been proven to work for more than 3 months.
Don’t forget to list the equipment invloved to help others follow, or avoid [if you have been unsuccessful], your route.
If you have deployed a ‘workaround’, i.e, using old drivers for Wi Fi Hardware, be clear about the situation.
Good luck to those willing to try to find a solution, remember you probably can do it all you really need is want to do it.
-
Dec 26, 2011 1:35 AM in response to Froggy Grodkinby ferkijel,Froggy, I MUST agree that the problem is a tough beast, and definitely not a result of a single root cause. 100% agreed. But there's no need to accuse someone of not trying anything...I can relate to Quas...I DID read every single post in this 69 page long (to-date) thread, and tried absolutely every single thing. I have had this dropped WiFi issue since I unpacked my iMac 21.5" in early October. After almost 3 months of futile attempts I chose a workaround and spent 15 bucks in a used WiFi bridge.
Now, the reason for my reply: your workaround (the magic DNS thing) points out that either:
1) Your problem was between your router and your ISP, not between you and your router, as seems to be the case for 99.9% of the people complaining about this issue
2) Your problem was solved because of another "fixes" you tried.
Trying to fix a dropped connection between your WiFi card and your router with a DNS change is like adjusting the seat height of your car to fix an engine issue. Totally disconnected, no relationship at all. Please don't get me wrong, I do believe every word you say that your problem was there, and now it's fixed, but it was not your WiFi card/drivers/configuration to begin it (but rather your general Internet connection configuration instead), or it was not the DNS change that fixed it.
To all those still trying to work around the dropped WiFi issue: please do not continue to attempt to fix your connection to the router by playing with your DNS settings. It only clutters the list of non-proven solutions.
-
Dec 26, 2011 2:11 AM in response to tutpugpeterby Jean-Yves Vienne France,Thank you so much for posting the link. it solved the issue I had been having since I upgraded to Lion in july. I had tried so many thing which did not work that I had gave up looking for a solution hoping Apple would do the job. I am quite amazed that it is someone outside Apple that found the way to get aroung the driver issue on the Atheros card.
If you have and iMac 21.5 2010 with an Atheros card follow the tuto on youtube.
Thank's again for relaying the Rys Sommefeldt fix