Hello,
Why doesn't Dantz change the situation to Clients announcing themselves to the
Server? It's a much beter scheme i think. It would also be better for a running
Backup Server 'script'. It could start backing up immediatelly when a client
announces itself. I'm having simular problems and it's only in the following
combination of factors:
Windows 2000
Service Pack 1 installed
DHCP
3com 3c905[B|C]-TX Network card
A machine above a certain speed (somewhere between 166 en 350 MHz)
It's not a problem with leases getting expired. In my situation it looks like
Retrospect's Client is binding to an ip address on startup and ignores further
changes. My problem is that the machine gets an ip address (same as ever) from
the dhcp server AFter Retrospect's Client binds to the ip address of the
network interface, so it's listening on the wrong ip address. My workaround is
a batch file in the client's startup menu, which stops and starts Retrospect.
Works fine for me.
.....hmmmmm
Heh, now that i think about it, if the client would announce itself to the
server, it would announce with a wrong ip address too, so that wouldn't help my
situation :) But it would avoid dhcp lease expiry problems, that are reported
on this list a lot.
Cheers,
martijn
Once upon a 05-03-2001, Irena Solomon hit keys in the following order:
> Hello,
>
> Steve, in your situation my suspicion was that this behavior resulted from a
> combination of two factors; have you had a chance to set up the test I
> suggested? You were dealing with DHCP clients with very short leases that
> were added by direct IP address. If you can change the way Retrospect finds
> these clients (Direct IP -> Multicast/Subnet Broadcast) will either solve
> the problem or direct us to the next step in troubleshooting. As it sounds
> like you've decided to address it in another way, perhaps David and I could
> pick up the troubleshooting where you and I left off. This kind of behavior
> isn't normal, and I can't offer a simple solution without troubleshooting.
>
> David, how were these clients added originally? Are they DHCP clients? How
> long is the lease? I'd prefer to take this off-list, as it will likely
> require troubleshooting that won't interest the list in general.
>
> Thanks,
>
> Irena Solomon
> Dantz Technical Support
> 925.253.3050
>
> >> Subject: How can a client name change?
> >> From: "David Ross" <[EMAIL PROTECTED]>
> >> Date: Thu, 01 Mar 2001 08:14:04 -0500
> >>
> >> I use a Mac to backup a Dell PIII to a DAT drive. (This was an
> >> evolution, not a new setup.) Yesterday I realized that the backup wasn't
> >> working because the name of the PC had changed from "Dell PIII
> >> Accounting" to "111ES" about a week ago.
> >>
> >> Any ideas as to what could have done this? And the odds of intentional
> >> action by the direct staff are quite low. The machine is on the internet
> >> via an ADSL line through IPNR on a 7100. No ports are mapped to the
> >> Dell. And email isn't used on the Dell. Only surfing.
> >>
> >> So are there any reasonable accidental ways this could have happened.
> >> Could it be a virus picked up via surfing?
> >>
> >> TIA
> >>
> >
> >
> > I'm having this problem too. Irena Solomon from Dantz contacted me
> > about this, but they are unable to duplicate this on their end.
> >
> > I'm primarily seeing this with Win9x laptops. I'll originally give
> > the Retrospect client a name like <computer>@<room number> where
> > <computer> is the "machine name".
> >
> > The machines will back up successfully for weeks, then
> > all-of-a-sudden, the Retrospect client will rename itself to
> > <computer>. This happened to about 20 computers (all Win9x
> > computers).
> >
> > This also just happened the past week when I updated a laptop from
> > Win98 to WinME. Immediately after I did this, the client was renamed.
> >
> > Nobody at Dantz that contacted me has any real idea why this is
> > happening (I sent them the logs to show that at no time did the Mac
> > program do the renaming -- it was pretty clear that this was
> > something happening on the client end.)
> >
> >
> > I've since gone to the practice of making sure the client name is the
> > same as the computer name and it hasn't happened since.
> >
> >
> > FWIW.
> >
> > - Steve
>
>
>
> --
> ----------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Archives: <http://list.working-dogs.com/lists/retro-talk/>
> Search: <http://www.mail-archive.com/retro-talk%40latchkey.com/>
>
> For urgent issues, please contact Dantz technical support directly at
> [EMAIL PROTECTED] or 925.253.3050.
--
----------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives: <http://list.working-dogs.com/lists/retro-talk/>
Search: <http://www.mail-archive.com/retro-talk%40latchkey.com/>
For urgent issues, please contact Dantz technical support directly at
[EMAIL PROTECTED] or 925.253.3050.
