Client Not Found Error

[ITZA]

Issue: Client Not Found Error

 

Conditons: See below

 

Server Platform: Windows 2000 Server

 

Client Platform: Windows 2000 Server

 

 

 

Cause: Each server in our network has two NIC's (Network Interface Card) installed, one NIC is configured with a routable IP address which is used to connect the server to the internet. The other is configured with a non-routable ip address (192.168.XXX.XXX) to allow us to perform our backups over a backend LAN using the aforemented non-routable IP addresses.

 

 

 

Despite the fact that the second NIC was not connected on this server, it was enabled. Retrospect client was configured to use the routable ip address assigned to the 'primary NIC and indeed the server was detected using the 'Clients' function on the Retrospect server. Furthermore, this setup had been used for some months to successfully backup the server. No changes to the configuration was made after the initial installation.

 

 

 

Without apparent cause, attempts to backup began to fail as described in the original complaint below. Rebooting the system occassionally resulted in restoration and successful backup followed by subsequent failures which finally resulted in a complete failure. Removing the client software and reinstalling same had no affect.

 

 

 

Solution:

 

 

 

1. Completely remove the Retrospect client software.

 

2. Disable the NIC that WILL NOT BE USED for backup purposes.

 

3. Re-install the retrospect client software.

 

4. Enable both NIC's.

 

 

 

Recommendation to Dantz: Provide a means to specify, confirm and/or change the NIC or IP Address used by the client in the client configuration menus.

 

 

[Mayoff]

Our Knowlegebase provide directions for dealing with Multiple NIC cards. If the server has 2 NIC cards, then you need the Server Edition of Retrospect to select the card you wish to use:

 

 

 

Troubleshooting multiple ethernet cards on a Retrospect Client running Windows (from the Knowledgebase)

 

 

 

This document explains some of the problems found when using more than one ethernet card on a PC with Retrospect.

 

 

 

1. The first thing to do is install the 5.1 client or later and restart, then open the client control panel. The status should be "Waiting for first access", or "Ready" if the client has ever been logged in. If this fails (for example, the client status might be "(network shut down)") then you need to troubleshoot basic TCP/IP network connectivity on the client.

 

 

 

2. The next thing to do is to try and access the client from Retrospect. If you're using Retrospect for Windows, go to Configure>Clients>Add and use the Test button. You can enter the DNS name, the WINS name, or the TCP/IP address. Possible responses are:

 

error -530 - This means that the host wasn't there (eg, ping failed).

 

error -541 - This means that the host is there (eg, ping succeeded) but it's not a Retrospect Client.

 

Found client... with address, name & version displayed.

 

 

 

If your client has 2 NICS and each NIC has a single address, simply try each TCP/IP address. One should work, and the other should get an error -541.

 

 

 

3. Now it gets complicated. If step 2 succeeded and the client is at the right address, you're done. If step 2 succeeded and the client is at the wrong address, you should be able to edit the BindListener registry entry (see below) to set the address PROVIDED THAT a) The client is running Windows NT, XP or 2000, and The address you want to set it to is a fixed (not DHCP) address.

 

 

 

4. If steps 2 and 3 don't resolve your problem, it's time to talk to Dantz Technical support.

 

 

 

BindListener Instructions:

 

You must be using NT/2000/XP and want to force the client to bind to a FIXED address.

 

1. Use the services control panel to halt the Retrospect Client service.

 

2. In Regedit, go to HKEY_LOCAL_MACHINE\SOFTWARE\Dantz\Client\5.0

 

3. Change the BindListener value from "0.0.0.0" to the desired address.

 

4. Start the client service, open the control panel & verify the status is Ready or Waiting for first access.