You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Lion WiFi Connection Problem

Since installing Lion on both my IMac and MacBook Pro, the WiFi cycles (wifi icon on the menu bar) - looking for network - network on - looking for network. iMac with OS 10.6 doesn't have this problem so it's not the AirPort and there was no problem prior to installing Lion. The AirPort Utility log shows lots of connection activity but I don't know if that means anything. The network troubleshooter says theres no problem but it's causing big problems with connection speed and applications that need a constant connection are giving me network errors constantly. Please give me some advise....

Posted on Jul 20, 2011 5:19 PM

Reply
Question marked as Top-ranking reply

Posted on Jul 20, 2011 7:07 PM

Welcome to my nightmare...Been going on for a year now. Nice to see the didn't bother addressing this issue with the new OS.

2,673 replies

Sep 30, 2011 3:22 PM in response to lupunus

Some new Information from Apple's hotline an a resume of the previous findings.


First the news.

Apple phone support told, that some network files can get corrupted over time and should be deleted occasionally, especially if you have installed a new operating environment like Lion.


For that, switch OFF the wireless on the machine you want to tweak.

Delete from the system files:


* preferences.plist

* Networkinterfaces.plist

* com.apple.network.identification.plist

* com.apple.airport.preferences.plist

* (and any associated files like above that had ".orig" at the end)


Eventually you should also delete all related entry's from Keychain Access

Reboot and join the network again.


Nevertheless, there could be also different reasons for the problems one experience. For that a resume about the major issues....


In most cases, people blame on firsthand the obvious because they are mostly, by lack of knowledge, not able to see the coherence in a complicated infrastructure as wireless and networking is.

That's pretty normal and o.k. as well as a car driver mostly not have to have any knowledge about the regulations and functions of the fuel injection system.


I've discovered on many troubleshoots around wireless problems regardless of Apple, Linux or Windows, that (except a single reason became valid) in most cases it's a mix of minor issues what leads to major problems; e.g. constantly stream drop out, lousy speed, 3 stations work well but one wont, WiFi drop when a smart phone connects, up to total loss of the WiFi connection.


Although it's sometimes a rough job to find the reasons behind the trouble in networks it's always a fine idea first to eliminate all known or discoverable possible reasons.


What comes out so far?


  1. Corrupted or damaged configuration files on client.
  2. Different domains in the local network
  3. General radio problems in WiFi. Based on disturbance from interferences, obstacles in or reflections of the radio beam
  4. Mismatched settings on the network participants
  5. Problems with the 802.11b/g/n compatibility mode
  6. Hardware fault's or buggy drivers / firmware


...and of course there could be a lot more reasons.


On this I'll follow the numbering above and will also add a short description about possible reasons or a example in a not so technical manner for better understanding.


One may check, which possible solution or combination of solutions may best fit the own problematic.


#1 -> Corrupted or damaged configuration files on client.

Possible reasons: Time, Updates, Upgrades, accidentally power loss on running system and nearly countless more.

Solution: See entry of this post.

Alternative solution:

For those are a bit frightened to delete complete system configuration files. In many cases this "short version" will do the trick too.


* Switch OFF wifi on the affected machine.

* Delete all affected networks from the "known networks" list in System Settings

* Delete all keys pointing to these networks from Keychain Access

* Reboot

* Join network again.


#2 -> Different domains in the local network environment.

Description: In a network segment (your home network) all systems have to be member of the same local domain. This allows a clear name resolution (DNS) in the net. Most systems have a default set local domain name in the network configuration to ease joining a network with systems of the same bread.

Windows systems have by default set a own local domain like e.g. "workgroup" (depending on version or localisation). Mac's have by default set the local domain name as "local". Some Routers have by default set one of these, none or a different local domain name; e.g. in UK some BT-DSL/WiFi boxes provide "home" for the local domain name.

Reasons: If there different domains in the same segment (your network), name resolution trouble is programmed and that leads to unwanted network traffic, packet collisions and could at last force stations to disassociate from the network or get disassociated by access point (router) due to time out, bad or wrong response.

User experience: Slow and sluggish network, WiFi or iTunes/Video stream drop, lousy data transfer speed or being unable to open different Internet sites in the browser. Also observations like: My Windows box work well in my wireless but my Mac wont. At the office all is perfect but at home...

Solution: Configure ALL stations (clients) in your network to use the same local domain name, regardless of which name you choose. Eventually set up a second location (profile) for the particular network.

Attention!

If you want to use Apples new child "Airdrop" you must use "local" as the domain name, as Airdrop refuses to work with other local domains or with stations using not "local" for domain name.


