Re: DHCP and PCs...FEATURE REQUEST...

2000-08-28 Thread Irena Solomon
Title: Re: DHCP and PCs...FEATURE REQUEST...



Configuring Retrospect to look for clients with subnet broadcast isn't associated with their IP address; Retrospect will look for any machine on in that subnet with the client software loaded. If you add any particular machine by IP address, though, Retrospect will be looking for that client at THAT address only. You may need to forget a client that you have added by address before subnet broadcast will allow you to log it in independent of it's (assigned) IP address. Just make sure that you have added in the appropriate range for the subnets you want Retrospect to look in.

If this doesn't work, I'd suggest you give tech support a call and we can make sure that everything is properly configured.

Regards,
Irena

From: "Donny Piwowarski" <[EMAIL PROTECTED]>
Reply-To: "retro-talk" <[EMAIL PROTECTED]>
Date: Mon, 28 Aug 2000 17:11:12 -0700
To: "retro-talk" <[EMAIL PROTECTED]>
Subject: Re: DHCP and PCs...FEATURE REQUEST...


Right! That works. We can see the clients but if their IP address changes , Retrospect no longer sees them.
- Original Message - 
From: Irena Solomon   
To: retro-talk   
Sent: Monday, August 28, 2000 4:46 PM
Subject: Re: DHCP and PCs...FEATURE REQUEST...

The most direct solution to this issue is to use the Subnet Broadcast feature available in Retrospect 4.2 Mac and Retrospect 5.0 Server Backup and later. From the backup Mac, go to Configure -> Clients -> Network, and under the TCP/IP menu at the top of the screen, select Configure Subnet Broadcast. Enter the subnet address and subnet mask. On the Windows side, go to Configure -> Clients -> Add, click Advanced and choose Subnet Broadcast. This will allow Retrospect to see the clients that are assigned IP addresses by DHCP.

Best Regards,

Irena Solomon
Technical Support Specialist
Dantz Development Corporation
925.253.3050
[EMAIL PROTECTED]

--- 
From: Matt Barkdull <[EMAIL PROTECTED]>
Reply-To: "retro-talk" <[EMAIL PROTECTED]>
Date: Mon, 28 Aug 2000 11:59:51 -0800
To: "retro-talk" <[EMAIL PROTECTED]>
Subject: Re: DHCP and PCs...FEATURE REQUEST...


You know what would be really cool to do, is to tie AppleTalk and TCP/IP into the Retrospect Clients.

This seems like it would work real well for DHCP clients to have both AppleTalk and TCP/IP talking to the server.  Why? AppleTalk could be used to tell the server the current IP address of the machine.  It could also be used as a fall back in case IP fails.


This won't solve any problems for folks that don't pass AppleTalk at all, but it will for the others.


I am having problems keeping my windows clients backed up.

Our setup is as follows:
Mac G4 running Retrospect 4.3
We have 4 subnets in our building. Our G4 lives on one , while the clients live on the other 3 subnets.
The problem appears to be related to DHCP.

We have a seven day lease period for IP addresses.
It appears that whenever the client's IP address changes, the backup server loses track of the client and therefore the client does not get backed up.
I have to manually add them back into the client database and re-add them to the script.
Does anyone have any experience or suggestions with running a backup server and using DHCP as the method for assigning IP addresses?
Thanks
Donny










Re: DHCP and PCs...FEATURE REQUEST...

2000-08-28 Thread Donny Piwowarski
Title: Re: DHCP and PCs...FEATURE REQUEST...



Right! That works. We can see the clients but if 
their IP address changes , Retrospect no longer sees them.

  - Original Message - 
  From: 
  Irena 
  Solomon 
  To: retro-talk 
  Sent: Monday, August 28, 2000 4:46 
  PM
  Subject: Re: DHCP and PCs...FEATURE 
  REQUEST...
  The most direct solution to this issue is to use the Subnet 
  Broadcast feature available in Retrospect 4.2 Mac and Retrospect 5.0 Server 
  Backup and later. From the backup Mac, go to Configure -> Clients -> 
  Network, and under the TCP/IP menu at the top of the screen, select Configure 
  Subnet Broadcast. Enter the subnet address and subnet mask. On the Windows 
  side, go to Configure -> Clients -> Add, click Advanced and choose 
  Subnet Broadcast. This will allow Retrospect to see the clients that are 
  assigned IP addresses by DHCP.Best Regards,Irena 
  SolomonTechnical Support SpecialistDantz Development 
  Corporation925.253.3050[EMAIL PROTECTED]--- 
  From: Matt Barkdull <[EMAIL PROTECTED]>
  Reply-To: "retro-talk" 
<[EMAIL PROTECTED]>Date: Mon, 28 Aug 2000 11:59:51 
-0800To: "retro-talk" 
<[EMAIL PROTECTED]>Subject: Re: DHCP and 
PCs...FEATURE REQUEST...
  You know what would be really cool to do, is to tie AppleTalk 
