The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    Airport/Safari difficulties

    Discussion in 'Apple and Mac OS X' started by gms238, Dec 3, 2010.

  1. gms238

    gms238 Notebook Consultant

    Reputations:
    8
    Messages:
    133
    Likes Received:
    0
    Trophy Points:
    30
    I need some help with my wife's Dec/2008 MBP. Specs are 4 gb ram and a 500 gb hd, with more than 200 gb free.

    Problem: She was doing some work on the 'Net when all of the sudden Safari came up with a message that stated she wasn't connected. However, the Airport signal indicator showed the standard 'full signal' indication. Try as I might I can't get her up and running again.

    Things I've tried:
    1. Turning Airport off and on multiple times.
    2. Resetting the router.
    3. Taking the computer to different free wi-fi locations.
    4. Resetting the PRAM
    5. Renewing the DHCP lease
    6. Running Disk Utility and repairing the permissions.
    7. Re-installing Safari and Firefox from a usb drive.
    8. Connecting with and without Apple's firewall running

    Nothing seems to work. I'm missing something, but for the life of me I can't figure out what it is. Airport shows we're connected, but the web browsers refuse to open.

    Any ideas, suggestions or help? Thank you in advance.
     
    gms238, Dec 3, 2010
    #1
  2. doh123

    doh123 Without ME its just AWESO

    Reputations:
    996
    Messages:
    3,727
    Likes Received:
    1
    Trophy Points:
    106
    anywhere you can plug it in directly without using Airport... just for troubleshooting. If it doesn't work that way either, its most likely a software issue. Its always possible there is a hardware problem, and it just died.
     
    doh123, Dec 3, 2010
    #2