#3 -> General radio problems in wireless networks based on disturbance from interferences, obstacles in or reflections of the radio beam

Description: The radio beams of a wireless are not Roentgen X-Ray based and therefore obstacles, interferences from other wireless systems or reflections of the radio beam could cause major disturbance of the wireless network and based on this, the data stream in the network.

Possible reasons:

  • Obstacles like Walls, magnetic fields from live high voltage lines, antenna cable or insufficient shielded speaker systems. Metal frames or plating, furniture, bundled water pipes, dry construction plaster walls*, Humans* and much more.
  • Interferences from other radio equipment like Bluetooth, cordless phones, neighborhood WiFi, cordless speakers, cordless doorbells, intercoms, ptt units, baby phone's, surveillance and alarm systems, commercial weather radar, some military equipment and so on.


*) Water is a big bar for radio. Plastered dry construction walls and Humans contain a lot of water.


One of the named possible reasons or any combination can cause major annoyance due to unwanted network traffic or packet collisions and could at last force stations to disassociate from the network or get disassociated by access point (router) due to time out or signal loss.

User experience: Heavy fading signal strength, slow and sluggish wireless connection iTunes/Video stream drop, lousy data transfer speed, total connection loss or only time relating disturbances here and there.

Solutions:

Placement of transmitter. Not flat at the wall. Not in a corner, not on the floor, not behind a furniture, not near of other radio sources e.g. cordless phones. Not near of anything that can reflect radio beams. Best: as high as possible; e.g. Airport Extreme mount on ceiling. Maximum possible line of sight to all stations respectively corners of the home.

Placement of stations: see above and below.

Placement of yourself: If possible not between your Mac' antenna(s) and the transmitter.

Radio interferences: Check that the channel you use have at least a 5 channel gap to the two strongest wireless networks around. If possible use the recommended overlapping free channels for your country for best performance. On 2.4GHz networks -> for US-1,6,11 and for Europe 1,5,9,13. If possible swap to 5GHz 802.11n only and force the stations supporting this to use only 5GHz. Disable 802,11a/b/g wireless if possible. Place cordless phone stations as far away from the router (access point) as possible. Eventually disable all radio transmitting equipment in the house. If the wireless then work better, enable one at the time to see which is the disturbing one. Don't forget leaking microwave ovens. A running faulty microwave may drown your complete wireless network at once and your neighbors WiFi too.


#4 -> Mismatched settings on the network participants.

Description: Self describing.

Reasons: New equipment in the network, differences between home and office/work settings.

Solution: Check and change to match. Eventually establish a second location (profile) in System Settings on that.

Remember: Contrary to marketing and promotion, Networking NEVER was easy Plug&Play and at least for the next few years it wont.


#5 -> Problems with the 802.11b/g/n compatibility mode.

Modern WiFi bases pretend to integrate every protocol regardless of age or used hardware in the connected stations. Pretty good idea from the viewpoint of a marketing department. Unfortunately. it could cause major problems in real wireless networks because mixing stone age 802.11a, cable LAN and lightning fast 802.11n 5GHz in the same network is a big challenge. Any minor disturbance in such a constellation may lead to major trouble. Aside from the fact, that the slowest participant in a network dictate the pace, some router's and client's chipsets have problems with that "compatibility mode".

Solution: If ever possible try to force your network on one (fastest) protocol only. If you need 802.11g (iPhone, iPod touch) try to fix your infrastructure on 802.11g 2.4GHz and 802.11n 5GHz or 2.4GHz only with the loss of the possible 5GHz speed.


#6 -> Hardware fault's or buggy drivers / firmware

What's to say? Give a bug report to Apple, wait for a fix with the next update or hope that your system is still under warranty. Eventually roll back to previous OS version or firmware.


Addendum for Airport Extreme or Time Capsule users.

If possible deactivate the "Guest Network". It constantly switches between 2.4GHz and 5GHz band for a maximum of user convenience. Unfortunately this may cause trouble if other disturbances are also in the wireless.



That's for now....



Happy networking - Lupunus

Oct 5, 2011 9:10 AM in response to hormelmeatcompany

hormelmeatcompany wrote:


If my car breaks down, is it the road configuration's fault that I can't get to work or school?

In information technology infrastructure is the physical hardware used to interconnect computers and users. Infrastructure also includes the transmission media and also the router. In technical discussions "infrastructure" also includes the settings and configurations of the physical hardware including the settings of that little interface inside the computer named NIC (network interface controller) or WNIC (wireless network interface controller).


Let's stay on your picture...