and TCP/IP into the Retrospect Clients.This seems like it would work 
real well for DHCP clients to have both AppleTalk and TCP/IP talking to the 
server.  Why? AppleTalk could be used to tell the server the current IP 
address of the machine.  It could also be used as a fall back in case 
IP fails.This won't solve any problems for folks that don't pass 
AppleTalk at all, but it will for the others.
I am having problems keeping my windows 
  clients backed up.Our setup is as 
  follows:Mac G4 running Retrospect 4.3We have 4 subnets in our 
  building. Our G4 lives on one , while the clients live on the other 3 
  subnets.The problem appears to be related to DHCP.We have a seven day lease period for IP addresses.It 
  appears that whenever the client's IP address changes, the backup server 
  loses track of the client and therefore the client does not get backed 
  up.I have to manually add them back into the client database and 
  re-add them to the script.Does anyone have any experience or 
  suggestions with running a backup server and using DHCP as the method for 
  assigning IP 
  addresses?ThanksDonny


Re: DHCP and PCs...FEATURE REQUEST...

2000-08-28 Thread Irena Solomon
Title: Re: DHCP and PCs...FEATURE REQUEST...



The most direct solution to this issue is to use the Subnet Broadcast feature available in Retrospect 4.2 Mac and Retrospect 5.0 Server Backup and later. From the backup Mac, go to Configure -> Clients -> Network, and under the TCP/IP menu at the top of the screen, select Configure Subnet Broadcast. Enter the subnet address and subnet mask. On the Windows side, go to Configure -> Clients -> Add, click Advanced and choose Subnet Broadcast. This will allow Retrospect to see the clients that are assigned IP addresses by DHCP.

Best Regards,

Irena Solomon
Technical Support Specialist
Dantz Development Corporation
925.253.3050
[EMAIL PROTECTED]

--- 
From: Matt Barkdull <[EMAIL PROTECTED]>
Reply-To: "retro-talk" <[EMAIL PROTECTED]>
Date: Mon, 28 Aug 2000 11:59:51 -0800
To: "retro-talk" <[EMAIL PROTECTED]>
Subject: Re: DHCP and PCs...FEATURE REQUEST...


You know what would be really cool to do, is to tie AppleTalk and TCP/IP into the Retrospect Clients.

This seems like it would work real well for DHCP clients to have both AppleTalk and TCP/IP talking to the server.  Why? AppleTalk could be used to tell the server the current IP address of the machine.  It could also be used as a fall back in case IP fails.


This won't solve any problems for folks that don't pass AppleTalk at all, but it will for the others.


I am having problems keeping my windows clients backed up.
 
Our setup is as follows:
Mac G4 running Retrospect 4.3
We have 4 subnets in our building. Our G4 lives on one , while the clients live on the other 3 subnets.
The problem appears to be related to DHCP.
 
We have a seven day lease period for IP addresses.
It appears that whenever the client's IP address changes, the backup server loses track of the client and therefore the client does not get backed up.
I have to manually add them back into the client database and re-add them to the script.
Does anyone have any experience or suggestions with running a backup server and using DHCP as the method for assigning IP addresses?
Thanks
Donny








Re: DHCP and PCs...FEATURE REQUEST...

2000-08-28 Thread Matt Barkdull
Title: Re: DHCP and PCs...FEATURE
REQUEST...


You know what would be really cool to do, is to tie AppleTalk and
TCP/IP into the Retrospect Clients.

This seems like it would work real well for DHCP clients to have
both AppleTalk and TCP/IP talking to the server.  Why? 
AppleTalk could be used to tell the server the current IP address of
the machine.  It could also be used as a fall back in case IP
fails.


This won't solve any problems for folks that don't pass
AppleTalk at all, but it will for the others.


I am having
problems keeping my windows clients backed up.
 
Our setup
is as follows:
Mac G4
running Retrospect 4.3
We have 4
subnets in our building. Our G4 lives on one , while the clients live
on the other 3 subnets.
The problem
appears to be related to DHCP.
 
We have a
seven day lease period for IP addresses.
It appears
that whenever the client's IP address changes, the backup server
loses track of the client and therefore the client does not get
backed up.
I have to
manually add them back into the client database and re-add them to
the script.
Does anyone
have any experience or suggestions with running a backup server and
using DHCP as the method for assigning IP
addresses?
Thanks
Donny




Re: DHCP

2000-02-14 Thread Matthew Tevenan

Ryan,

By the way, I'm assuming you've originally added all of these clients by
address (since you made a point of mentioning they all had static
addresses).

If not, the rules change. If you add a subnet to 4.2 and the clients were
initially added via default multicast, Retrospect will look for them in
BOTH the default multicast and in the defined subnets. Basically no more
configuring is required, except adding those new subnets.

Matthew Tevenan
Technical Support Specialist
Dantz Development Corporation
925.253.3050 
[EMAIL PROTECTED]

