This discussion is archived
27528 Views 4 Replies Latest reply: Oct 12, 2008 9:24 PM by Carroll Morgan
Currently Being ModeratedMar 16, 2008 2:07 AM (in response to ronch)Hei
I see your point, but you sure have another Time Machine backup disc on a safe place outside your home? I looked in the manula which tells you the is a reset button
30 Chapter 4 Tips and Troubleshooting
If Your Time Capsule Isn’t Responding
Try unplugging it and plugging it back in.
If your Time Capsule stops responding completely, you may need to reset it to the
factory default settings.
Important: This erases all of the current settings and resets them to the settings that
came with your Time Capsule.
To return your Time Capsule to the factory settings:
m Use something pointed to press and hold the reset button until the status light flashes
quickly (about 5 seconds).
Your Time Capsule resets with the following settings:
Â Your Time Capsule receives its IP address using DHCP.
Â The network name is reset to Apple Network XXXXXX (where XXXXXX is replaced
with the last six digits of the AirPort ID).
Â The Time Capsule password is reset to public.
If your Time Capsule still isn’t responding, try the following:
1Unplug your Time Capsule.
2Use something pointed to press and hold the reset button while you plug in your Time
Capsule.Mac book, Mac OS X (10.5.1)
Currently Being ModeratedMar 16, 2008 1:47 PM (in response to niehanse)I dont want to reset it to default settings. I am talking about resetting it so it re-connects to the PPOE connection as ALL routers on the market occasionally drop and this is the procedure to reconnect. I can't believe this but since I posted this question last night, today a client has called me and screwed up his time capsule because the internet dropped and he had to pull the plug to restart it. Now his time machine wont back up any more. He gets an error because just as I had guessed, time machine was probably in mid backup when he pulled the plug as it usually is backing up hourly on an active users machine. EXACTLY what I was afraid of. I am afraid every time capsule will have this issue rendering them useless or dangerous to use if you really want a true backup.
Message was edited by: ronchMacBook Pro, Mac OS X (10.4.6), 2.16 Duo
Currently Being ModeratedMar 21, 2008 1:20 PM (in response to ronch)Hey, folks...
How about a reset function that reverts the unit to pre-7.3.1 firmware?
7.3.1 bricked my TC...on 10.4, 10.5, XP SP2 and Vista machines.
Since 7.3.1, only 10.5 sees it during setup config...then loses it by the end of the config process saying it can't be found. Windows boxes give me an error 6752 (or 6753?) when i try to configure find the TC by 'Configure other.'
Apple support was of no help at all, and even told me that they don't support problems UNLESS you're using the TC as a wireless base station connected to your modem/ISP. Funny. It was part of my mixed wireless network for a week and a half and worked beautifully (until 7.3.1). AND the Apple website touts the fact that it SHOULD join an existing wireless network--but tech doesn't support it.
Anyone have any ideas re: reverting the TC back to previous firmware? (I've tried the Option/Check for updates trick--it still won't install the previous firmware.)
Otherwise, anyone want a pretty white brick for $300?Many, Mac OS X (10.5.2), Have two flavors of Windows and OS X
Currently Being ModeratedOct 12, 2008 9:24 PM (in response to ronch)In contrast to the above report, I have done this today (pressing and holding reset button) without losing the backups; all that was reset were the network connections. Being interrupted in the middle of a backup "should not" lose the backup structure; the current (partial) backup should simply be thrown away the next time around... though nothing is certain in this world.
Nevertheless there have recently been some problems somewhat like those reported in this thread (and others): dropped connections that don't reconnect; very slow backups (12hrs) for none of the well-known good reasons (eg initial backup, or deep traversal).
In my case it seems to be linked with my having manually configured a WDS-style setup with an Extreme as master, the TC as relay and an Express as remote. "Linked" means only that the problems started when I did this, and seem to have gone away since I have undone it, reverting to the wizard-style "extend my network" settings (whatever that means).
All the software/firmware is right up-to-date (as far as I know).2GHz Intel Core 2Duo, 1Gb RAM, 80Gb HD, Mac OS X (10.5.5), No hardware mods/extras.