If you went to school and your car brake down there could be different reasons for that including a road configuration fault if your car hit a hidden road hole and the axle break.


To run a working network connection there are clear defined rules and regulations to follow.

and a working network connection have absolutely nothing to do with the kind or version of the operating system of any connected computer.

The network itself is for good reasons independent from any operating system.


For that is valid:

If you have a problem in your network the reason is in no manner the operating system of your computer.


There are only three possible roots of a network problem:

  • Hardware fault
  • Wrong setup of the infrastructure
  • Wrong or mismatching configuration* on at least one of the participants.


On wireless networks additionally disturbances of the radio stream; e.g. from interferences.



Lupunus


*) Wrong configuration can include a "bug" in the firmware of the NIC/WNIC but that is in the cases we discuss here very unlikely as millions of Lion users have no problems with wireless.

Oct 24, 2011 10:12 AM in response to Shivetya

Shivetya wrote:


Does airport extreme have a similar option? Can't recall but its funny to have to change my router just so OS X will work

Yes it have.


But if you use the Extreme better try the following:


  • Disable Guest Network
  • Give the 5GHz a dedicated name
  • Set radio mode to: "802.11n only (5GHz) - 802.11n only (2.4GHz)" or "802.11n only (5GHz) - 802.11b/g" if iPhone/iPod Touch is in use.
  • Force the Mac(s) to use the 5GHz only by deleting the 2.4GHz name (SSID) from the list of "known networks"


Place the Extreme on a good location with a maximum line of sight to all corners of your home (prefer ceiling mount). Not on a wall, not in a corner, not on the floor or in/behind furniture.



Lupunus

Nov 5, 2011 2:47 AM in response to lrogersinlv

The only permanent solutions I found for my setup (iMac mid 2010 Core i3 3,2 GHz / FritzBox 7270 v3) within the last three month were:


  1. going back to Snow Leopard
  2. replacing Lion`s wi-fi-drivers with Snow Leopard´s old wi-fi-drivers (http://rys.pixeltards.com/2011/09/04/osx-lion-wifi.html) > only works with the atheros-chipset and you can`t use Airdrop any more...
  3. doing a permanent ping to google.com or whatever via a terminal-window > not realy comfortable...
  4. switching to the 5 GHz-band (802.11 n+a) in my router`s configuration > iPhones can`t join the wi-fi any more as they only support 2,4 GHz in 802.11 n...


My choice is No. 2.


