TimeCapsule in different subnet

Question

Level 1

0 points

TimeCapsule in different subnet

Hi People,

Got a question about the TimeCapsule (TC).

Untill now my TC has been on the same subnet as my MBP. Due to some changes in my network i have at this moment +- 20 subnets / vlans. These subnet are all being routed by some Cisco Layer 3 routers which also contains hot standby routing. This solution is for my home lab which consist a lot of Cisco devices.

Simple situation:

TC Gigabit0/1 = 10.0.0.136/24

Router Gigabit0/1 = 10.0.0.1/24

Router Gigabit0/2 = 192.168.20.1/24

What do work at this moment.

I can route thats for sure, the network is fully routed by EIGRP/ OSPF and RIPv2. I also can internet thru the VLAN's so routing is not the issue.

I can ping the TC and getting i nice response from it. BUT i can't backup on it, "backup delayed"is the message.

When i go to Airport Utility i can't see the TC anymore.

When i go to the same subnet 10.0.0.0/24 with my MBP i can see the TC in the airport utility and i can backup to it.

I know that routers seperate broadcast traffic etc. so maybe that is the problem. Does someone know a solution to this, because i want to be able to access te TC in different subnets.

When my redesign is finished i consist of a few ESX servers, Layer 3 routers/ switches, Accesspoint on dot1q. So i nice home lab.

Thanks in advance.

MacBookPro, Mac OS X (10.5.5)

Posted on Oct 12, 2008 8:47 AM

Reply

Answer 1

WBW

Level 4

1,265 points

Oct 13, 2008 12:44 AM in response to routing

TC has to be on the same subnet as the Time Machine computer for it to work.

Reply

Answer 2

routing Author

Level 1

0 points

Oct 16, 2008 11:13 PM in response to WBW

That's strange. WHY does it need that, because i can ping it from a different subnet. Is the TC that kind of dumb device that it only can receive backups from the same subnet?

So a ping with i'm getting response is working, so no routing issue. Very strange.

Reply

Answer 3

raz@

Level 1

0 points

Jan 5, 2009 5:02 AM in response to routing

hello,

i would try this: while on other subnet, "connect to server": afp://TC's_IP, then when mounted in finder, go to system preferences/time machine and "change disk" then choose that mount point 😉

it works even if you have backed up before moving to other subnet. it even works over internet like that ... 🙂

cheers !
raz.

Reply

Answer 4

Jan 5, 2009 7:41 PM in response to routing

When you ping a device on a network, you pass the address of the device to the ping program in order to find it. In essence, you have to 'configure' the ping program to find the TimeCapsule. Conversely, Finder doesn't need any configuration to find the TimeCapsule (when it's on the local subnet.) The user doesn't need to know an IP address, etc. -- it just shows up and works.

TimeCapsule accomplishes this magic with Bonjour/Rendezvous/ZeroConf/mDNS(multicast DNS). In particular, it send out mDNS advertisements for airport.tcp., afpovertcp.tcp, and smb.tcp services. These advertisements, however, only go so far as the local subnet.

If you want automatic discovery of Bonjour devices outside of the local subnet, you'll need to setup DNS servers and clients to do DNS-SD or configure a Rendezvous Beacon to simulate the correct advertisements on a remote subnet. Or just manually configure whatever client you want to connect to the TimeCapsule (e.g. instruct Finder to Connect To Server afp://x.x.x.x).

Reply