2 Replies Latest reply: Feb 2, 2013 8:42 AM by GRB
GRB Level 1 Level 1 (0 points)

I just replaced an aging Airport with a new TimeCapsule. Installation was fine. MacBook (OS 10.6.8) recognized the TimeCapsule, and started backing things up on TimeMachine.  The backup "timed out". And now, Airport no longer detects TimeCapsule, ALTHOUGH every machine in the house, including my MacBook and my Android phone, are feeding off of the internet via the TimeCapsule.  (On the other hand, one of the syncing functions between my phone and the computer no longer work). 

 

The TimeCapsule's light is "green", and has never strayed from that.

 

In addition, my wife's MacBook Air DOES see the TimeCapsule (including the "Data" file from my original attempt to backup my computer -- we've not tried enabling Time Machine on her computer yet).

 

I'm stumped and frustrated!  Any ideas?


MacBook (13-inch), Mac OS X (10.6.8)
  • LaPastenague Level 8 Level 8 (44,315 points)

    Restart the TC.. it is buggy..

    You will need to do this occasionally.

     

    Is it working in bridge or main router in the network?

     

    It will help if you do a few things.

     

    Use SMB names.. short no spaces, pure alphanumeric.

    Use WPA2 Personal security.

    Use fixed radio channels.. change it to manual and change the 2.4ghz to 11, 6, or 1.. try them in that order.. stick with what works the best.

     

    There are a few other things that might help but cannot totally fix it.

     

    Unfortunately the latest TC cannot revert firmware to a version that matches your 10.6.8 computer.. but it will match Lion or Mountain Lion which is probably on the air.

  • GRB Level 1 Level 1 (0 points)

    By restart, I assumed you meant, "unplug and replug".  Did that.  No difference.

     

    It is the main router.

     

    So I reaccessed the TimeCapsule through my wife's Mtn Lion computer, changed the name of the Base Station (removed a space), and then changed the radio channel to "11".

     

    Once everything restarted, I was able to access again via my MacBook 10.6.8.

     

    So, for the time being, all is well!

     

    Thanks!