Time Capsule / Xbox Live compatibility issues...

I have my xbox connected to my Time Capsule through ethernet so wireless isn't an issue. I've tried port forwarding and DMZ host which both leave the xbox telling me my NAT is set to strict. So far though it seems I can still use xbox live with my friends and it isn't an issue. However my girlfriend just got into 1 vs 100 and has played a few times so far. We just booted the xbox up today and tried to log in and now it gives us a network connection error each time we try to play. I've tried every various setting I can think of in the Time Capsule and none of them seem to work. Will my gf never be able to play 1 vs 100 again?
Does anybody else have an Xbox connected to a Time Capsule that is able to play 1 vs 100? Could you please try if you haven't and let me know how it goes for you.
Thanks in advance,
Kye

Similar Messages

Airport time capsule Extreme dropping connection issue i have already upgraded new firmware 7.7.3 but problem is still in wifi connectivity drop please solve this issue i have expanded my money in tc drive

time capsule drop wifi connection issue .I have already upgraded new firmware 7.7.3 but problem in not solve i am very confuse to resolving this issue.also i attached my log here.
May 15 11:37:43
5
Initialized (firmware 7.7.3).
May 15 11:37:50
5
Deauthenticating with station ff:ff:ff:ff:ff:ff (reserved 3).
May 15 11:37:50
5
Deauthenticating with station ff:ff:ff:ff:ff:ff (reserved 2).
May 15 11:37:50
5
Rotated TKIP group key.
May 15 11:37:51
5
Clock synchronized to network time server time.apple.com (adjusted +1 seconds).
May 15 11:37:54
5
Associated with station b8:e8:56:1f:2c:98
May 15 11:37:54
5
Installed unicast CCMP key for supplicant b8:e8:56:1f:2c:98
May 15 11:38:27
5
Associated with station 78:a3:e4:ba:90:42
May 15 11:38:27
5
Installed unicast CCMP key for supplicant 78:a3:e4:ba:90:42
May 15 11:39:14
5
Connection accepted from [::ffff:192.168.1.170]:49439.
May 15 11:40:49
5
SMB/CIFS login OK from [email protected].
May 15 11:43:14
5
Connection accepted from [::ffff:192.168.1.170]:49452.
May 15 11:43:19
5
Connection accepted from [::ffff:192.168.1.170]:49454.
May 15 11:43:20
5
Connection accepted from [::ffff:192.168.1.170]:49456.
May 15 11:43:42
5
Disassociated with station b8:e8:56:1f:2c:98
May 15 11:43:43
5
Rotated TKIP group key.
May 15 11:44:20
5
Connection accepted from [::ffff:192.168.1.170]:49460.
May 15 11:45:21
5
SMB/CIFS login OK from [email protected].
May 15 11:47:33
5
Associated with station b8:e8:56:1f:2c:98
May 15 11:47:33
5
Installed unicast CCMP key for supplicant b8:e8:56:1f:2c:98
May 15 11:47:34
5
Disassociated with station b8:e8:56:1f:2c:98
May 15 11:47:35
5
Rotated TKIP group key.
May 15 11:47:57
5
Associated with station e4:92:fb:dc:02:0b
May 15 11:47:57
5
Installed unicast CCMP key for supplicant e4:92:fb:dc:02:0b
May 15 11:49:25
5
SMB/CIFS login OK from [email protected].
May 15 11:50:37
5
Connection accepted from [::ffff:192.168.1.170]:49472.
May 15 11:50:42
5
Connection accepted from [::ffff:192.168.1.170]:49474.
May 15 11:50:44
5
Connection accepted from [::ffff:192.168.1.170]:49476.
May 15 11:51:18
5
SMB/CIFS login OK from [email protected].
May 15 11:51:25
5
SMB/CIFS login OK from [email protected].
May 15 11:51:53
5
Connection accepted from [::ffff:192.168.1.170]:49478.
May 15 11:53:07
5
Idle timeout for station e4:92:fb:dc:02:0b
May 15 11:53:07
5
Disassociating with station e4:92:fb:dc:02:0b (reserved 4).
May 15 11:53:07
5
Disassociated with station e4:92:fb:dc:02:0b
May 15 11:53:07
5
Rotated TKIP group key.
May 15 11:54:45
5
Connection accepted from [::ffff:192.168.1.170]:49497.
May 15 11:54:52
5
Connection accepted from [::ffff:192.168.1.170]:49499.
May 15 11:54:57
5
Connection accepted from [::ffff:192.168.1.170]:49502.
May 15 11:55:15
5
Connection accepted from [::ffff:192.168.1.170]:49504.
May 15 11:55:24
5
Connection accepted from [::ffff:192.168.1.170]:49506.
May 15 11:55:45
5
Connection accepted from [::ffff:192.168.1.170]:49508.
May 15 12:05:39
5
SMB/CIFS login OK from [email protected].
May 15 12:05:40
5
unloading current configuration.
May 15 12:05:55
5
Deauthenticating with station ff:ff:ff:ff:ff:ff (reserved 3).
May 15 12:05:55
5
Deauthenticating with station ff:ff:ff:ff:ff:ff (reserved 2).
May 15 12:05:55
5
Rotated TKIP group key.
May 15 12:05:56
5
Clock synchronized to network time server time.apple.com (adjusted +0 seconds).
May 15 12:06:00
5
Associated with station 78:a3:e4:ba:90:42
May 15 12:06:00
5
Installed unicast CCMP key for supplicant 78:a3:e4:ba:90:42
May 15 12:06:45
5
Disassociated with station 78:a3:e4:ba:90:42
May 15 12:06:45
5
Rotated TKIP group key.
May 15 12:07:19
5
Associated with station 78:a3:e4:ba:90:42
May 15 12:07:19
5
Installed unicast CCMP key for supplicant 78:a3:e4:ba:90:42
May 15 12:09:15
5
Connection accepted from [::ffff:192.168.1.170]:49576.
May 15 12:09:35
5
Connection accepted from [::ffff:192.168.1.170]:49578.
May 15 12:09:49
5
Connection accepted from [::ffff:192.168.1.170]:49580.
May 15 12:25:40
5
Connection accepted from [::ffff:192.168.1.170]:49709.
May 15 12:25:51
5
Connection accepted from [::ffff:192.168.1.170]:49711.
May 15 12:26:12
5
Connection accepted from [::ffff:192.168.1.170]:49717.
May 15 12:27:40
5
Connection accepted from [::ffff:192.168.1.170]:49723.
May 15 12:27:41
5
unloading current configuration.
May 15 12:27:56
5
Deauthenticating with station ff:ff:ff:ff:ff:ff (reserved 3).
May 15 12:27:56
5
Deauthenticating with station ff:ff:ff:ff:ff:ff (reserved 2).
May 15 12:27:56
5
Rotated TKIP group key.
May 15 12:28:00
5
Associated with station 78:a3:e4:ba:90:42
May 15 12:28:00
5
Installed unicast CCMP key for supplicant 78:a3:e4:ba:90:42
May 15 12:29:23
5
SMB/CIFS login OK from [email protected].
May 15 12:29:31
5
Connection accepted from [::ffff:192.168.1.170]:49730.
May 15 12:29:31
5
Connection accepted from [::ffff:192.168.1.170]:49732.
May 15 12:34:15
5
Connection accepted from [::ffff:192.168.1.170]:49739.
May 15 12:34:16
5
unloading current configuration.
May 15 12:34:31
5
Deauthenticating with station ff:ff:ff:ff:ff:ff (reserved 3).
May 15 12:34:31
5
Deauthenticating with station ff:ff:ff:ff:ff:ff (reserved 2).
May 15 12:34:31
5
Rotated TKIP group key.
May 15 12:34:49
5
Associated with station 78:a3:e4:ba:90:42
May 15 12:34:50
5
Installed unicast CCMP key for supplicant 78:a3:e4:ba:90:42
May 15 12:36:07
5
Connection accepted from [::ffff:192.168.1.170]:49745.
May 15 12:36:08
5
Connection accepted from [::ffff:192.168.1.170]:49747.
May 15 12:40:40
5
Associated with station 10:68:3f:46:d2:69
May 15 12:40:41
1
WPA handshake failed with STA 10:68:3f:46:d2:69 likely due to bad password from client
May 15 12:40:41
5
Deauthenticating with station 10:68:3f:46:d2:69 (reserved 2).
May 15 12:40:41
5
Disassociated with station 10:68:3f:46:d2:69
May 15 12:41:48
5
Disassociated with station 10:68:3f:46:d2:69
May 15 12:42:12
5
Connection accepted from [::ffff:192.168.1.170]:49759.
May 15 12:42:13
5
unloading current configuration.
May 15 12:42:28
5
Deauthenticating with station ff:ff:ff:ff:ff:ff (reserved 3).
May 15 12:42:28
5
Deauthenticating with station ff:ff:ff:ff:ff:ff (reserved 2).
May 15 12:42:28
5
Rotated TKIP group key.
May 15 12:42:32
5
Associated with station 78:a3:e4:ba:90:42
May 15 12:42:32
5
Installed unicast CCMP key for supplicant 78:a3:e4:ba:90:42
May 15 12:44:04
5
Connection accepted from [::ffff:192.168.1.170]:49768.
May 15 12:44:10
5
Connection accepted from [::ffff:192.168.1.170]:49771.
May 15 12:45:03
5
Connection accepted from [::ffff:192.168.1.170]:49773.
May 15 12:45:03
5
unloading current configuration.
May 15 12:45:18
5
Deauthenticating with station ff:ff:ff:ff:ff:ff (reserved 3).
May 15 12:45:18
5
Deauthenticating with station ff:ff:ff:ff:ff:ff (reserved 2).
May 15 12:45:18
5
Rotated TKIP group key.
May 15 12:45:23
5
Associated with station 78:a3:e4:ba:90:42
May 15 12:45:23
5
Installed unicast CCMP key for supplicant 78:a3:e4:ba:90:42
May 15 12:46:23
5
Associated with station e4:92:fb:dc:02:0b
May 15 12:46:24
5
Installed unicast CCMP key for supplicant e4:92:fb:dc:02:0b
May 15 12:46:43
5
Associated with station 24:fd:52:d0:3c:50
May 15 12:46:43
5
Installed unicast CCMP key for supplicant 24:fd:52:d0:3c:50
May 15 12:46:58
5
Connection accepted from [::ffff:192.168.1.170]:49780.
May 15 12:47:02
5
Connection accepted from [::ffff:192.168.1.170]:49782.
May 15 12:47:05
5
Associated with station 24:fd:52:d0:3c:50
May 15 12:47:05
5
Installed unicast CCMP key for supplicant 24:fd:52:d0:3c:50
May 15 12:47:13
5
Associated with station 24:fd:52:d0:3c:50
May 15 12:47:14
5
Installed unicast CCMP key for supplicant 24:fd:52:d0:3c:50
May 15 12:47:27
5
Associated with station 24:fd:52:d0:3c:50
May 15 12:47:30
5
Installed unicast CCMP key for supplicant 24:fd:52:d0:3c:50
May 15 12:47:39
5
Disassociated with station 24:fd:52:d0:3c:50
May 15 12:47:40
5
Rotated TKIP group key.
May 15 12:47:44
5
Associated with station 24:fd:52:d0:3c:50
May 15 12:47:44
5
Installed unicast CCMP key for supplicant 24:fd:52:d0:3c:50
May 15 12:49:07
5
Disassociated with station 24:fd:52:d0:3c:50
May 15 12:49:07
5
Rotated TKIP group key.
May 15 12:49:13
5
Associated with station 24:fd:52:d0:3c:50
May 15 12:49:13
5
Installed unicast CCMP key for supplicant 24:fd:52:d0:3c:50
May 15 12:51:19
5
Associated with station 24:fd:52:d0:3c:50
May 15 12:51:20
5
Associated with station 24:fd:52:d0:3c:50
May 15 12:51:20
5
Installed unicast CCMP key for supplicant 24:fd:52:d0:3c:50
May 15 12:51:26
5
Associated with station 24:fd:52:d0:3c:50
May 15 12:51:30
5
Deauthenticating with station 24:fd:52:d0:3c:50 (reserved 2).
May 15 12:51:30
5
Disassociated with station 24:fd:52:d0:3c:50
May 15 12:51:31
5
Rotated TKIP group key.
May 15 12:51:31
5
Associated with station 24:fd:52:d0:3c:50
May 15 12:51:31
5
Installed unicast CCMP key for supplicant 24:fd:52:d0:3c:50
May 15 12:51:34
5
Associated with station 24:fd:52:d0:3c:50
May 15 12:51:38
5
Associated with station 24:fd:52:d0:3c:50
May 15 12:51:40
5
Deauthenticating with station 24:fd:52:d0:3c:50 (reserved 2).
May 15 12:51:40
5
Disassociated with station 24:fd:52:d0:3c:50
May 15 12:51:40
5
Associated with station 24:fd:52:d0:3c:50
May 15 12:51:41
5
Rotated TKIP group key.
May 15 12:51:42
5
Associated with station 24:fd:52:d0:3c:50
May 15 12:51:42
5
Installed unicast CCMP key for supplicant 24:fd:52:d0:3c:50
May 15 12:51:47
5
Associated with station 24:fd:52:d0:3c:50
May 15 12:51:49
5
Associated with station 24:fd:52:d0:3c:50
May 15 12:51:49
5
Installed unicast CCMP key for supplicant 24:fd:52:d0:3c:50
May 15 12:51:55
5
Associated with station 24:fd:52:d0:3c:50
May 15 12:51:57
5
Associated with station 24:fd:52:d0:3c:50
May 15 12:51:59
5
Deauthenticating with station 24:fd:52:d0:3c:50 (reserved 2).
May 15 12:51:59
5
Disassociated with station 24:fd:52:d0:3c:50
May 15 12:51:59
5
Rotated TKIP group key.
May 15 12:52:05
5
Associated with station 24:fd:52:d0:3c:50
May 15 12:52:09
5
Deauthenticating with station 24:fd:52:d0:3c:50 (reserved 2).
May 15 12:52:09
5
Disassociated with station 24:fd:52:d0:3c:50
May 15 12:52:20
5
Disassociated with station 24:fd:52:d0:3c:50
May 15 12:59:22
5
Connection accepted from [::ffff:192.168.1.170]:49810.
May 15 12:59:22
5
Connection accepted from [::ffff:192.168.1.170]:49812.
May 15 13:00:07
5
Connection accepted from [::ffff:192.168.1.170]:49817.
May 15 13:00:07
5
unloading current configuration.
May 15 13:00:22
5
Deauthenticating with station ff:ff:ff:ff:ff:ff (reserved 3).
May 15 13:00:22
5
Deauthenticating with station ff:ff:ff:ff:ff:ff (reserved 2).
May 15 13:00:22
5
Rotated TKIP group key.
May 15 13:00:35
5
Associated with station 78:a3:e4:ba:90:42
May 15 13:00:35
5
Installed unicast CCMP key for supplicant 78:a3:e4:ba:90:42
May 15 13:02:00
5
Connection accepted from [::ffff:192.168.1.170]:49826.
May 15 13:02:00
5
Connection accepted from [::ffff:192.168.1.170]:49828.
May 15 13:03:14
5
Connection accepted from [::ffff:192.168.1.170]:49832.
May 15 13:03:15
5
unloading current configuration.
May 15 13:03:31
5
Deauthenticating with station ff:ff:ff:ff:ff:ff (reserved 3).
May 15 13:03:31
5
Deauthenticating with station ff:ff:ff:ff:ff:ff (reserved 2).
May 15 13:03:31
5
Rotated TKIP group key.
May 15 13:04:03
5
Associated with station 78:a3:e4:ba:90:42
May 15 13:04:03
5
Installed unicast CCMP key for supplicant 78:a3:e4:ba:90:42
May 15 13:05:07
5
Connection accepted from [::ffff:192.168.1.170]:49843.
May 15 13:05:07
5
Connection accepted from [::ffff:192.168.1.170]:49845.
May 15 13:06:15
5
Connection accepted from [::ffff:192.168.1.170]:49848.
May 15 13:06:16
5
unloading current configuration.
May 15 13:06:31
5
Deauthenticating with station ff:ff:ff:ff:ff:ff (reserved 3).
May 15 13:06:31
5
Deauthenticating with station ff:ff:ff:ff:ff:ff (reserved 2).
May 15 13:06:31
5
Rotated TKIP group key.
May 15 13:07:04
5
Associated with station 78:a3:e4:ba:90:42
May 15 13:07:04
5
Installed unicast CCMP key for supplicant 78:a3:e4:ba:90:42
May 15 13:08:08
5
Connection accepted from [::ffff:192.168.1.170]:49854.
May 15 13:08:09
5
Connection accepted from [::ffff:192.168.1.170]:49856.
May 15 13:08:20
5
Connection accepted from [::ffff:192.168.1.170]:49858.
May 15 13:12:31
5
unloading current configuration.
May 15 13:32:36
1
WPA handshake failed with STA 1c:7b:21:9c:20:fd likely due to bad password from client
May 15 13:32:57
1
WPA handshake failed with STA 1c:7b:21:9c:20:fd likely due to bad password from client
May 15 13:33:09
1
WPA handshake failed with STA 1c:7b:21:9c:20:fd likely due to bad password from client
May 15 13:33:22
1
WPA handshake failed with STA 1c:7b:21:9c:20:fd likely due to bad password from client
May 15 13:33:33
1
WPA handshake failed with STA 1c:7b:21:9c:20:fd likely due to bad password from client
May 15 15:21:21
1
WPA handshake failed with STA 10:68:3f:46:d2:69 likely due to bad password from client
May 15 15:21:26
1
WPA handshake failed with STA 10:68:3f:46:d2:69 likely due to bad password from client
May 15 15:21:41
1
WPA handshake failed with STA 10:68:3f:46:d2:69 likely due to bad password from client

