Add Client that was previously removed?

[adrianspray]

Hi,

I've been using Retrospect on and off for about ten years or so on macs. Currently running Retrospect Backup 6.1.126 on Powermac G4 on OSX 10.4.10 which back ups one other mac and 2 windows pcs (XP) over our local network.

 

I've been having problems with the windows clients which occasionally leads to the error "Internal consistency

check failed: Assertion check at elem16.c-687". I found a work around was to tell Retrospect to forget and then reestablish each defective client.

 

However, when I've come to do this today I find that I am unable to re-add the windows client through Configure>Clients>Network. One windows client shows up but the other is just not visible.

 

I have tried;

Uninstalling and reinstalling the windows client (on the windows pc)

Deleting all preferences on the mac server (both root and user levels)

 

But no luck . . .

 

Any help or pointers would be appreciated

[rhwalker]

Quote:

---

However, when I've come to do this today I find that I am unable to re-add the windows client through Configure>Clients>Network. One windows client shows up but the other is just not visible.

 

---

This is caused when Retrospect can't communicate with the client. Could be caused by several things:

 

(1) Windows client not running. I'm not a Windows person, but there must be some sort of a process monitor to tell you if the Windows client is running. Is there some sort of an on/off switch on the Windows client to shut it off?

 

(2) Windows firewall in place. Retrospect needs port 497 open for TCP and UDP, and broadcast and multicast. Here's a note from the KnowledgeBase about some utility that can be run to open things up on Windows firewall:

 

Quote:

---

However, if you enable Windows XP’s built-in Internet Connection Firewall on a computer already running the Retrospect client, you will need to run a Retrospect utility to enable client communication through the firewall. Run the "retfwset.exe" utility, found in the Retrospect client directory (by default C:\Program Files\Dantz\Client), to allow Retrospect client communication.

 

---

 

(3) something in your network infrastructure blocking port 497 TCP/UDP between this client and the Retrospect server, or blocking broadcast/multicast.

 

Can you at least ping that client from the Retrospect machine? That would show connectivity to the machine, but perhaps blocked ports, etc.

 

Russ

[adrianspray]

Russ,

Thanks for your reply. I could access the PC over the network and was able to ping it which as you suggest would indicate issues with accessing the retrospect client.

 

The client on the pc was correctly installed and I checked that it was on through the control panels setting and windows firewall was set up to allow traffic through the ports you specified.

 

In the end I removed the client form the windows PC, re-downloaded the client from the emc website and re-installed. The re-installation asked for permission to create an exception for the windows firewall and is now visible through Retrospect on the Mac server. So all up and running again.

 

Thanks for your help.

 

regards

 

Adrian