Macbook Air Rev.C won't connect to Wireless router

Discussion in 'MacBook Air' started by edblor, Mar 11, 2010.

  1. macrumors regular

    Jan 15, 2008
    I have a Macbook Air Rev.C 1.86GHz and just yesterday, it stopped connecting to my D-Link wireless router.

    There have not been any updates applied to the router or the Mac recently, nor have I installed any apps to the Mac either.

    My iPhone sees and connects to the router fine, as does my MSI netbook, and my TabletPC too.

    I have turned the router off numerous times in trying to troubleshoot this, and only for a minute or two, does the Mac see the router and connect getting an IP. It then loses the connection shortly after.

    I have turned off the Mac's Airport a number of times, I have reset the SMB (I think, using the ctrl/shift/option/Power button while off, letting go, then pressing the Power Button only).

    Any thoughts or suggestions?

    Until yesterday evening, everything was fine with my Mac's wifi.

  2. macrumors regular

    Dec 3, 2009
    If you go to System Preferences > Network > select Airport > Advanced > TCPIP, does it say configure IPV4 'Using DHCP' - in other words getting its ip address etc from the router? And has the Air been given an IP address from the router?
  3. Gee
    macrumors 65816

    Feb 27, 2004
    London, UK
    First thing I normally try after restarting everything is to change the channel on your wifi. Might be some new interference somewhere that is affecting the air more than your other devices.
  4. macrumors 6502

    Mar 22, 2009
    Rockville (Despite REM's plea.)
    A couple of things come to mind:

    1) make sure your home connection is first in the list of know networks:

    System Preferences > Network

    select AirPort
    select Advanced > Airport

    2) there was a thread somewhere on here about having to do some magic things if you were upgrading, but it seems odd that it would all of a sudden happen.

    3) Do you see anything related to en0 in the System Console (/var/log/system.log if you are command line person)

    4) It could be a permissions issue, might be worth running "Repair Permssions" on you root volume from Disk Utility.

    5) It could be bad hardware. Apple might ask you to reinstall your OS.

    Good luck.

Share This Page