how to correctly add clients

[pbartoli]

I just realized that something wrong was going on why my bakup setup.

The problem is I have added the clients with "Add Source Directly" digitizing the clients' IP address, but the client computers are setup to have DHCP... so next time they're switched on the IP adress is different and they're not being baked up!!

 

Which is the correct way to add clients? I have and ethernet network, the Macs are setup with DHCP IP adresses.

 

I understand "Multicast" and "Add Source Directly" are both not suitable for my configuration.

 

Should I use the "subnet broadcast" method?

[pbartoli]

I just realized that something wrong was going on why my bakup setup.

The problem is I have added the clients with "Add Source Directly" digitizing the clients' IP address, but the client computers are setup to have DHCP... so next time they're switched on the IP adress is different and they're not being baked up!!

 

Which is the correct way to add clients? I have and ethernet network, the Macs are setup with DHCP IP adresses.

 

I understand "Multicast" and "Add Source Directly" are both not suitable for my configuration.

 

Should I use the "subnet broadcast" method?

 

After some web/forum searching my few hairs are getting more and more gray...

 

I tried to add again the clients with Subnet Broadcast but nothing shows up.

 

Can I solve the problem creating DHCP static adresses and then adding clients with Add Source Directly? Will this work?

How can you create DHCP static adresses in real world?

 

I know I pose lots of questions, but I'm trying to get my backup work... it was much simpler in Retrospect 6 days to my point of view.

 

Thanks

[breakaway]

We use the concept of reserved IP addresses whereby the computer is set to DHCP, but because we have told the DHCP server to give a specific MAC address a specific IP, the computer gets the same IP each time it renews. We've had no problems in backing up clients this way.

 

If you pause your pointer over the address field in the Add Source Directly drop down, you'll notice that you can enter a WINS name or a DNS name in addition to the IP address. Those alternatives can be helpful if you have a mixed OS environment.

[pbartoli]

We use the concept of reserved IP addresses whereby the computer is set to DHCP, but because we have told the DHCP server to give a specific MAC address a specific IP, the computer gets the same IP each time it renews. We've had no problems in backing up clients this way.

 

If you pause your pointer over the address field in the Add Source Directly drop down, you'll notice that you can enter a WINS name or a DNS name in addition to the IP address. Those alternatives can be helpful if you have a mixed OS environment.

 

Sorry but I don't follow you Ryan, I'm not enough technical to understand what you mean.

BTW, I don't have mixed OS in the network, just Apple Macs.

[breakaway]

If you know how to do it and your DHCP server supports it, it is possible to set the computers to DHCP and have the server give them the same IP address. In this type of configuration, Retrospect works just fine...at least it does for me. If you don't know how to set something like this up, it might just be easier to set static addresses on your computers.

[pbartoli]

If you know how to do it and your DHCP server supports it, it is possible to set the computers to DHCP and have the server give them the same IP address. In this type of configuration, Retrospect works just fine...at least it does for me. If you don't know how to set something like this up, it might just be easier to set static addresses on your computers.

 

At the moment I don't know how to set static DHCP adresses.

 

But afterall, why should I choose between static IP versus DHCP?

[breakaway]

The Retrospect Client doesn't have the capability to report a new IP address (that I know of) when you configure the source as an IP. So if the IP address of the client changes, the server won't know where to find the client.

 

[Tree]

In my case, I have established static DHCP (reserving IP assignments based on MAC hardware address) using a feature of my router. I log in to my router with admin credentials and then build up a list of MAC addresses and the IP's reserved for them. The user interface for doing so will vary based on the brand name of the router, assuming that your router offers this feature. Just look for something named "Static DHCP" or "DHCP reservation" or something similar; you might even Google-hunt for instructions by searching those terms plus the brand name of your router.

[rhwalker]

Just make sure that the "Static DHCP" or "DHCP reservation" scope doesn't overlap the dynamic DHCP pool, or else disorder could result.

 

russ

[Tree]

In my case, assigning IPs at the router, there is no issue of scope overlap; the router automatically adjusts the dynamic pool as reservations are made. But you're right, that might not be true of every router.

[tgfn]

you can use multicast, it is able to react to changed ip-adresses.

you can also use subnet broadcast.

In may case, i had to add the correct ip-adress range and subnet mask to be able to see the clients, allthough the server resides in the same subnet as the clients.