Issues with Time Capsule- Dropping connection daily
I own a 1TB Time Capsule and use it to store backups and my iTunes library. I have a large library, and I wanted to have a dedicated drive to store all of my songs so they could be accessed by both my PC and MacBook, so I was pointing in this direction at the Apple Store.
When trying to move files over to the TC from my Macbook, my Macbook will often freeze, and the TC can no longer be found, along with my wireless network. The light remains green, but it is unusable unless it is unplugged from the wall and plugged back in. This has happened daily for the past few weeks, but today has happened 5 times in the past hour.
It most commonly happens when I am adding songs to my iTunes Library, both from CDs and from files. It should be noted that, when the TC goes down, I also can't access the internet on my PC, which has an ethernet cord from my TC plugged in.
I'd appreciate any help whatsoever - this is starting to get very irritating.
Thanks!
Hi I had similar problems. I moved houses got my own cable modem and tried to use the TC as my wireless, as i had it in my other home. The connection would drop constantly and i was unable to use the TC as a wireless device, it would also freeze my computer (mac book Pro). After asking everyone for help i found that when i moved the TC next to the cable modem in the garage it all worked. Apparently the ethernet cable that ran from the garage to the living room was only using 4 of the 8 pins and thus was dropping the connection. i am now connected directly from the modem to the tc and it has not failed yet (cross my fingers). After all this was suppose to be wireless and thus i don't need to have it right next to my computer. The signal is strong and it has not caused any problems. I didn't mess with the settings after i did a hard reset on the TC. So far so good. hopes this helps.
Similar Messages
-
DNS Issues with Time Capsule - DNS Proxy periodically dies
hi all .... looking for some suggestions
I have a time capsule 1TB, connected to a linksys adsl modem in bridge mode, with the TC acting as DHCP server for my local clients. In the PPPoE settings I also enter the primary and secondary addresses for DNS that my ISP supplied.
I am able to successfully connect to the internet, and all clients successfully pick up an IP address, and each client picks up the TC as the DNS proxy. Everything works perfectly as it should.
Usually once per day, there seems to be a slight hickup with the internet connection (hard to tell whether I am losing the PPPoE or some other issue). When this happens, the PPPoE connection remains active, as I am able to access anything on the internet from an IP level. However, the DNS proxy service on the TC seems to die and as a result, all internet browsing fails. If I reboot the TC, everything comes back to normal. If I dont reboot, the only way to get browsing working is to manually enter the DNS IP address from ISP into the client PCs. However, this is a manual fix that I should not have to perform.
Looking for advice and guidance. Seems like a bug but I cant tell. If I was able to set the DHCP server to pass out the ISP supplied addresses that would also work, but I cant.Just got off the phone with support for this very same problem. DNS Proxy is definitely dying in the TC, looks like a firmware issue to me.
This is the 3rd TC I'm on. First was a 500GB, had this problem, replaced it under warranty at Apple's direction, replacement did the same, just upgraded this weekend to 1GB, and same issue still. All on 7.3.2 firmware.
TC 1TB, PPPoE to my ISP, ISP's DNS Servers listed in the PPPoE config in the TC.
When a host gets DHCP from the TC the only DNS returned is the TC itself, since it proxies the ISP DNS servers.
Once every day or two, the DNS proxy dies. local network works, and I can add my ISP's DNS addresses in my host config and I have DNS again, but this is definitely something dying in the DNS proxy in the TC.
Just for kicks trying to switch from my ISP's DNS servers to OpenDNS now since someone said that worked for them, but I am not hopeful... I don't see this as a host DNS issues at all.
The dead proxy is very clear:
$ nslookup apple.com. 192.168.1.1 # that's the TC
Server: 192.168.1.1
Address: 192.168.1.1#53
** server can't find apple.com: SERVFAIL
$ nslookup apple.com. 208.67.222.222 # that's OpenDNS
Server: 208.67.222.222
Address: 208.67.222.222#53
Non-authoritative answer:
Name: apple.com
Address: 17.149.160.49
I replaced a linksys router with the TC and am kind of unhappy that a $500 router dies every couple of days. My cheapo Linksys router never needed to be restarted, it only ever got rebooted once every year or so when the house lost power long enough for the UPS to run out of battery.
Help us out here Apple, I replaced a $50 router with a $500 because I like the flavor of your kool aid, and this thing dies every day or two. Even if you can't fix why the proxy is dying every couple of days, can you please at least update the firmware to maybe restart the proxy if it quits working? -
Issue with AFP server dropping connections on 10.8.5 server 2.2.2
We are having issues with users getting dropped from their AFP server shares.
These issues did not start happening until we upgraded to 10.8.5 and server 2.2.2
the first symptoms were an occasional user would lose his / her active connection while copying files. They were unable to disconnect from the network shares without physically disconnecting the LAN or disabling the network on their system. Once the connection was removed they could reconnect to the network and establish their AFP shares again.
However this his escalated to every user losing connections to their AFP shares at the same time.
The server has no AFP error in the AFP error log however we are getting diskutil crash reports at around the same time. (See Below)
The server has
smalltree 1x6 8254 with latest drivers supporting a LACP bonded 6 pair connecting to an edgecore (LACP configured)switch.
small tree 10Gb card directly connected to an edit station.
onboard ethernet connected to switch in support of DHCP & DNS. (previous version of server would not see the bonded pair)
Two Accusys A12S2's
(we did not have this dropping connection issue before the upgrade to server 2.2.2 and OSX 10.8.5)
Users connected to any network connection to the server appear to be affected when the AFP shares are disconnected. Direcet connect, onboard ethernet port and Bonded pair connections)
diskutil verifies all shared drives appear to be ok. (All Green)
SYSTEM LOG
Feb 23 11:15:44 doghouse.local diskutil[1067]: -[__NSCFConstantString getBytes:length:]: unrecognized selector sent to instance 0x7fff7628bbe8
Feb 23 11:15:44 doghouse.local diskutil[1067]: *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[__NSCFConstantString getBytes:length:]: unrecognized selector sent to instance 0x7fff7628bbe8'
*** First throw call stack:
0 CoreFoundation 0x00007fff91b2bb06 __exceptionPreprocess + 198
1 libobjc.A.dylib 0x00007fff901403f0 objc_exception_throw + 43
2 CoreFoundation 0x00007fff91bc240a -[NSObject(NSObject) doesNotRecognizeSelector:] + 186
3 CoreFoundation 0x00007fff91b1a02e ___forwarding___ + 414
4 CoreFoundation 0x00007fff91b19e18 _CF_forwarding_prep_0 + 232
5 diskutil 0x000000010c1eb550 diskutil + 83280
6 diskutil 0x000000010c1ea0af diskutil + 77999
7 diskutil 0x000000010c1e7abe diskutil + 68286
8 diskutil 0x000000010c1dd0ef diskutil + 24815
9 diskutil 0x000000010c1e5161 diskutil + 57697
10 Foundation 0x00007fff8d29dd05 __NSFireDelayedPerform + 358
11 CoreFoundation 0x00007fff91ae8804 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 20
12 CoreFoundation 0x00007fff91ae831d __CFRunLoopDoTimer + 557
13 CoreFoundation 0x00007fff91acdad9 __CFRunLoopRun + 1529
14 CoreFoundation 0x00007fff91acd0e2 CFRunLoopRunSpecific + 290
15 Foundation 0x00007fff8d2c57ee -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 268
16 Foundation 0x00007fff8d25e1aa -[NSRunLoop(NSRunLoop) run] + 74
17 diskutil 0x000000010c1e5126 diskutil + 57638
18 diskutil 0x000000010c1e51cd diskutil + 57805
19 libdyld.dylib 0x00007fff86bf87e1 start + 0
Feb 23 11:15:44 doghouse.local ReportCrash[1064]: Saved crash report for diskutil[1061] version 680 to /Library/Logs/DiagnosticReports/diskutil_2014-02-23-111544_doghouse.crash
Feb 23 11:15:44 doghouse.local ReportCrash[1064]: Removing excessive log: file://localhost/Library/Logs/DiagnosticReports/diskutil_2014-02-22-164711_dogh ouse.crash
Feb 23 11:15:44 doghouse.local ReportCrash[1064]: failed looking up LS service ( scCreateSystemService returned MACH_PORT_NULL, called from SetupCoreApplicationServicesCommunicationPort, so using client-side NULL calls.
Feb 23 11:15:44 doghouse.local ReportCrash[1064]: LaunchServices/5123589: Unable to lookup coreservices session port for session 0x186a0 uid=0 euid=0
Feb 23 11:15:44 doghouse.local ReportCrash[1064]: failed looking up LS service ( scCreateSystemService returned MACH_PORT_NULL, called from SetupCoreApplicationServicesCommunicationPort, so using client-side NULL calls.
Feb 23 11:15:44 doghouse.local ReportCrash[1064]: LaunchServices/5123589: Unable to lookup coreservices session port for session 0x186a0 uid=0 euid=0
Feb 23 11:15:44 doghouse.local ReportCrash[1064]: failed looking up LS service ( scCreateSystemService returned MACH_PORT_NULL, called from SetupCoreApplicationServicesCommunicationPort, so using client-side NULL calls.
Feb 23 11:15:44 doghouse.local ReportCrash[1064]: LaunchServices/5123589: Unable to lookup coreservices session port for session 0x186a0 uid=0 euid=0
Feb 23 11:15:44 doghouse.local ReportCrash[1064]: failed looking up LS service ( scCreateSystemService returned MACH_PORT_NULL, called from SetupCoreApplicationServicesCommunicationPort, so using client-side NULL calls.
Feb 23 11:15:44 doghouse.local ReportCrash[1064]: LaunchServices/5123589: Unable to lookup coreservices session port for session 0x186a0 uid=0 euid=0
Feb 23 11:15:44 doghouse.local ReportCrash[1064]: failed looking up LS service ( scCreateSystemService returned MACH_PORT_NULL, called from SetupCoreApplicationServicesCommunicationPort, so using client-side NULL calls.
Feb 23 11:15:44 doghouse.local ReportCrash[1064]: LaunchServices/5123589: Unable to lookup coreservices session port for session 0x186a0 uid=0 euid=0
Feb 23 11:15:44 doghouse.local diskutil[1071]: -[__NSCFConstantString getBytes:length:]: unrecognized selector sent to instance 0x7fff7628bbe8
Feb 23 11:15:44 doghouse.local ReportCrash[1064]: Saved crash report for diskutil[1067] version 680 to /Library/Logs/DiagnosticReports/diskutil_2014-02-23-111544-1_doghouse.crash
Feb 23 11:15:44 doghouse.local diskutil[1071]: *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[__NSCFConstantString getBytes:length:]: unrecognized selector sent to instance 0x7fff7628bbe8'
*** First throw call stack:
0 CoreFoundation 0x00007fff91b2bb06 __exceptionPreprocess + 198
1 libobjc.A.dylib 0x00007fff901403f0 objc_exception_throw + 43
2 CoreFoundation 0x00007fff91bc240a -[NSObject(NSObject) doesNotRecognizeSelector:] + 186
3 CoreFoundation 0x00007fff91b1a02e ___forwarding___ + 414
4 CoreFoundation 0x00007fff91b19e18 _CF_forwarding_prep_0 + 232
5 diskutil 0x0000000100e49550 diskutil + 83280
6 diskutil 0x0000000100e480af diskutil + 77999
7 diskutil 0x0000000100e45abe diskutil + 68286
8 diskutil 0x0000000100e3b0ef diskutil + 24815
9 diskutil 0x0000000100e43161 diskutil + 57697
10 Foundation 0x00007fff8d29dd05 __NSFireDelayedPerform + 358
11 CoreFoundation 0x00007fff91ae8804 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 20
12 CoreFoundation 0x00007fff91ae831d __CFRunLoopDoTimer + 557
13 CoreFoundation 0x00007fff91acdad9 __CFRunLoopRun + 1529
14 CoreFoundation 0x00007fff91acd0e2 CFRunLoopRunSpecific + 290
15 Foundation 0x00007fff8d2c57ee -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 268
16 Foundation 0x00007fff8d25e1aa -[NSRunLoop(NSRunLoop) run] + 74
17 diskutil 0x0000000100e43126 diskutil + 57638
18 diskutil 0x0000000100e431cd diskutil + 57805
19 libdyld.dylib 0x00007fff86bf87e1 start + 0
Feb 23 11:15:44 doghouse.local ReportCrash[1064]: Removing excessive log: file://localhost/Library/Logs/DiagnosticReports/diskutil_2014-02-22-164712_dogh ouse.crash
Feb 23 11:15:44 doghouse.local ReportCrash[1064]: failed looking up LS service ( scCreateSystemService returned MACH_PORT_NULL, called from SetupCoreApplicationServicesCommunicationPort, so using client-side NULL calls.
Feb 23 11:15:44 doghouse.local ReportCrash[1064]: LaunchServices/5123589: Unable to lookup coreservices session port for session 0x186a0 uid=0 euid=0
Feb 23 11:15:44 doghouse.local ReportCrash[1064]: failed looking up LS service ( scCreateSystemService returned MACH_PORT_NULL, called from SetupCoreApplicationServicesCommunicationPort, so using client-side NULL calls.
Feb 23 11:15:44 doghouse.local ReportCrash[1064]: LaunchServices/5123589: Unable to lookup coreservices session port for session 0x186a0 uid=0 euid=0
Feb 23 11:15:44 doghouse.local ReportCrash[1064]: failed looking up LS service ( scCreateSystemService returned MACH_PORT_NULL, called from SetupCoreApplicationServicesCommunicationPort, so using client-side NULL calls.
Feb 23 11:15:44 doghouse.local ReportCrash[1064]: LaunchServices/5123589: Unable to lookup coreservices session port for session 0x186a0 uid=0 euid=0
Feb 23 11:15:44 doghouse.local ReportCrash[1064]: failed looking up LS service ( scCreateSystemService returned MACH_PORT_NULL, called from SetupCoreApplicationServicesCommunicationPort, so using client-side NULL calls.
Feb 23 11:15:44 doghouse.local ReportCrash[1064]: LaunchServices/5123589: Unable to lookup coreservices session port for session 0x186a0 uid=0 euid=0
Feb 23 11:15:44 doghouse.local ReportCrash[1064]: failed looking up LS service ( scCreateSystemService returned MACH_PORT_NULL, called from SetupCoreApplicationServicesCommunicationPort, so using client-side NULL calls.
Feb 23 11:15:44 doghouse.local ReportCrash[1064]: LaunchServices/5123589: Unable to lookup coreservices session port for session 0x186a0 uid=0 euid=0
Feb 23 11:15:44 doghouse.local ReportCrash[1064]: Saved crash report for diskutil[1071] version 680 to /Library/Logs/DiagnosticReports/diskutil_2014-02-23-111544-2_doghouse.crash
Feb 23 11:15:44 doghouse.local ReportCrash[1064]: Removing excessive log: file://localhost/Library/Logs/DiagnosticReports/diskutil_2014-02-23-093307_dogh ouse.crash
diskutil crash report
Process: diskutil [1061]
Path: /usr/sbin/diskutil
Identifier: diskutil
Version: 680
Code Type: X86-64 (Native)
Parent Process: sh [1060]
User ID: 0
Date/Time: 2014-02-23 11:15:43.719 -0800
OS Version: Mac OS X 10.8.5 (12F45)
Report Version: 10
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Application Specific Information:
*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[__NSCFConstantString getBytes:length:]: unrecognized selector sent to instance 0x7fff7628bbe8'
terminate called throwing an exception
abort() called
Application Specific Backtrace 1:
0 CoreFoundation 0x00007fff91b2bb06 __exceptionPreprocess + 198
1 libobjc.A.dylib 0x00007fff901403f0 objc_exception_throw + 43
2 CoreFoundation 0x00007fff91bc240a -[NSObject(NSObject) doesNotRecognizeSelector:] + 186
3 CoreFoundation 0x00007fff91b1a02e ___forwarding___ + 414
4 CoreFoundation 0x00007fff91b19e18 _CF_forwarding_prep_0 + 232
5 diskutil 0x000000010124a550 diskutil + 83280
6 diskutil 0x00000001012490af diskutil + 77999
7 diskutil 0x0000000101246abe diskutil + 68286
8 diskutil 0x000000010123c0ef diskutil + 24815
9 diskutil 0x0000000101244161 diskutil + 57697
10 Foundation 0x00007fff8d29dd05 __NSFireDelayedPerform + 358
11 CoreFoundation 0x00007fff91ae8804 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 20
12 CoreFoundation 0x00007fff91ae831d __CFRunLoopDoTimer + 557
13 CoreFoundation 0x00007fff91acdad9 __CFRunLoopRun + 1529
14 CoreFoundation 0x00007fff91acd0e2 CFRunLoopRunSpecific + 290
15 Foundation 0x00007fff8d2c57ee -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 268
16 Foundation 0x00007fff8d25e1aa -[NSRunLoop(NSRunLoop) run] + 74
17 diskutil 0x0000000101244126 diskutil + 57638
18 diskutil 0x00000001012441cd diskutil + 57805
19 libdyld.dylib 0x00007fff86bf87e1 start + 0
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x00007fff86519212 __pthread_kill + 10
1 libsystem_c.dylib 0x00007fff8a31ab24 pthread_kill + 90
2 libsystem_c.dylib 0x00007fff8a35ef61 abort + 143
3 libc++abi.dylib 0x00007fff85dc39eb abort_message + 257
4 libc++abi.dylib 0x00007fff85dc139a default_terminate() + 28
5 libobjc.A.dylib 0x00007fff90140873 _objc_terminate() + 91
6 libc++abi.dylib 0x00007fff85dc13c9 safe_handler_caller(void (*)()) + 8
7 libc++abi.dylib 0x00007fff85dc1424 std::terminate() + 16
8 libc++abi.dylib 0x00007fff85dc261b __cxa_rethrow + 85
9 libobjc.A.dylib 0x00007fff90140575 objc_exception_rethrow + 40
10 com.apple.CoreFoundation 0x00007fff91acd146 CFRunLoopRunSpecific + 390
11 com.apple.Foundation 0x00007fff8d2c57ee -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 268
12 com.apple.Foundation 0x00007fff8d25e1aa -[NSRunLoop(NSRunLoop) run] + 74
13 diskutil 0x0000000101244126 0x101236000 + 57638
14 diskutil 0x00000001012441cd 0x101236000 + 57805
15 libdyld.dylib 0x00007fff86bf87e1 start + 1
Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0 libsystem_kernel.dylib 0x00007fff86519d16 kevent + 10
1 libdispatch.dylib 0x00007fff8a0dddea _dispatch_mgr_invoke + 883
2 libdispatch.dylib 0x00007fff8a0dd9ee _dispatch_mgr_thread + 54
Thread 2:
0 libsystem_kernel.dylib 0x00007fff865196d6 __workq_kernreturn + 10
1 libsystem_c.dylib 0x00007fff8a31bf1c _pthread_workq_return + 25
2 libsystem_c.dylib 0x00007fff8a31bce3 _pthread_wqthread + 412
3 libsystem_c.dylib 0x00007fff8a306191 start_wqthread + 13
Thread 3:
0 libsystem_kernel.dylib 0x00007fff865196d6 __workq_kernreturn + 10
1 libsystem_c.dylib 0x00007fff8a31bf1c _pthread_workq_return + 25
2 libsystem_c.dylib 0x00007fff8a31bce3 _pthread_wqthread + 412
3 libsystem_c.dylib 0x00007fff8a306191 start_wqthread + 13
Thread 4:
0 libsystem_kernel.dylib 0x00007fff865196d6 __workq_kernreturn + 10
1 libsystem_c.dylib 0x00007fff8a31bf1c _pthread_workq_return + 25
2 libsystem_c.dylib 0x00007fff8a31bce3 _pthread_wqthread + 412
3 libsystem_c.dylib 0x00007fff8a306191 start_wqthread + 13
Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x0000000000000000 rbx: 0x0000000000000006 rcx: 0x00007fff5e9c9ad8 rdx: 0x0000000000000000
rdi: 0x0000000000000707 rsi: 0x0000000000000006 rbp: 0x00007fff5e9c9b00 rsp: 0x00007fff5e9c9ad8
r8: 0x00007fff764be278 r9: 0x00007fff5e9c9ae0 r10: 0x0000000020000000 r11: 0x0000000000000206
r12: 0x00007fff5e9c9c60 r13: 0x0000000000000001 r14: 0x00007fff764bf180 r15: 0x00007fff5e9c9b40
rip: 0x00007fff86519212 rfl: 0x0000000000000206 cr2: 0x00007fff764b7ff0
Logical CPU: 0
Binary Images:
0x101236000 - 0x10126efff diskutil (680) <47174BB8-7EAC-39F7-96F7-99FE93C9CAF3> /usr/sbin/diskutil
0x7fff60e36000 - 0x7fff60e6a93f dyld (210.2.3) <6900F2BA-DB48-3B78-B668-58FC0CF6BCB8> /usr/lib/dyld
0x7fff85d6f000 - 0x7fff85d6ffff libkeymgr.dylib (25) <CC9E3394-BE16-397F-926B-E579B60EE429> /usr/lib/system/libkeymgr.dylib
0x7fff85dc0000 - 0x7fff85de5ff7 libc++abi.dylib (26) <D86169F3-9F31-377A-9AF3-DB17142052E4> /usr/lib/libc++abi.dylib
0x7fff85de6000 - 0x7fff85e4eff7 libc++.1.dylib (65.1) <20E31B90-19B9-3C2A-A9EB-474E08F9FE05> /usr/lib/libc++.1.dylib
0x7fff85e4f000 - 0x7fff85ef5ff7 com.apple.CoreServices.OSServices (557.6 - 557.6) <FFDDD2D8-690D-388F-A48F-4750A792D2CD> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServi ces.framework/Versions/A/OSServices
0x7fff85f54000 - 0x7fff85f62ff7 libkxld.dylib (2050.48.12) <B8F7ED1F-CF84-3777-9183-0A1C513DF81F> /usr/lib/system/libkxld.dylib
0x7fff861de000 - 0x7fff86353ff7 com.apple.CFNetwork (596.5 - 596.5) <22372475-6EF4-3A04-83FC-C061FE4717B3> /System/Library/Frameworks/CFNetwork.framework/Versions/A/CFNetwork
0x7fff86354000 - 0x7fff863d5fff com.apple.Metadata (10.7.0 - 707.12) <69E3EEF7-8B7B-3652-8320-B8E885370E56> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadat a.framework/Versions/A/Metadata
0x7fff86468000 - 0x7fff86470ff7 libsystem_dnssd.dylib (379.38.1) <BDCB8566-0189-34C0-9634-35ABD3EFE25B> /usr/lib/system/libsystem_dnssd.dylib
0x7fff86499000 - 0x7fff86506ff7 com.apple.datadetectorscore (4.1 - 269.3) <5775F0DB-87D6-310D-8B03-E2AD729EFB28> /System/Library/PrivateFrameworks/DataDetectorsCore.framework/Versions/A/DataDe tectorsCore
0x7fff86507000 - 0x7fff86522ff7 libsystem_kernel.dylib (2050.48.12) <4B7993C3-F62D-3AC1-AF92-414A0D6EED5E> /usr/lib/system/libsystem_kernel.dylib
0x7fff865b1000 - 0x7fff865b2ff7 libremovefile.dylib (23.2) <6763BC8E-18B8-3AD9-8FFA-B43713A7264F> /usr/lib/system/libremovefile.dylib
0x7fff86764000 - 0x7fff86769fff libcache.dylib (57) <65187C6E-3FBF-3EB8-A1AA-389445E2984D> /usr/lib/system/libcache.dylib
0x7fff86784000 - 0x7fff86785fff libDiagnosticMessagesClient.dylib (8) <8548E0DC-0D2F-30B6-B045-FE8A038E76D8> /usr/lib/libDiagnosticMessagesClient.dylib
0x7fff86bf6000 - 0x7fff86bf9ff7 libdyld.dylib (210.2.3) <F59367C9-C110-382B-A695-9035A6DD387E> /usr/lib/system/libdyld.dylib
0x7fff8715b000 - 0x7fff8715bfff com.apple.vecLib (3.8 - vecLib 3.8) <6CBBFDC4-415C-3910-9558-B67176447789> /System/Library/Frameworks/vecLib.framework/Versions/A/vecLib
0x7fff871a8000 - 0x7fff87235ff7 com.apple.SearchKit (1.4.0 - 1.4.0) <C7F43889-F8BF-3CB9-AD66-11AEFCBCEDE7> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchK it.framework/Versions/A/SearchKit
0x7fff87236000 - 0x7fff87243fff libbz2.1.0.dylib (29) <CE9785E8-B535-3504-B392-82F0064D9AF2> /usr/lib/libbz2.1.0.dylib
0x7fff872d9000 - 0x7fff87373fff libvMisc.dylib (380.10) <A7F12764-A94C-36EB-88E0-F826F5AF55B4> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libvMisc.dylib
0x7fff87455000 - 0x7fff87455fff com.apple.CoreServices (57 - 57) <9DD44CB0-C644-35C3-8F57-0B41B3EC147D> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
0x7fff87874000 - 0x7fff87947ff7 com.apple.DiscRecording (7.0 - 7000.2.4) <6DCA9535-E276-3D77-BEB3-296B537AA6BB> /System/Library/Frameworks/DiscRecording.framework/Versions/A/DiscRecording
0x7fff879ab000 - 0x7fff879aefff libutil.dylib (30) <EF3340B2-9A53-3D5E-B9B4-BDB5EEECC178> /usr/lib/libutil.dylib
0x7fff87da3000 - 0x7fff87da5ff7 com.apple.EFILogin (2.0 - 2) <51A470D7-1F72-3369-AF0F-AD2340B42C12> /System/Library/PrivateFrameworks/EFILogin.framework/Versions/A/EFILogin
0x7fff880b1000 - 0x7fff880e9fff libncurses.5.4.dylib (37.3) <68D5B5F5-8252-3F1E-AFF1-C6AFE145DBC1> /usr/lib/libncurses.5.4.dylib
0x7fff881ed000 - 0x7fff881faff7 com.apple.NetAuth (4.0 - 4.0) <F5BC7D7D-AF28-3C83-A674-DADA48FF7810> /System/Library/PrivateFrameworks/NetAuth.framework/Versions/A/NetAuth
0x7fff88571000 - 0x7fff8859fff7 libsystem_m.dylib (3022.6) <B434BE5C-25AB-3EBD-BAA7-5304B34E3441> /usr/lib/system/libsystem_m.dylib
0x7fff887e7000 - 0x7fff887e8ff7 libSystem.B.dylib (169.3) <5ED23C27-47AF-3C93-984A-172751CF745A> /usr/lib/libSystem.B.dylib
0x7fff887e9000 - 0x7fff8883aff7 com.apple.SystemConfiguration (1.12.2 - 1.12.2) <581BF463-C15A-363B-999A-E830222FA925> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfi guration
0x7fff8883b000 - 0x7fff88b52ff7 com.apple.CoreServices.CarbonCore (1037.6 - 1037.6) <1E567A52-677F-3168-979F-5FBB0818D52B> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/CarbonCore
0x7fff88b53000 - 0x7fff88b54ff7 libsystem_sandbox.dylib (220.3) <B739DA63-B675-387A-AD84-412A651143C0> /usr/lib/system/libsystem_sandbox.dylib
0x7fff88be0000 - 0x7fff88bf3ff7 libbsm.0.dylib (32) <F497D3CE-40D9-3551-84B4-3D5E39600737> /usr/lib/libbsm.0.dylib
0x7fff88dd0000 - 0x7fff88dd1fff libsystem_blocks.dylib (59) <D92DCBC3-541C-37BD-AADE-ACC75A0C59C8> /usr/lib/system/libsystem_blocks.dylib
0x7fff892df000 - 0x7fff892e5fff libmacho.dylib (829) <BF332AD9-E89F-387E-92A4-6E1AB74BD4D9> /usr/lib/system/libmacho.dylib
0x7fff892e6000 - 0x7fff89335ff7 libcorecrypto.dylib (106.2) <CE0C29A3-C420-339B-ADAA-52F4683233CC> /usr/lib/system/libcorecrypto.dylib
0x7fff89336000 - 0x7fff89536fff libicucore.A.dylib (491.11.3) <5783D305-04E8-3D17-94F7-1CEAFA975240> /usr/lib/libicucore.A.dylib
0x7fff89537000 - 0x7fff89537fff libOpenScriptingUtil.dylib (148.3) <F8681222-0969-3B10-8BCE-C55A4B9C520C> /usr/lib/libOpenScriptingUtil.dylib
0x7fff89538000 - 0x7fff89581ff7 com.apple.DiskManagement (5.3.1 - 680) <5438A1FF-B92C-3D28-A8E4-FB41F03144C2> /System/Library/PrivateFrameworks/DiskManagement.framework/Versions/A/DiskManag ement
0x7fff89589000 - 0x7fff895abff7 libxpc.dylib (140.43) <70BC645B-6952-3264-930C-C835010CCEF9> /usr/lib/system/libxpc.dylib
0x7fff895b6000 - 0x7fff895cdfff com.apple.CFOpenDirectory (10.8 - 151.10) <F7AD9844-559A-366E-8192-BB4FCF9EE7A3> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpen Directory.framework/Versions/A/CFOpenDirectory
0x7fff895ce000 - 0x7fff895d9fff libsystem_notify.dylib (98.5) <C49275CC-835A-3207-AFBA-8C01374927B6> /usr/lib/system/libsystem_notify.dylib
0x7fff8960f000 - 0x7fff89614fff libcompiler_rt.dylib (30) <08F8731D-5961-39F1-AD00-4590321D24A9> /usr/lib/system/libcompiler_rt.dylib
0x7fff899f3000 - 0x7fff89a3fff7 libauto.dylib (185.4) <AD5A4CE7-CB53-313C-9FAE-673303CC2D35> /usr/lib/libauto.dylib
0x7fff89b9a000 - 0x7fff89b9cff7 libunc.dylib (25) <92805328-CD36-34FF-9436-571AB0485072> /usr/lib/system/libunc.dylib
0x7fff89bd8000 - 0x7fff89c09ff7 com.apple.DictionaryServices (1.2 - 184.4) <FB0540FF-5034-3591-A28D-6887FBC220F7> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Diction aryServices.framework/Versions/A/DictionaryServices
0x7fff8a01f000 - 0x7fff8a0afff7 libCoreStorage.dylib (296.18.2) <2FFB6BCA-3033-3AC1-BCE4-ED102DCBECD5> /usr/lib/libCoreStorage.dylib
0x7fff8a0d9000 - 0x7fff8a0eeff7 libdispatch.dylib (228.23) <D26996BF-FC57-39EB-8829-F63585561E09> /usr/lib/system/libdispatch.dylib
0x7fff8a0ef000 - 0x7fff8a11afff libxslt.1.dylib (11.3) <441776B8-9130-3893-956F-39C85FFA644F> /usr/lib/libxslt.1.dylib
0x7fff8a2e9000 - 0x7fff8a2f3fff libcsfde.dylib (296.18.2) <08092C5B-2171-3C1D-A98F-CF499A315DDC> /usr/lib/libcsfde.dylib
0x7fff8a305000 - 0x7fff8a3d1ff7 libsystem_c.dylib (825.40.1) <543B05AE-CFA5-3EFE-8E58-77225411BA6B> /usr/lib/system/libsystem_c.dylib
0x7fff8a5c9000 - 0x7fff8a628fff com.apple.AE (645.6 - 645.6) <44F403C1-660A-3543-AB9C-3902E02F936F> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.fram ework/Versions/A/AE
0x7fff8a679000 - 0x7fff8a776fff libsqlite3.dylib (138.1) <ADE9CB98-D77D-300C-A32A-556B7440769F> /usr/lib/libsqlite3.dylib
0x7fff8a8e3000 - 0x7fff8a9e0ff7 libxml2.2.dylib (22.3) <47B09CB2-C636-3024-8B55-6040F7829B4C> /usr/lib/libxml2.2.dylib
0x7fff8afa9000 - 0x7fff8afdffff libsystem_info.dylib (406.17) <4FFCA242-7F04-365F-87A6-D4EFB89503C1> /usr/lib/system/libsystem_info.dylib
0x7fff8afe6000 - 0x7fff8afeefff liblaunch.dylib (442.26.2) <2F71CAF8-6524-329E-AC56-C506658B4C0C> /usr/lib/system/liblaunch.dylib
0x7fff8b2b7000 - 0x7fff8b368fff com.apple.LaunchServices (539.9 - 539.9) <07FC6766-778E-3479-8F28-D2C9917E1DD1> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchS ervices.framework/Versions/A/LaunchServices
0x7fff8b3bc000 - 0x7fff8b3c0ff7 com.apple.TCC (1.0 - 1) <F2F3B753-FC73-3543-8BBE-859FDBB4D6A6> /System/Library/PrivateFrameworks/TCC.framework/Versions/A/TCC
0x7fff8c051000 - 0x7fff8c0b9fff libvDSP.dylib (380.10) <3CA154A3-1BE5-3CF4-BE48-F0A719A963BB> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libvDSP.dylib
0x7fff8c15b000 - 0x7fff8c17cff7 libCRFSuite.dylib (33) <736ABE58-8DED-3289-A042-C25AF7AE5B23> /usr/lib/libCRFSuite.dylib
0x7fff8c1bc000 - 0x7fff8c1c2ff7 libunwind.dylib (35.1) <21703D36-2DAB-3D8B-8442-EAAB23C060D3> /usr/lib/system/libunwind.dylib
0x7fff8c58d000 - 0x7fff8c984fff libLAPACK.dylib (1073.4) <D632EC8B-2BA0-3853-800A-20DA00A1091C> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libLAPACK.dylib
0x7fff8c985000 - 0x7fff8c993ff7 libsystem_network.dylib (77.10) <0D99F24E-56FE-380F-B81B-4A4C630EE587> /usr/lib/system/libsystem_network.dylib
0x7fff8c994000 - 0x7fff8c99bfff libcopyfile.dylib (89) <876573D0-E907-3566-A108-577EAD1B6182> /usr/lib/system/libcopyfile.dylib
0x7fff8c99c000 - 0x7fff8c9aafff libcommonCrypto.dylib (60027) <BAAFE0C9-BB86-3CA7-88C0-E3CBA98DA06F> /usr/lib/system/libcommonCrypto.dylib
0x7fff8ccbc000 - 0x7fff8cf8dff7 com.apple.security (7.0 - 55179.13) <F428E306-C407-3B55-BA82-E58755E8A76F> /System/Library/Frameworks/Security.framework/Versions/A/Security
0x7fff8d22a000 - 0x7fff8d589fff com.apple.Foundation (6.8 - 945.18) <1D7E58E6-FA3A-3CE8-AC85-B9D06B8C0AA0> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
0x7fff8d939000 - 0x7fff8d950fff com.apple.GenerationalStorage (1.1 - 132.3) <FD4A84B3-13A8-3C60-A59E-25A361447A17> /System/Library/PrivateFrameworks/GenerationalStorage.framework/Versions/A/Gene rationalStorage
0x7fff8d951000 - 0x7fff8d952fff liblangid.dylib (116) <864C409D-D56B-383E-9B44-A435A47F2346> /usr/lib/liblangid.dylib
0x7fff8d953000 - 0x7fff8d95afff com.apple.NetFS (5.0 - 4.0) <82E24B9A-7742-3DA3-9E99-ED267D98C05E> /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS
0x7fff8d968000 - 0x7fff8d9d1fff libstdc++.6.dylib (56) <EAA2B53E-EADE-39CF-A0EF-FB9D4940672A> /usr/lib/libstdc++.6.dylib
0x7fff8dbde000 - 0x7fff8dc4cff7 com.apple.framework.IOKit (2.0.1 - 755.42.1) <A90038ED-48F2-3CC9-A042-53A3D7985844> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
0x7fff8e11b000 - 0x7fff8e11dfff libquarantine.dylib (52.1) <143B726E-DF47-37A8-90AA-F059CFD1A2E4> /usr/lib/system/libquarantine.dylib
0x7fff9012f000 - 0x7fff9024792f libobjc.A.dylib (532.2) <90D31928-F48D-3E37-874F-220A51FD9E37> /usr/lib/libobjc.A.dylib
0x7fff91567000 - 0x7fff91568ff7 libdnsinfo.dylib (453.19) <14202FFB-C3CA-3FCC-94B0-14611BF8692D> /usr/lib/system/libdnsinfo.dylib
0x7fff91952000 - 0x7fff919b5fff com.apple.audio.CoreAudio (4.1.2 - 4.1.2) <FEAB83AB-1DE5-3813-BA48-7A7F2374CCF0> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio
0x7fff91a98000 - 0x7fff91c82ff7 com.apple.CoreFoundation (6.8 - 744.19) <0F7403CA-2CB8-3D0A-992B-679701DF27CA> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x7fff91c83000 - 0x7fff91e09fff libBLAS.dylib (1073.4) <C102C0F6-8CB6-3B49-BA6B-2EB61F0B2784> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libBLAS.dylib
0x7fff91e13000 - 0x7fff91e25ff7 libz.1.dylib (43) <2A1551E8-A272-3DE5-B692-955974FE1416> /usr/lib/libz.1.dylib
0x7fff91e76000 - 0x7fff91e7cfff com.apple.DiskArbitration (2.5.2 - 2.5.2) <C713A35A-360E-36CE-AC0A-25C86A3F50CA> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
0x7fff91f14000 - 0x7fff91f54ff7 com.apple.MediaKit (14 - 687) <8AAA8CC3-3ACD-34A5-9E57-9B24AD8AFD4D> /System/Library/PrivateFrameworks/MediaKit.framework/Versions/A/MediaKit
0x7fff92028000 - 0x7fff92037ff7 libxar.1.dylib (105) <370ED355-E516-311E-BAFD-D80633A84BE1> /usr/lib/libxar.1.dylib
0x7fff921bd000 - 0x7fff921c1fff libpam.2.dylib (20) <C8F45864-5B58-3237-87E1-2C258A1D73B8> /usr/lib/libpam.2.dylib
0x7fff921c2000 - 0x7fff92314fff com.apple.audio.toolbox.AudioToolbox (1.9.2 - 1.9.2) <DC5F3D1B-036A-37DE-BC24-7636DC95EA1C> /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox
External Modification Summary:
Calls made by other processes targeting this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by all processes on this machine:
task_for_pid: 240
thread_create: 0
thread_set_state: 0
VM Region Summary:
ReadOnly portion of Libraries: Total=89.5M resident=64.1M(72%) swapped_out_or_unallocated=25.4M(28%)
Writable regions: Total=82.6M written=784K(1%) resident=1340K(2%) swapped_out=0K(0%) unallocated=81.3M(98%)
REGION TYPE VIRTUAL
=========== =======
MALLOC 72.3M
MALLOC guard page 32K
STACK GUARD 56.0M
Stack 10.0M
VM_ALLOCATE 8K
__DATA 3472K
__LINKEDIT 52.1M
__TEXT 37.4M
__UNICODE 544K
mapped file 18.1M
shared memory 12K
=========== =======
TOTAL 250.0MThat kind of crash is usually caused by system corruption. I suggest you reinstall.
-
Time Capsule drops connection with Windows 7 - KNOWN ISSUE
There are several sites posting solutions to this problem (example below).
Solution 1. - revert to older firmware of TC
Solution 2. - change local security policies
ONE PROBLEM THOUGH. I believe ONLY PROFESSIONAL versions of windows have the local policies acceptable. This means all of us using HOME editions are screwed.
*Thread from:*
*http://techsupport.foreverwarm.com/time-capsule-windows*
Windows Vista and Windows 7 cannot see Time Capsule drive
This might be your security settings. Open the Local Security Policy utility:
%windir%\system32\secpol.msc /s
Navigate to Local Policies folder, Security Options view. Find “Network security: LAN Manager authentication level”. If it is set to “Send NTLMv2 response only” change it to “Send LM & NTLM – use NTLMv2 session security if negotiated”.ONE PROBLEM THOUGH. I believe ONLY PROFESSIONAL versions of windows have the local policies acceptable. This means all of us using HOME editions are screwed.
Home Edition users would have to perform a Registry edit as follows:
1. Open registry editor (ref: Start > Search > Enter: regedit)
2. Browse to HKEYLOCALMACHINE\SYSTEM\CurrentControlSet\Control\Lsa
3. Create a new DWORD value with the following properties: NAME = LmCompatibilityLevel & VALUE = 1
4. Restart your PC and try the connection again... -
Connection with Time Capsule dropping out constantly
Hello everyone,
I have a MBP with retina display running on the last version of OSX. I bought two weeks ago a Time Capsule 2TB. The intend of this last buy was to improve the strengh of my wireless connection. This did not happen as I found myself with a WIFI network slower than the one provided by my old modem, which was acquired from my DSL provider two years ago! Anyway, I was not too unhappy with having my TC as it meant that I could access it from anywhere and use it to back my MBP. I also use it to store my iTunes library. However, the wireless connection between my MBP and Time Capsule keeps dropping out. Listening to music is almost impossible and very frustating! Backing up takes forever! I would be happy to blame the distance between my MBP and the TC but that absolutely does not make any sense to me: I run FileBrowser on my IPAD2 and it plays music perfectly well from the same exact same distance. It seems a bit ridiculous to me!
Has anyone encountered the same problem? I am statring my MBP with retina display that I have already brought back to the apple store once!
Thank you for your help!Question,...
Could my issue with connection dropping be because the MBP is trying to swap between 2.4 and 5 ?
Yes, they are designed to switch to the better band automagically.. voodoo black arts .. it does lead to issues.
The TC itself will swap channels automagically if there is interference.. so you have two items.. using voodoo to find the best channel and best band.
If you live in apartment building for instance surrounded by wireless.. the TC could be swapping constantly.
So there is no point.. turn off the auto swapping channels.. and change the 5ghz name to swap band swapping. At least to test.
Locking the TC channels,..do you mean channel 1, 2,3 ?
2.4 ghz has only 3 channels that do not overlap.. so it is useless testing 1,2,3 -- 11.
Test channel 1, 6, 11 pick the best of these.
Using 5ghz there are a greater number of bands.. it has poor range even though it suffers less interference.. so pick a channel near to 40.. I think that is a default.. and pick a high channel like 158.. exactly which doesn't matter.
So your TC is setup.. new name.. TC
Name for 2.4ghz wireless TC24ghz
Name for 5ghz wireless TC5ghz
(hard disk name should also have no spaces.. this is important for later OS like ML).
Set the wireless for each band to a channel.
wpa2 security.
See how it goes.
The fact is the TC could still be faulty or your MBPr.. but it is more likely setup is wrong. Or you live in an area of overwhelming wifi interference. -
Connection timeout issues with Time Capsule
I have a first generation 500 GB Time Capsule, with AT&T Uverse internet service. The device worked fine up until 3 weeks ago, at which time I received a "connection timeout" error when trying to connect from any of the computers in the house. At that time, the computers were showing that the wireless network was available, but I was just unable to connect. I could connect to the device using the ethernet connection, and the wired computer would still successfully backup.
I restarted the Time Capsule, and everything immediately returned to normal. Everything worked fine for about a week, and then the problem occurred again. The issue has been occurring more and more frequently, to the point that it now is only working for several hours before requiring a reset.
Has anybody experienced anything similar to this? Any thoughts on a solution to this?Hi I had similar problems. I moved houses got my own cable modem and tried to use the TC as my wireless, as i had it in my other home. The connection would drop constantly and i was unable to use the TC as a wireless device, it would also freeze my computer (mac book Pro). After asking everyone for help i found that when i moved the TC next to the cable modem in the garage it all worked. Apparently the ethernet cable that ran from the garage to the living room was only using 4 of the 8 pins and thus was dropping the connection. i am now connected directly from the modem to the tc and it has not failed yet (cross my fingers). After all this was suppose to be wireless and thus i don't need to have it right next to my computer. The signal is strong and it has not caused any problems. I didn't mess with the settings after i did a hard reset on the TC. So far so good. hopes this helps.
-
Random Connectivity Issues with Time Capsule
I am having random connectivity issues with my time capsule with my intel based iMac. I don't have any issues with my MacAir, iPads or iPhones... just the iMac. It shows a "good" connection but sometimes... TC won't be able to connect to run a backup or I can't get to the internet. It doesn't appear to be an internet problem as I can get to the internet on other devices. It appears to be a connection issue between the iMAC and the TC. Thoughts or suggestions?
Do a full reset of the iMac.. apparently after the latest Mountain Lion update it can cause issues. I have not needed to try this as I have not seen it myself but I track the treads very closely and this popped up.
http://support.apple.com/kb/ht3964 -
Issues with time capsule back ups when external hard drive is connected/not connected
I have a 2TB Airport Time Capsule (ATC) (tall tower type) purchased a few weeks ago and initially wanted it to back up a Seagate FreeAgent 500Gb external drive (formatted extended journalled) as well as three Macbook Pros. The Seagate has a single partition called Lib and is not used for Timemachine backup; it just contains my iTunes library and lots of scanned and archived documents. I want the Lib folder to be accessible to all three Mac users in the house and I've set up all of the Macs to connect and back up to the ATT. They can all see the 'Lib' folder when it is connected to the ATC.
After a bit of searching on the discussion boards I realise that the ATC will not back up 'Lib' when the Seagate is connected by USB directly and that ATT will back it up if it is connect to my Mac and set not to exclude Lib BUT I am encountering some problems with this scenario when I activate time machine.
When I disconnect the Seagate by using 'disconnect' in the ATC viewer in Finder I shut down the drive before disconnecting the usb and reconnecting to the Macbook Pro just as a precaution. When i connect and then activate back up using Time Machine selecting the ATC data folder, it is showing no previous back ups and never backed up. When I had the Seagate connected to the ATT I was seeing back ups as far as 6th May when I bought the ATC. I know that the Time Machine backups are not on the Seagate as I had to reformat it a few days ago and use Data Rescue 3 when I lost the ability to see any files on it after disconnecting it from the ATC. I saw the 6th May backups in Time Machine before I disconnected the Seagate a few minutes ago so they must be on the ATC - just not showing after the Seagate was disconnected.
Can anyone talk me through what may be happening here and advise on the best way of managing this. I'm already planning to buy another external drive as the Seagate is getting a bit old now and I realise I should have secondary back up. I should just say that the reason for bothering with the shared external drive is so that we can all access the photos and household files over the wireless network using ATT. I would just like it to be backed up with minimal fuss if possible.
Many thanks in anticipation of some help with this
II would fix the problem by simply installing a more flexible backup software. Carbon Copy Cloner costs US40. And it is licensed so you can load it on all the computers in your house.
It can backup the external drive while connected to the TC, although if you are using wireless it will be sure slow.
Including the external drive in your backup with TM, is just messy. It will work.. and although you are not seeing the previous backups, they are there.. but TM cannot see them until it reconnects with the external drive in place. Once it reconnects it will need to deep scan the previous backup.. you are going to find a simple backup takes far longer than you want. It is also difficult to recover from.
See Q5 here http://pondini.org/TM/FAQ.html
And several other comments in Pondini's KB will be helpful to understand. Sadly the guy who wrote it died before Mavericks came on the scene.. but it has more bugs than ever. TM has become less reliable for a lot of people.. and that is not doing any swapping of disks.
TM is honestly great for simple backups of your OS and particularly for incrementals but getting a clone of the disk like your external is far better for your setup.
See http://pondini.org/TM/Clones.html -
HT1218 iPhone 4s connectivity issues with Time Capsule 4th generation
Out of nowhere, my iPhone 4s all of a sudden quit connecting to my Time Capsule's wifi. Have never had any problems until yesterday. Have read multiple forums that say reset your iphone, turn wifi off and then on, forget and then resgn into network, change the channels on wifi from automatic to different channels. Changing the channels worked for about an hour and then I was back to square one. Everything else failed. iMac and MacBook connect without any problems or delays at all. PLEASE HELP?!?!
Your TC replaced what?
Are you extending on 2.4ghz?
There is a chance the TC is lower than the router it replaced.. you may need to get the second Express closer to get a good signal so it can extend properly.. the idea is to have the express in about the centre of signal strength not distance.. use your laptop if you have one with a wireless analysis program like istumbler to find the signal at the TC from say 3M.. at the express 1 and at the express 2. Work out if the signal is too low and move them as appropiate.
Or.. think the arrangement and use something like EOP adapters direct to your office.. they can work hugely better than wireless. (or just as badly.. depending on the house wiring). -
Ethernet Issues with Time Capsule and Airplay
I am running OSX v10.9.2. I have a 3-week old 3TB Time Casule (TC) connected by Ethernet cable to a DSL modem. I broadcast our wireless network from the TC rather than from the DSL modem because of the faster speed that TC provides. My computers (iMac also 3 weeks old) and a Windows laptop are connected to the network via a fibre optic cable LAN. There are also three 2nd generation Airport Express modules which I use to push music around the house.
When I connect my iMac to the WiFi network, I have zero problems reaching Time Capsule, backing up my iMac using Time Machine or pushing music throughout the house.
However, when I switch to Ethernet (my preferred network access), the TC and the Airport Express units drop (have orange warning signs in Airport Utility). Additionally, TC drops from my “finder shared menu” (but oddly enough, not each and every time). When this happens, I switch to WiFi and all returns to normal.
Since I prefer using Ethernet, what can I do to eliminate this problem…or is this something that I need to wait for Apple to address/resolve? I was online with Apple Support and they claim the problem stems from the OSX Firewall and that I use bitDefender as a virus protector. However, when I disable them (and restart the computer each step of the way), the problem is not solved. It may work for about a minute or 2 (only after restart) but then it all drops.
Any advice would be greatly appreciated!!You might need to explain a bit more as fibreoptic hookups in a house are too expensive for most of us. Fibre technology is well developed but not at home level routers and switches... so unless you are using enterprise level stuff I don't know how to test it.
You do need to understand something.. the airport utility at least is 100% dependent on wireless now. It has taken me ages to understand that simple point. v5 utility was happy with either ethernet or wireless.. but the actual connections to the wireless routers as far as the OS in the computer is concerned is totally wireless. Even if you use ethernet your wireless should also be active. Just make sure it is second on the list of networks so whenever ethernet is up, it is preferred over wireless.
There is a big FATT BUTT here.. I do not like running wireless and ethernet simultaneously as I found it slows the network.. even if the order is correct. But I have not done the tests on Mavericks with the newest AC model TC. It definitely causes slow downs on earlier OS.
It is not actually possible to avoid the wireless issue .. although you can manually mount the disk in finder. That should stop it dropping out.. mostly.
Another BIG FATT BUTT.. you need to mount by IP not network names.. I have found in Mavericks network names drop in and out like a yoyo. So the only reliable method is using IP addresses. That means you need static IP on the TC at least, which is no problem as long as it the main router. If you have it in bridge, use the dsl modem to fix the IP of the TC via dhcp reservations. Or set static IP on it.
Then you go to Finder.. Go in the top menu, Connect to server.
Type in AFP://TCIPaddress
eg at default. AFP://10.0.1.1
It will search and discover the TC, and then request a password.. this is your disk access password on the TC, mostly set to device access password. It is public by default. Most likely the setup wizard will have forced you to change it.
Don't forget to save it in your keychain.
Will this fix it.. hmmm no.. probably not??
There are more bugs here than you can poke a stick insect at.
Perhaps once a week you will need to reboot everything... If it is daily or hourly.. then something more needs doing.
I do strongly recommend everything on the network using SMB names.. Not apple naming convention. Since Mavericks is now using SMB networking protocol by default.
Fix it everywhere on everything. Keep names short, no spaces and stick to pure alphanumeric.
Tell us if it helps or even if not.. !! -
Airport Express w/Time Capsule drops connection
I just integrated my new Time Capsule into our all-Mac network here a couple of days ago and its been fine for the most part but I've noticed that the existing airport express flashes amber for a few seconds every so often (usually once per hour or so) and disconnects everyone sharing files and connections. I have Leopard Server 10.5.2 running as well and this didn't seem to be happening before introducing Server to the mix (it was connected about 48 hours AFTER the time capsule) but the problem seems to lie with the Airport Express. Things are connected as follows:
Cable modem --> Airport Extreme
Airport Extreme --> 2 ethernet connections to Macs, 1 ethernet connection to Time Capsule
Time Capsule --> 1 ethernet connection to Mac Mini running Leopard Server
I have bridge mode set up and a couple of portables connected to it as well as an Apple TV, all of these seem to be connecting and staying connected just fine - it's the two Mac's connected directly to the Airport Extreme that get hit - the light on the unit (AE) flashes amber for maybe 2-3 seconds and I lose connection to any other macs I was connected to - I can easily re-connect with no problems at all but its obviously kind of a pain when you're working on files from the server, etc. and everything more or less locks up while OS X loses these connections.
Does anyone have any insight into why this might be happening? I've never had any trouble with this prior to Time Capsule/Leopard Server, both of which I allowed to more or less set their own settings on the Airport Extreme figuring that it isn't too complex a set up or anything, it's not like we're a full on 20 client office here or something, just 5 total macs, no pc's, etc.
any guidance would be greatly appreciated.I'm running into exactly the same problem. Configuration is the same as Jackoschild's. I get about an hour of good connection, then signal drops off and I get a rapid set of connects then disconnects. Very frustrating. I'm considering turning off the Airport on the Time Capsule and going with my 54g wireless built-in to the FIOS router it is attached to. Total of two iMacs running 10.5.2 (one 20" G5, one 24" iMac) and four PCs (Windows XP SP2) demonstrating the problem. I NEVER had a drop issue with the FIOS ActionTek wireless.
Any solutions? -
Issues with Time Capsule or Home Network Setup
I have the following network:
{if this image does not come through well here is a link to one: http://daviddwight.smugmug.com/photos/i-WTzcHBn/0/XL/i-WTzcHBn-XL.jpg }
Bill of Materials:
2Wire DSL Modem (also set up making a wireless network)
Ethernet running from Modem to Apple Time Capsule (also making a wireless network)
Time Capsule hooked to 27" iMac (OS 10.7.2) via Ethernet
Time Capsule hooked to a powered USB Hub
2 printers connected to hub
2 external disk drives connected to hub
wireless devices are an xBox, 2 iPod touches, and iPhone, an iPad, a MacBook and an AirPort Express hooked to a Stereo
I have an AirPort Express I don't use
The iMac Time Machine uses the Time Capsule
Everything works except:
the AirPort Express music drops out often
but more importantly I want to have the MacBook use a partition on one of the external disk drives for its Time Machine storage - it always has trouble mounting the drive, it will crank for hours and then give an error
Every once in a while I get an error that says something like "another device already using this IP address"
I think I may have a problem with DHCP or NAT or something
Can someone help provide some adviceNice pic!!
Is the imac and MBP using Lion?
Is the TC running 7.6 firmware?
Has the issue existed since you put this together or happened subsequent to firmware or OS upgrades?
To some extent what you answer to the above will alter the advice.. but I would try a network rearrange which I know is a real pain.. a lot of work and I cannot promise it will solve things.. but I would like you to run the modem in router mode and the TC in bridge. Set a very short dhcp lease on the 2wire.. 10min.. the renewal of IP will not affect network performance in signifcant way.. but will help keep arp tables up to date.
Use manual setup for wireless on the TC.. fix the channels and make sure security is set WPA2 with a decent passkey.. and set all the names of things (and passwords) to no spaces.. no special characters.. straight alphanumeric. Wireless bridging will handle fixed channel much better than auto.
This could all achieve nothing.. but it is hard to track the issue.
You should also study the log of the TC.. but it does not seem to report an awful lot.
Do any devices have static IP set? If not then the TC is not handling DHCP very well if you are getting duplicate IP addresses. That is why I want you to try something else as the main router.
For devices like the printers. I have to admit being surprised you can manage both printers. USB hubs are a bit notorious for being a mixed bag.. if things go wrong with external USB drive I would be looking at finding a more compatible powered hub. Since these a cheap anyway.. it is finding one that agrees with TC or AEBS.. do a google search for what people are using.. again nothing might fix the problem.. but if you try something different.. hopefully with a different chipset.. it helps narrow the issue.
BTW plug the hug into the Mac and your system profiler will show lots of info about the USB device. -
Time Capsule drops connection to iMac
I've recently got a late 2009 iMac 21.5" and am having issues using it with my Time Capsule. Intermittently the iMac loses connection, it appears to still be connected the the TC but it can't communicate. I've set a ping going to 10.0.1.1 in the Terminal app with no reply and then turn airport off and back on again and hey presto it starts receiving a reply. I've looked at interference, change channel on my TC, no difference. So I ran an ethernet cable into a LAN port on the TC and no it works fine, two days with no drop outs. I don't know what to try next any ideas?
I think I have the same issue.
My iMac is connected to the TimeCapsule via ethernet (though I do have wifi running to synch a few apps with iphone).
My problem is that I have my iPhoto library file on the TimeCapsule so that it can be accessed by other family members. Almost invariably, when I plug in my iPhone, iPhoto pops up and asks which library to use even though I have indicated that the iphoto library on the TimeCapsule is to be the default.
So, in essence, I don't have to log back in, only re-connect almost always which is a pain.
Any ideas appreciated! -
Mac book has problem with dropping connection to newest Time Calsule.
NHawk wrote:
The first problem is that the time capsule quit performing backups for my laptop.
Welcome to Apple's discussion groups.
For help with your Time Machine problem, check the FAQ and Troubleshooting items at the top of the Time Machine section for OS X 10.6:
http://discussions.apple.com/forum.jspa?forumID=1342
the Time Capsule started blinking yellow and airport utility came up saying there was a problem finding a wireless signal (i think).
Please describe your local network configuration, including brand(s) and model number(s) of all equipment, as well as how everything is connected. It sounds like your Time Capsule is configured to connect wirelessly to a network created by your cable company's router. -
Fix *most but not all* issues with Time Capsule, Time Machine and 10.5.3
There are so many posts related to this issue, that I just wanted to create one short post with a how to fix / quick tips that seems to work for most but granted not all
Issues: Cannot backup, gets stuck into preparing phase or backup volume seems to be corrupted or not working. User was able to use TM with TC w/o problems before update to 10.5.3
1) Turn off TM
2) reboot TC (unplug and plug back in or do it via Airport Utility)
3) Disable energy saving and screen saving features (* see remark at the end)
4) reboot iMac, Macbook or whatever you are using
5) go to finder, unmount the backup volume
6) force a manual backup in TM
7) it will take up to 30 minutes preparing backup and then it should work
(*) I found that if the Mac enters into sleep mode or a password protected screensaver sometimes the backup gets interrupted and one get an error message. This seems like a bug and I reported it to Apple.Hi! I've had the same problem and in my case I even couldn't access the Time Machine with the Airport Utility though I was properly connected with the network. Now it seems to work, and here's what I did:
- I did a hard reset of TC by pressing the reset button for 5 sec. until the light starts flashing
- I set up the whole network/airport/tc preferences again (what you always have to do after hard reset)
- I manually startet a backup.
When I manually started the back up for the first time, the TM preferences said "Preparing" and then stopped without backing up anything.
I restarted the backup again (manually) and finally it worked like described in this post: "Preparing" for roughly half an hour.
In this time, Time Capsule/Machine finds out, what files needed to be backed up. After that Preparation period, time machine started backing up as usual.
All you have to do is hard resetting and setting up the Time Capsule from new. You DO NOT have to delete the hard drive!!!
Message was edited by: DoubleMumboJumbo
Message was edited by: DoubleMumboJumbo
Maybe you are looking for
-
HT1695 CAN'T SYNC MY IPOD OR IPAD
Although I've previously sync my ipod touch and ipad2 the dll file appears to be missing. I've uninstalled and reinstalled itune but still have the problem. Any answers to this problem please?
-
Mdworker deny file-read-data, what does it really mean?
I get numerous log posts like this: 3/17/14 7:22:57.561 AM sandboxd[5688]: ([4412]) mdworker(4412) deny file-read-data /Volumes/Time Machine Backups/Backups.backupdb/Jack Shelton's iMac/2014-03-17-042247/JackHD/System/Library/Fonts/TimesLTMM (import
-
_FU_P - No matching record found..
Hi All, I am trying to upgrade to an existing system from 8.81 PL:06 to PL:08 and get the failure as follows: Object: FUP Failure Message: No Matching records found (ODBC - 2028) I have no idea as to what this object is. Can anyone shed some light on
-
Business object attribute assignment
Hi Al Experts, We have a transaction in SAP called SWF_BAM where we can trigger a proxy call on the basis of events triuggered. I created a z BO and i am trying to create the binding between my BO and proxy structure. Here we can link the BO attribut
-
ALV GRID update internal table
Hi all, I have an internal table display in a ALV GRID. Only one column is editable. When I change the field value, ALV GRID display the change, but when I click on refresh return the old value. I've checked in DEBUG mode and when I click on refresh