Currently Being ModeratedMar 30, 2013 6:33 AM (in response to Mr G Almighty)
Google chrome gives this error message when the Wifi drops
Error 105 (net::ERR_NAME_NOT_RESOLVED): Unable to resolve the server's DNS address
And also when I boot up, Avast tells me of an internal error and I should check the avast program or the system logs, but I don't know where to find the system logs, or what I'm looking for in them.
- Mr G
Currently Being ModeratedMar 30, 2013 6:40 AM (in response to Mr G Almighty)
First problem is use of anything such as MacKeeper or Avast...there have been regular problems reported on here with that kind of software...and MacKeeper is very hard to remove, it places files in hidden locations that are not removed by the uninstaller. You need to thoroughly cleanse the system of MacKeeper and Avast.
Second, when you say you did a router reboot did you disconnect the power to the router? The DHCP daemon has to completely stop and many routers do not power down on the power button but go to standby. The DHCP daemon does not restart properly under those conditions.
Power down all devices and disconnect power to the router. Wait ten minutes or so and then restart the router and give it a few minutes to capture the initial IP address and stabilize. Then startup the connected devices one at a time giving each a few minutes to establish their IP address and stabilize.
Currently Being ModeratedMar 30, 2013 6:44 AM (in response to Ralph Landry1)
When I powered down the router I did disconnect it but only for a few seconds, and since finding out where the system log is I've seen a "daemon" section with a stream of information on internet activity, but when it goes down it stops.
I'll unplug the router for about 10mins now, and do you have any suggestions on how to remove avast and mackeeper?
- Mr G
Currently Being ModeratedMar 30, 2013 7:07 AM (in response to Ralph Landry1)
Phew, lucky me I used that exact guide to uninstall my Mackeeper.
I've reset my router, and by that I mean leaving it off for 10mins and now I've connected back to it, is there anything else I should do?
Currently Being ModeratedMar 30, 2013 7:28 AM (in response to Mr G Almighty)
Off hand for now just see if the system is stable.
Have you checked to see if there are firmware up dates for the router? You need to login to the router to do that, but that is all that comes to mind right now.
Good that you did Phil's MacKeeper cleanup, should be ok in that area.
Currently Being ModeratedMar 30, 2013 7:34 AM (in response to Ralph Landry1)
I've unstalled Avast now, and mackeeper and while my internet is much faster the problem still persists.
I've noticed I'm on channel 6, would channel 11 be better?
It is last alot longer now but still happening every now and then
Currently Being ModeratedApr 8, 2013 11:31 PM (in response to Mr G Almighty)
I'm having the same problem, and i think it all started when i updated to 10.8.3. This happened to me last year on my imac and it was so annoying. it seems like everytime apple releases a new update there are bugs that cause my wifi to drop.
Currently Being ModeratedApr 9, 2013 2:02 AM (in response to Mr G Almighty)
I have had this problem for months and have been forced to use an ethernet cable until this week when I have resolved my problem. I change the channel on my router from auto to manual and set it on 9 and applied it. Since then no problems. I believe it was interference from my house phone system so by changing the channel to 2 nopw operate on difference frequencies.
hope you get it fixed
Currently Being ModeratedApr 11, 2013 6:41 AM (in response to Mr G Almighty)
I have the same problem
After the 10.8.3 update, my modem wi-fi network has stopped working for me. I tried diagnostics but 2 wi-fi channel still doesn't work.
I need to plug in a router (I use with hotel travelling for ethernet sharing) and that works
Mobile broadband and tethering also works
so it is very specific to which wi-fi connection the laptop will work now
Tried everything as the original poster said, nothing works, I really need this working again
Currently Being ModeratedApr 11, 2013 8:29 PM (in response to dreve)
I have the same problem. My iMac is on 10.8.3 and it disconnects from wifi after sleep. I have to search for my network and reconnect. I have an Airport Extreme.
I've had both the Airport Extreme the iMac for quite a while This only started to occur with the latest OS X update to 10.8.3
Currently Being ModeratedApr 11, 2013 8:34 PM (in response to Mr G Almighty)
I hate to say this but your router "Belkin N+ Wireless Router" is not dual band. When you have a mixed network of B, G, & N (like an iphone, mac, other stuff), your router switches bands leaving some of your stuff confused. It happens more than you think.
Try setting your router to B/G only and see if this fixes the problem. If it does then you know what you need to do. Get a decent dual band router. I think the AEBS (airport extreme base station) is outstanding.
Currently Being ModeratedMay 4, 2013 11:11 AM (in response to Mr G Almighty)
I have been having this problem with just one of our iMacs in our house. I went through Apple support and navigated through all the twists and turns they suggested to try to get the problem solved. NOTHING WORKED. THEY DON"T KNOW HOW TO FIX THIS PROBLEM. BUT I DO! Unfortunately it involves buying a $30 wireless ethernet adapter (I got an IOGEAR, and I have no connection to their company. Probably any wireless ethernet adapter will work). I turned off the internal airport wireless device and through the network settings in the system preferences connected to my CISCO LYNKSYS ROUTER (which has been bashed left and right in the forums here). THE PROBLEM IS SOLVED!!!!! NO RESTARTING!!! NO DROPPED CONNECTIONS!!!!
So the problem isn't with the router, its with the airport wireless adapter in the iMac. It ***** to have to spend more money after you lay out so much for an apple product, but it sure beats restarting the computer over and over every day.
Hope this helps my friends out there. I can now allow my hair to repopulate my head since I've been pulling it out over this issue for months.