ALL the other tips/tricks/recommendations (from this community, different websites and Apple`s support-hotline) worked for some hours or days only in my case...

Nov 29, 2011 11:03 AM in response to lrogersinlv

As a summary of what I tried within the last days:



Gonna go back to Snow Leopard`s wi-fi-driver again and just hope for the wonder to happen with one of the next Lion-Updates...

Dec 5, 2011 2:10 PM in response to lrogersinlv

I'm sure all of you are as frustrated as I was with these issues. Here's my experience, including an improvement on the keepalive scipt, which fixed the connection issues for me.


The issue:

2011 13" MacBook Air running Lion drops WiFi connection at home every few minutes

  • Will not automatically reconnect, must manually click on the network name to get it to reconnect.
  • For what it's worth: It has a stable connection at the local university (read: *lots* of access points).
  • The problem is not the home network: my 2007 MacBook running Snow Leopard continues to connect rock-solid to the home router, as it always has.


Solutions which did not work:


  • The Apple Store, first and foremost.
    • Three visits and a new AirPort card, no fix.
    • They finally said this is a Known Issue with Lion.
  • Changing router channels
  • Creating a new network location



The solution which works for me:


  • I'm running a slightly more elegant keepalive script, based on these instructions: (http://osxdaily.com/2011/08/08/mac-wi-fi-dropping-use-a-simple-keepalive-bash-sc ript-to-maintain-wireless-connection/)
    • Zero disconnect issues while the script is running.
    • My below changes allow the script to be completely unobtrusive. It runs when you open the file, loads when you log in, starts minimized, and doesn't issue a prompt when you log out.
  • Changes to the OS X Daily instructions in red:
    • Step 1:
      • You’ll need to know your wireless access points IP address before proceeding, it’s usually something like 192.168.0.1 or 192.168.1.1.
      • You can get this information from System Preferences > Network > Advanced > TCP/IP and looking for the IP next to “Router"
      • Make note of that IP and proceed with the following:
      • This IP will only work with your home network. If you also have issues connecting to wireless access points while away from home, skip to the end and read my hint.
    • Step 2:
      • Launch the Terminal (located in /Applications/Utilities/)
      • Type the following command:

nano keepalive.command
  • Paste in the following, be sure to replace the IP with your own routers:

osascript -e 'tell application "Finder" to set visible of process "Terminal" to false'
#!/bin/bash
ping -i 5 -n 192.168.1.1
  • Hit Control+O, then hit enter to Save the contents of keepalive.sh
  • Hit Control+X to exit from nano
  • Step 3:
    • Back at the command line, we have to make the script executable, we do this with:
  • chmod +x keepalive.command
  • Step 4: Allow log out without annoying prompts to close the terminal.
    • Click Terminal > Preferences > Shell
    • Prompt before closing: Select "Only if there are processes other than:"
    • Click the + sign, type ping and hit enter
  • Step 5: Set the script to start automatically.
    • Click System Preferences > Accounts > Login Items
    • Find keepalive.command. It should be located in your home directory.
    • Drag keepalive.command to your login items.
  • Step 6: Test the script.
    • Open keepalive.command. It should load a terminal window minimized to the dock. The window should look like the top image at the OS X Daily link, with ping running every 5 seconds.
    • Log out and log back in. The script should launch automatically, minimized to the dock. You should now be able to log out without any prompts to close the terminal.
    • Hopefully, your WiFi connection is now stable because of the tiny amounts of data being constantly sent over the connection. Ping, running 24/7, will use around 1 MB per month, so don't worry about excessive data usage.
  • Hint: It's better to ping your own router while you're at home, but if you also have issues staying connected while away from home, create a second script with a different name and use Google's DNS IP, 8.8.8.8 This script will work from anywhere.

  • Thanks to Ahmet Toker and OS X Daily for this workaround!


    (Sorry about the screwy formatting of this post, the forum is not displaying it properly.)

    Dec 9, 2011 7:55 PM in response to Tuskuno

    Glad it worked for you, @Tuskuno, but no luck for me. I will say that it managed to load my FB page, but it was very slow. All other pages timed out. Probably just FB server being more responsive.


    My key symptoms continue to be:

    1. I can ping any host name without problems
    2. My browser resolves DNS name, but then cannot get through to hosts, or occasionally gets through but data comes in VERY slowly. E.g. It can take 3 minutes just to load part of a page!


    The saga continues...

    Feb 10, 2012 4:59 AM in response to laechleviel

    Will this method work for MacBook Pro (13-inch, Late 2011) ??

    Please reply!!


    Thanks

    Feb 21, 2012 5:21 PM in response to lrogersinlv

    Once again, here's a simple workaround that worked for me and at least 3 other people with the drop-out problem:


    Disabled n-mode on my router, rock stable connection ever since.


    So again for everyone with the "drop-out"-problem:


    1. Go to your router/Airport configuration,
    2. search for "Wireless Settings", change "Radio Mode" or "Wireless Network Mode" to
    3. "802.11b/g only" or "802.11G only" or "2.4GHz Only" or "G Only".


    No more dropouts for me.


    If you can't find this setting, post the model of your router and I will try to direct you there, it's a really easy workaround that takes 5 minutes to try out.

    If it works you'll only sacrifice some wireless speed for stability until it's fixed by Apple.

    -------------------------------------------------------------------------



    Here's what my original problem looked like:

    2008 macbook, worked fine with SL, on Lion the WiFi symbol showed a connection, but every few minutes the internet just "stopped".

    All other devices (iphone, android phone, win laptop, ps3) worked just fine, and had a steady connection, while the macbook was out.


    diagnosed this by pinging google on all devices, and every device kept a stable connection, only the macbook was timing out.


    Since several people posted that it "worked on their 2year-old router, but not the new one" I tried to make my new "N"-router older, or simply slower. and it worked.


    Things I tried that didn't work (again, for me):

    setting fixed DNS-server, setting the router to "N"-mode only, setting router to fixed channel.

    ---------------------------------------------------------------------------


    So once again, please try this simple workaround and post if it worked.

    Feb 24, 2012 8:04 AM in response to lrogersinlv

    Please try following - I have found this advise on macrumors.com, written by mobius1ski:

    http://forums.macrumors.com/showthread.php?t=1210649


    It may be a problem with the connection information stored in your network profile.
    1. Go to System Preferences > Network.
    2. Click the Wi-Fi connection.
    3. Click the Advanced... button on the bottom right.
    4. Click the Wi-Fi tab.
    5. Under Preferred Networks, select your wireless network.
    6. Click the - (delete) button.
    7. Turn off your Wi-Fi connection.
    8. Turn it back on.
    9. Select and login to your wireless network. This will re-save your connection under Preferred Networks.
    10. Close your laptop and reopen it to test whether it worked.

    Feb 28, 2012 11:34 PM in response to max hampel

    max hampel wrote:


    Once again, here's a simple workaround that worked for me and at least 3 other people with the drop-out problem:


    Disabled n-mode on my router, rock stable connection ever since.


    So again for everyone with the "drop-out"-problem:


    1. Go to your router/Airport configuration,
    2. search for "Wireless Settings", change "Radio Mode" or "Wireless Network Mode" to
    3. "802.11b/g only" or "802.11G only" or "2.4GHz Only" or "G Only".


    No more dropouts for me.


    If you can't find this setting, post the model of your router and I will try to direct you there, it's a really easy workaround that takes 5 minutes to try out.

    If it works you'll only sacrifice some wireless speed for stability until it's fixed by Apple.

    -------------------------------------------------------------------------



    Here's what my original problem looked like:

    2008 macbook, worked fine with SL, on Lion the WiFi symbol showed a connection, but every few minutes the internet just "stopped".

    All other devices (iphone, android phone, win laptop, ps3) worked just fine, and had a steady connection, while the macbook was out.


    diagnosed this by pinging google on all devices, and every device kept a stable connection, only the macbook was timing out.


    Since several people posted that it "worked on their 2year-old router, but not the new one" I tried to make my new "N"-router older, or simply slower. and it worked.


    Things I tried that didn't work (again, for me):

    setting fixed DNS-server, setting the router to "N"-mode only, setting router to fixed channel.

    ---------------------------------------------------------------------------


    So once again, please try this simple workaround and post if it worked.


    THIS WORKS. Amazing. My problem was a little different than everyone else's, my iMac kept giving me a "timed out" response when I tried to connect to my wifi network and it would take forever to shut off wireless, wait a few minutes, and try again. I changed my Netgear's mode to "150 mbps b/g/n mixed mode" from "150 mbps g/n only mode" and everything's fast and working now.


    Thank you Max!

    Apr 22, 2012 12:36 PM in response to lrogersinlv

    Afternoon all,


    I too was having this problem/a similar problem. My Mac Pro simply would not connect to my router, I was getting a recurring "time out" error.


    I followed several pieces of advice including the following:

    1. Deleting all known Wifi networks via Settings\Networks and then deleting all Wifi passwords from my Key Chain. Finally I deleted the Wifi info from the Preferences file in the Mac HD. Restarting after this.
    2. I connected via Ethernet and downloaded and installed the 10.7.3 Client Combo update.
    3. Resetting PRAM etc.

    None of this worked so I wanted to check it was not an issue with my Mac Pro connecting to any network therefore I tethered to my iPhone via the Mac's Airport Card. This worked.

    This prompted me to say stuff it and re-set my Router. After doing this and ensuring I carried out step 1 above again (including the re-start) I connected to my Wifi and have not had any issues so far. Albeit only an hour and a half.


    hope this helps

    Sep 20, 2012 12:18 AM in response to lrogersinlv

    Dear friends from 161 pages of support discussions: Lion 10.7.5 is out, support page says ao.

    This update also includes fixes that:

    • Resolve an issue in which icons in Launchpad could get rearranged after a restart
    • Improve Wi-Fi reliability for iMac (Late 2009 and newer)
    • ...

    If you still have Lion, please update and check whether your connection is improved. I will test your morning and report.


    I had issues with an AVM Fritz!Box 7390 on all bands, and never on my TC on 5 GHz exclusive. Good luck all.

    Jan 11, 2013 4:18 PM in response to gphonei

    Hi,


    I have not the same problem, but my brother has it.


    The "funny" thing is that he has the same MBA as me, with the same version of Lion:

    • When he connects to his Wi-Fi, it does not work, the wi-fi icon is cycling and it is unable to connect to internet.
    • When I connect to his Wi-Fi with my own MBA, everything works perfectly.

    Of course, we checked all the parameters. No difference, nothing. He told me that is Wi-Fi worked in other places so I think it is voodo or we shall exorcise is NetGear router !


    I did not read the 170 pages (wow !) of this topic to see if what I propose has already been proposed. So I propose it now 😉.


    If everyone of us opens a bug at https://bugreport.apple.com it will be visible by Apple. I recently had a problem with Lion and Time Machine. A topic was very active and many of the participants opened a bug. A few weeks later, we had a Supplemental Update that corrected the problem.


    So, let us all open a bug report ! (and make some voodo or incantations)

    Lion WiFi Connection Problem

    Welcome to Apple Support Community
    A forum where Apple customers help each other with their products. Get started with your Apple Account.