It says you have the wrong password.
WPA handshake failed with STA 10:68:3f:46:d2:69 likely due to bad password from client
Reset the TC to factory and start again.
But do not be surprised if the v5 utility no longer works to do the setup.

Time Capsule & Xbox 360 over ethernet issues

I have a Time Capsule connected to my modem, I can access the internet over WiFi on my mac without issues, however when I connect my Xbox 360 to the router via ethernet it will not allow me to connect to Xbox live. What's highly frustrating is that it passes all test apart from the ICMP one. According to some forums, if your receive this then your router is not compatible with xbox live. However this contradicts people being able to connect through their TC on other posts. I can connect to xbox live if I directly plug it into my modem, so it is not anything todo with that side of things.
Is there any reason why this might be on my TC and how might I go about sorting this problem out?
Any help much appreciated
Matt

Although I also haven't been able to get it working over Wi-Fi yet, I've got it working pretty happily over what is ostensibly ethernet (powerline networking ftw).
My guess is that the problem you're having is due to your Time Capsule ignoring stuff (as a security measure) that Xbox Live is sending the Xbox, so what I think you need to do is tell your Time Capsule to stop doing that for the Xbox. You do that by getting your Time Capsule to give the Xbox the same IP address every time it connects, and to not block anything sent to that IP address.
First we need to get the Xbox's MAC address, which you can find either on the back of the Xbox itself, or by going to the System blade on the Xbox Dashboard, selecting Network Settings, Edit Settings, Additional Settings (push the left thumbstick to the right), Advanced Settings, then the MAC address should be displayed.
Just to be clear, a MAC address has nothing to do with Apple's computers, standing for Media Access Control, and is a quasi-unique code that nearly every network adapter has. We're using it here so your Time Capsule can recognise the Xbox.
Now you've got the MAC address, open AirPort Utility, select your Time Capsule and click Manual Settings, the Internet toolbar icon, then the DHCP tab. Click the plus button under the DHCP Reservations box, type Xbox 360 (or whatever you want) as the description, and click Continue. Now type the Xbox's MAC address into the MAC Address box, then click the IPv4 box, change the last number from 2 to 35 (so it's something like 10.0.1.35), and click Done.
Now we have the Xbox getting the same IP from the Time Capsule, we need to tell the Time Capsule to stop filtering stuff that's sent to that IP, to do that, click the NAT tab (inside the Internet section), then "Enable default host at:" and enter 35 as the last two digits (so it matches up with the IP address we put in the IPv4 box earlier). Finally, click Update, and when your Time Capsule has finished restarting, try the connection test on the Xbox again.

Time Capsule & Xbox 360 via ethernet

Hi
I have a Time Capsule connected to my modem wireless, I can access the internet over WiFi on my mac without issues.
When I connect my Xbox 360 to the router via ethernet it will not allow me to connect to Xbox live.
According to some forums people are able to connect their TC with XBOX 360. I can connect to xbox live if I directly plug it into my modem, so it is not anything to do with XBOX itself.
Does anybody has experience with that stuff?
Thank you in advance for any help!
Flo

Are you sure?
I am able to connect my XBOX with my wireless router. That works very good.
But I am not able to realise a connection between my XBOX 360 and my TC. So probably I have to change some configurations on my TC, right? Maybe it is a problem with my IP or DHCP configurations? I have the same problems with my Media Player ASUS O!Play HDP-R1. With wireless router I can connect the media player via ethernet to the internet but it does not work with Time Capsule.
I am really frustrated. I don't get it.

Time Capsule & XBOX

I have my xbox 360 connected to my TC via ethernet, but there are a couple issues. First is there anyway to really configure the router portion of time capsule? There are a few laughable options in the airport utility, but I can't find any setup pane that would actually be useful. I need it to open up some ports and hopefully fix the NAT problems that are created by using the default settings.
One other thing, I'm pretty sure that while the TC is doing it's hourly update the connection to xbox Live is essentially severed... Anyone else experience this?
Any suggestions would be appreciated.

I have my xbox 360 connected to my TC via ethernet, but there are a couple issues. First is there anyway to really configure the router portion of time capsule? There are a few laughable options in the airport utility, but I can't find any setup pane that would actually be useful. I need it to open up some ports and hopefully fix the NAT problems that are created by using the default settings.
One other thing, I'm pretty sure that while the TC is doing it's hourly update the connection to xbox Live is essentially severed... Anyone else experience this?
Any suggestions would be appreciated.

Time Capsule+ Xbox 360 wired connection

I am looking to pick up a Time Capsule to replace my airport express as my main router. I would like to plug in my Xbox 360 to one of the ethernet ports on the back of the time capsule, while still having a wireless network for my computers.
Are there any issues that I need to be aware of? Being that it is a "standard" router in a sense I would hope that everything likes to shake hands with each other.
Message was edited by: Sup909

Works fine.
Xbox360 although may not connect to TC. Reason WPA security.
Work around> connect Express wired to TC set express to create its own network>Xbox360 will connect to Express wireless network fine including Live.

Time Capsule & XBOX 360

Has anyone been able to get Time Capsule to work with XBOX 360 live?

I made a little movie in iMovie about how I got my Xbox 360 Wireless Adapter to receive a wireless connection from my 500 GB Time Capsule. I am pretty sure that this is also compatible with Airport Extreme.
This is the link to the video:
http://www.youtube.com/watch?v=ofz2-MhxBVg

Time Capsule dual wireless routers issues

I have a TimeWarner cable modem in the closet with a net gear 8port router connected where are all my cat5 cables drop in for our home.
I have a Cisco wireless router in the living room running wifi to iPads, iPhones, etc. That router has a cat5 cable going to my Apple Tv and everything is working fine.
I purchased a Time capsule to backup my macbook air and hooked it up to my office via cat5 and connected it's wifi to connect to my iPad when I'm in there since connectivity is sometimes slow to my Cisco wireless router.
Here's the problem. I can't get the Time Capsule to work at the same times as my Cisco wireless router. Each time I reset the modem it picks only one to connect to. My time capsule says no internet connectivity but the cat5 to my Thunderbolt shows "display ethernet" connected but I cannot access the internet.
A buddy said it's an IP address issue and they're trying to share one and that can't happen.
Please advise.
thanks.
cp

I assume that you have checked the Ethernet cable this connected to the Time Capsule and verified that it is functioning correctly. The Time Capsule would be configured to "Create a wireless network" if you want it to provide a wireless network. If you do not want the Time Capsule to provide a wireless network, then you would set the Network Mode to "Off".
To enable Bridge Mode, under the setting for Router Mode would be "Off (Bridge Mode)"
Click Update to save the settings and the Time Capsule will restart.

Time Capsule/External Hard-drive issues

Hello - I'm thinking about investing in a Time Capsule mainly to back-up my data and in particular the massive amount of photos (34,000) that I think are slowing this machine down! I just wanted to ask once I have the photos on the Time Capsule am I able to delete them from my hard-drive?
As an aside, I do have a couple of WD Hard-Drives but I amhaving issues with them in that I cannot get into the hard-drive. This has happened around the same time that I updated to OS X 10.9.2. I did read online that others were having issues with this too. Im not quite sure what to do as having spent the money on these hard-drives it's a little disappointing to have to consider buying a new external hard-drive - although probably a very worthwhile investment. Anyone having this problem too?
Thanks for your advice in advance it is much appreciated.

Since you have an iMac my advice would be to buy 2 external drives. Now you can decide to move some of your data off your iMac to one of the drives for archiving and then use the other drive as a Time Machine backup of both the iMac and the archive. You don't want a solution that has key data sitting on a single drive.
But...before you buy two drives, I must ask. How much space are you using currently on your iMac. Just having 34000 pictures won't slow down your machine unless it is running out of space. Are you running out of space? If you aren't, then a single large drive to backup your iMac is sufficient. Just don't delete the photos so you have a redundant copy of each.
Finally, I personally don't like backing up over wifi unless with a notebook. You have an iMac, a dedicated drive for backup should not be a problem behind that big screen. It will be more reliable than a wifi backup and a heck of a lot faster.

Time Capsule/Machine or Yosemite Issues

Hi,
I am really struggling with my system, 10.2. Not sure whether it is OS X or time capsule, although both have been reset, reformatted, OS X reinstalled as backup and as fresh install with only putting back applications and documents. But my system is still playing up. Any suggestions?
My symptoms are, time machine backups occur regular to time capsule then after sometime they just stop running. I have not seen a valid error message. I reboot the mac and it struggles to shutdown, often black screen with the rotating circle. I have reset PRAM/SMC/NCRAM, I have tried so many things with little success.
I have the time machine widget which says the message below, although the preference panel said that it was looking for the disk, not that it was preparing or anything. So I cancelled it.
Starting automatic backup
Attempting to mount network destination URL: afp://Marc;AUTH=SRP@SKY1EE2D._afpovertcp._tcp.local./Data
Mounted network destination at mount point: /Volumes/Data using URL: afp://Marc;AUTH=SRP@SKY1EE2D._afpovertcp._tcp.local./Data
Disk image /Volumes/Data/iMac.sparsebundle mounted at: /Volumes/Time Machine Backups
Backing up to /dev/disk3s2: /Volumes/Time Machine Backups/Backups.backupdb
Will copy (27.8 MB) from Macintosh HD
Found 174 files (27.8 MB) needing backup
2.98 GB required (including padding), 828.88 GB available
Copied 272 items (28.5 MB) from volume Macintosh HD. Linked 2341.
Created new backup: 2015-02-27-155639
Starting post-backup thinning
Deleted /Volumes/Time Machine Backups/Backups.backupdb/iMac/2015-02-26-151606 (21.1 MB)
Post-backup thinning complete: 1 expired backups removed
Backup completed successfully.
Network destination already mounted at: /Volumes/Data
Disk image already attached: /Volumes/Data/iMac.sparsebundle, DIHLDiskImageAttach returned: 35
Cancellation timed out - exiting
Just set a manual backup and it has been sitting on preparing for a while. At the end of my tether to say the least.
Thanks,
Marc

Network destination already mounted at: /Volumes/Data
The error I see is that the drive was NOT dismounted at the end of the previously successful backup.
So the next attempt at backup sees the drive as busy with the last backup.. to break this cycle has been an issue since Lion.. !!
The fix is simple .. reboot the TC. Once a week that is ok.
Not particularly helpful though if it happens several times a day.
This is just poor programming from Apple and poor bug fixes ever since.. not treating these issues as serious.
Both Time Machine and Networking in the latest Yosemite are simply poor.
I recommend you jump out. Accept the inevitable and use either a local external drive as a TM target.. so you get away from the network issues.
Or buy Carbon Copy Cloner (or other 3rd party backup) and use that.. to get away from the TM bugs.. you can even combine them and use CCC on an external drive.. but you will need to explore what works for you.
This is my list of details of getting past the networking issues with Yosemite.. but TM may still have issues. And I cannot fix those.
Factory reset universal
Power off the TC.. ie pull the power cord or power off at the wall.. wait 10sec.. hold in the reset button.. be gentle.. power on again still holding in reset.. and keep holding it in for another 10sec. You may need some help as it is hard to both hold in reset and apply power. It will show success by rapidly blinking the front led. Release the reset.. and wait a couple of min for the TC to reset and come back with factory settings. If the front LED doesn’t blink rapidly you missed it and simply try again. The reset is fairly fragile in these.. press it so you feel it just click and no more.. I have seen people bend the lever or even break it. I use a toothpick as tool.
N.B. None of your files on the hard disk of the TC are deleted.. this simply clears out the router settings of the TC.
Setup the TC again.
ie Start from a factory reset. No files are lost on the hard disk doing this.
Then redo the setup from the computer with Yosemite.
1. Use very short names.. NOT APPLE RECOMMENDED names. No spaces and pure alphanumerics.
eg TCgen5 and TCwifi for basestation and wireless respectively.
Even better if the issue is more wireless use TC24ghz and TC5ghz with fixed channels as this also seems to help stop the nonsense. But this can be tried in the second round.
2. Use all passwords that also comply but can be a bit longer. ie 8-20 characters mixed case and numbers.. no non-alphanumerics.
3. Ensure the TC always takes the same IP address.. you will need to do this on the main router using dhcp reservation.. or a bit more complex setup using static IP in the TC. But this is important.. having IP drift all over the place when Yosemite cannot remember its own name for 5 min after a reboot makes for poor networking. If the TC is main router it will not be an issue.
4. Check your share name on the computer is not changing.. make sure it also complies with the above.. short no spaces and pure alphanumeric.. but this change will mess up your TM backup.. so be prepared to do a new full backup. Sorry.. keep this one for second round if you want to avoid a new backup.
5. Mount the TC disk in the computer manually.
In Finder, Go, Connect to server from the top menu,
Type in SMB://192.168.0.254 (or whatever the TC ip is which you have now made static. As a router by default it is 10.0.1.1 and I encourage people to stick with that unless you know what you are doing).
You can use name.. SMB://TCgen5.local where you replace TCgen5 with your TC name.. local is the default domain of the TC and doesn't change.
However names are not so easy as IP address.. nor as reliable. At least not in Yosemite they aren't. The domain can also be an issue if you are not plugged or wireless directly to the TC.
6. Make sure IPv6 is set to link-local only in the computer. For example wireless open the network preferences, wireless and advanced / TCP/IP.. and fix the IPv6. to link-local only.
There is a lot more jiggery pokery you can try but the above is a good start.. if you find it still unreliable.. don't be surprised.
You might need to do some more work on the laptop itself. eg Reset the PRAM.. has helped some people. Clean install of the OS is also helpful if you upgrade installed.
Tell us how you go.
Someone posted a solution.. See this thread.
Macbook can't find Time Capsule anymore
Start from the bottom and work up.. I have a list of good network practice changes but I have avoided Yosemites bug heaven.
This user has had success and a few others as well.
RáNdÓm GéÉzÁ
Here is the fundamental problem.. a new DNS program in Yosemite is failing.
http://arstechnica.com/apple/2015/01/why-dns-in-os-x-10-10-is-broken-and-what-yo u-can-do-to-fix-it/

2TB Airport Time Capsule Connectivity and Range Issues

Got the brand new Airport + Time Capsule (2TB) to replace a weak (ane expensive) Linksys EA6500 AC router which had a hard time staying connected.
Originally replaced the Linksys with an old Belkin unit and everything worked fine. Then I bought the new Airport + Time Capsule. Since using my Airport, the connectivity & range are really unreliable. Either the signal disappears or router cannot even be found. Streaming is constantly interrupted regardless of device (AppleTV, iPhone, etc...). Because the Airport is my backup, I don't want to disconnect so I have resorted to plugging an older Linksys into one of the ethernet ports on the Airport. That network works just fine.
The latest firmware is installed... I am stumped. Big Apple supporter but this disappoints that I have any issues - especially with a new item of this price range.
In fact, as I am typing this, I opened the Airport Utility - which showed it working just fine 10 min ago - and got the following...
Suggestions are welcome... Bring it back? Change setting? Help !!
Thank you.

Poor wireless reliablity is being reported both here and in the airport section for the new extreme.
Just take a quick gander.. even the first page of threads here will have a few about the issue. So be warm and comforted.. you are merely a beta tester.. along with all the rest. eg
https://discussions.apple.com/thread/5140686?tstart=0
https://discussions.apple.com/thread/5259040?tstart=0
I would do the normal stuff to help wireless act in a stable manner.
1. Reset to factory.
2. Set all names to short, no spaces and pure alphanumeric. Give a different name to 5ghz so you can choose it.
3. Set fixed wireless channels and test in order for 2.4ghz, 11, 6, 1
And use 40 and 150 for 5ghz.. (a few channels either side is fine.. )
4. Clear out all the old wireless names on the devices.. and setup just the new TC.
No luck then return the TC and either get refund.. or take another.. but until Apple fixes the firmware it is not likely to be fixed.
I would buy the Asus RT-N66U or AC66U.. for a more mature product.. and us external drive for TM.

IMac and Time Capsule duplicate IP address issues

I recently bought an iMac and am using Time Capsule as a router. The TC is plugged into my DSL router via Ethernet and I have 3 Apples and 1 PC on the network.
I keep getting this error ONLY on the newest iMac (the others appear to not have an issue): "Another device on the network is using your computer's IP address (IP address #s in parentheses). Try Connecting again later. If you continue to have problems, change the IP address of this computer or the IP address of the other device. Contact the network administrator if you need more information."
It looks like my newest iMac and TC have the same IP address. Do I need to change the configuration in my TC because I'm using it to redistribute the internet from my DSL router?

Bridge Mode is correct, so you would want to leave that setting as is.
Once the update is complete, be sure to completely power cycle the entire network. That will allow the router to refresh and hopefully straighten out the IP address conflict.
Just power everything on the network down in any order that want
Wait a few minutes
Start the modem/router first and let it run for a full minute
Start the TC next in the same manner
Start each device one at a time the same way until everything is powered back up
If you continue to see IP address conflicts, then there may be an issue with the DHCP server on your router.

Time Capsule, Xbox and NAT settings.

Hello there..
I recently moved to a new a apartment and since then, am I having nothing but trouble. I've been struggling with the NAT setting on my iMac, because of bad connections and warnings on my Xbox. I want to change the settings from "strict" to "open", but I have no idea how?...
I use the newest Time Capsule and my iMac is from late 2009.
Any help will be much appreciated, thanks!

Thank you so much for the fast feedback, but i think it's already turned off... When i go to my AirPort Manual Setup, and so on, does it say "Off (Bridge Mode)"...?
I if it's any help: In my last apartment I had one modem and a Time Capsule. The modem supplied the Internet from our TV cable (I think) and then my Time Capsule that took the internet and made it wireless. I don't know if it's any help, but we didn't have any problems back then.
Now we only have my Time Capsule, that's using a regular internet cable from a little tiny white box that's hanging on our kitchen wall.
PS: My Time Capsule didn't create a new network when I moved, it kept the password, the networks name and maybe some settings? I don't know and I still don't have any idea on how to fix it...
Again, thank you so much for your reply!
Message was edited by: vfrederik

Airport Time Capsule/Air Express Networking Issue

All of a sudden none of my wireless devices will connect to my network (2 iPhone 5's, 1 iPhone4S and an iPad2). I have a Motorola Surfboard cable modem attached to a Linksys router. Hardwired to the Linksys router is an Apple Airport Time Capsule in bridge mode centrally located in the home to create a wireless network and a Mac mini in the kitchen. Hardwired to the Airport Time Capsule is another Mac mini in the family room and a Windows PC in the walkout. To extend the wireless network I have two Airport Express units at opposite ends of the home. When I use the Airport Utility both of the express units and the Airport Time Capsule will report which wireless clients are currently attached to them, and the clients show wifi as being available with full bars. However, when I try to use any app requiring network all we get is the spinning wheel. If I turn off wifi on the clients LTE & 3G works fine. I have shut down and sequentially started the network up beginning with the modem several times, leaving the system off for longer intervals each time. The DNS servers and domain name are correct and I have even initiated a DHCP lease renewal and restarted the clients with no help. I am guessing my Airport Time Capsule has failed but in no way that is obvious to me. Has anyone had a wireless failure like this? Any suggestions will be appreciated.

This is a follow up from my own post. I factory reset the Airport Time Capsule and the two Airport Express units and re-setup the wireless network leaving the Airport Time Capsule set to 802.11 N (802.11 b/g compatible) and the two Airport Express units extending the first; the network acted the same. I then changed the Airport Time Capsule to 802.11 N (only 5 GHz) and everything works as it used to. I can change it back to "b/g compatible" and it fails, and back to "only 5 GHz" and it works. It would seem the 2.4 GHz radio has failed in a rather odd way. The good thing is my wireless network is working without me having to layout some cash for new hardware. We will see how long the 5 GHz radio lasts, it is a gen 1 Time Capsule. For now all is well.

Xbox live Airport issues

My xbox live can't fine my airport express ip address, my lap tops do fine but not my xbox live got any ideas.

Try the following ...
On the AX:
o Use the AirPort Utility to check the following settings:
AirPort Menu
o Jot down the AirPort Network Name. (Note: The AirPort Network Name is the same as the SSID used by the Xbox.)
o Note your Wireless Security settings.
AirPort Menu - Wireless Options
o Note, whether or not, you have "Create a closed network" checked.
On the Xbox 360:
o System tab > Network Settings > Edit Settings
o IP Settings: Automatic
o DNS Settings: Automatic
o Wireless Mode > Select Wireless Network (Note: If you had "Create a closed network" enabled on the AX, then you will need to select "Specify Unlisted Network" otherwise you should see the AX's AirPort Network Name.
o Edit Wireless Security Settings (Note: You will have an opportunity to select your wireless security settings. They must match those set in the AX.) If you're not using wireless security, then select "No Security" from the list.
o Apply Settings
o Test Xbox Live and/or Test Media (This will run a series of tests to verify that your wireless is setup properly.)

Time Capsule / Xbox Live compatibility issues...

Similar Messages

Maybe you are looking for