> From: Matthew Tevenan <[EMAIL PROTECTED]>
> Reply-To: "retro-talk" <[EMAIL PROTECTED]>
> Date: Mon, 14 Feb 2000 16:04:37 -0800
> To: retro-talk <[EMAIL PROTECTED]>
> Subject: Re: DHCP
> 
> Ryan,
> 
> Unfortunately you will have to log out each and every client and then log
> them back in via multicast or subnet broadcast. Retrospect Mac doesn't have
> the capability to change the way you access a client automatically.
> 
> While Retrospect for Windows does have this capability (click the Change
> button in the Access tab of each client's Properties window), I'm unsure as
> to whether and/or when this will be introduced into Retrospect Mac.
> 
> Regards,
> 
> Matthew Tevenan
> Technical Support Specialist
> Dantz Development Corporation
> 925.253.3050 
> [EMAIL PROTECTED]
> 
>> From: Ryan La Riviere <[EMAIL PROTECTED]>
>> Reply-To: "retro-talk" <[EMAIL PROTECTED]>
>> Date: Mon, 14 Feb 2000 18:58:17 -0500
>> To: "retro-talk" <[EMAIL PROTECTED]>
>> Subject: DHCP
>> 
>> All,
>> 
>> I've some references to DHCP but nothing that answers my question.  Currently
>> part of our network is on a 144.118.xx.xx IP address scheme.  We're
>> converting
>> over to a 129.25.xx.xx address scheme.  Currently all the machines being
>> backed up have static IP addresses.  However some of them will have to use
>> DHCP when we switch over to the new IP address scheme. I'm trying to find out
>> how much of a hassle I'm going to have during this switch over.  Since this
>> is
>> being done in stages, the computers being backed up that will be using DHCP
>> will be switched first and the backup server (Retro 4.2A) switched last.
>> 
>> Thanks for any insight
>> -- 
>> 
>> Ryan La Riviere
>> 
>> Lab Services Coordinator; Drexel University
>> 215.895.6010
>> ICQ: 11747071, 44292959
>> http://staff.tdec.drexel.edu/larz
>> 
>> 
>> --
>> --
>> To subscribe:[EMAIL PROTECTED]
>> To unsubscribe:  [EMAIL PROTECTED]
>> Archives:<http://list.working-dogs.com/lists/retro-talk/>
>> Problems?:   [EMAIL PROTECTED]
>> 
> 
> 
> 
> --
> --
> To subscribe:[EMAIL PROTECTED]
> To unsubscribe:  [EMAIL PROTECTED]
> Archives:<http://list.working-dogs.com/lists/retro-talk/>
> Problems?:   [EMAIL PROTECTED]
> 



--
--
To subscribe:[EMAIL PROTECTED]
To unsubscribe:  [EMAIL PROTECTED]
Archives:<http://list.working-dogs.com/lists/retro-talk/>
Problems?:   [EMAIL PROTECTED]



Re: DHCP

2000-02-14 Thread Matthew Tevenan

Ryan,

Unfortunately you will have to log out each and every client and then log
them back in via multicast or subnet broadcast. Retrospect Mac doesn't have
the capability to change the way you access a client automatically.

While Retrospect for Windows does have this capability (click the Change
button in the Access tab of each client's Properties window), I'm unsure as
to whether and/or when this will be introduced into Retrospect Mac.

Regards,

Matthew Tevenan
Technical Support Specialist
Dantz Development Corporation
925.253.3050 
[EMAIL PROTECTED]

> From: Ryan La Riviere <[EMAIL PROTECTED]>
> Reply-To: "retro-talk" <[EMAIL PROTECTED]>
> Date: Mon, 14 Feb 2000 18:58:17 -0500
> To: "retro-talk" <[EMAIL PROTECTED]>
> Subject: DHCP
> 
> All,
> 
> I've some references to DHCP but nothing that answers my question.  Currently
> part of our network is on a 144.118.xx.xx IP address scheme.  We're converting
> over to a 129.25.xx.xx address scheme.  Currently all the machines being
> backed up have static IP addresses.  However some of them will have to use
> DHCP when we switch over to the new IP address scheme. I'm trying to find out
> how much of a hassle I'm going to have during this switch over.  Since this is
> being done in stages, the computers being backed up that will be using DHCP
> will be switched first and the backup server (Retro 4.2A) switched last.
> 
> Thanks for any insight
> -- 
> 
> Ryan La Riviere
> 
> Lab Services Coordinator; Drexel University
> 215.895.6010
> ICQ: 11747071, 44292959
> http://staff.tdec.drexel.edu/larz
> 
> 
> --
> --
> To subscribe:[EMAIL PROTECTED]
> To unsubscribe:  [EMAIL PROTECTED]
> Archives:
> Problems?:   [EMAIL PROTECTED]
> 



--
--
To subscribe:[EMAIL PROTECTED]
To unsubscribe:  [EMAIL PROTECTED]
Archives:
Problems?:   [EMAIL PROTECTED]