DHCP and PCs

2000-08-28 Thread Donny Piwowarski



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: 4.2 update and DHCP problems

2000-03-08 Thread Serge Paulus

I had the same problem and solved it by forgetting the client and then reinstalling it 
in the client database.

On mardi 7 mars 2000, Todd Reed [EMAIL PROTECTED] wrote:
I'm having trouble keeping my DHCP clients activated with Retrospect 
4.2 for Mac.

The clients, on a 10Bt hub, were all connecting fine via Appletalk 
and Retrospect 4.1

I began by updating the application to 4.2. Then I went into the 
client database and began switching client protocol to TCP/IP. After 
switching, they disappeared from the network. So we began updating 
the clients by going from system to system and running the
updater.

The next day I noticed that the clients were inactive in the client 
database. After looking at the clients in the network window, the 
systems also were active in the client database.

We updated a couple of systems again that day to get them to 4.2. 
Next day, again all the clients in the database are inactive. Nothing 
got backed up the night before. I know at least one of the clients 
got a full install of 4.2 from scratch, not an update.

I could use some suggestions as to why this is happening.

Todd Reed

Infoasis Internet Services534 4th St., Ste. 2San Rafael, CA 94901
  (415) 459-7991 FAX: (415) 459-7992  [EMAIL PROTECTED]
  http://www.infoasis.com


--
--
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]



4.2 update and DHCP problems

2000-03-07 Thread Todd Reed

I'm having trouble keeping my DHCP clients activated with Retrospect 
4.2 for Mac.

The clients, on a 10Bt hub, were all connecting fine via Appletalk 
and Retrospect 4.1

I began by updating the application to 4.2. Then I went into the 
client database and began switching client protocol to TCP/IP. After 
switching, they disappeared from the network. So we began updating 
the clients by going from system to system and running the updater.

The next day I noticed that the clients were inactive in the client 
database. After looking at the clients in the network window, the 
systems also were active in the client database.

We updated a couple of systems again that day to get them to 4.2. 
Next day, again all the clients in the database are inactive. Nothing 
got backed up the night before. I know at least one of the clients 
got a full install of 4.2 from scratch, not an update.

I could use some suggestions as to why this is happening.

Todd Reed

Infoasis Internet Services534 4th St., Ste. 2San Rafael, CA 94901
  (415) 459-7991 FAX: (415) 459-7992  [EMAIL PROTECTED]
  http://www.infoasis.com


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



DHCP

2000-02-14 Thread Ryan La Riviere

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]



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: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,

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]