As one of the senior QA people here at Dantz, I've been asked to reply to
this post. Hopefully I can cover most of the issues involved.

First, I have to thank Gowan for that last post. I appreciate its pragmatic
approach. My intention with this post is to address Gowan's questions, and
to provide an overview of troubleshooting an NT/2000 system with multiple

Gowan's questions:
1. Does anyone have the Retrospect CLIENT running successfully on a Win2k
SERVER? YES. Absolutely. Here at Dantz we back up Windows 2000 servers via
the client every night.

2. Does anyone have the Retrospect Client working on a dual-homed machine?
YES. I personally have backed up a client with 2 NICs every night for over a
year, using Win NT 4.0 and then Windows 2000 as soon as the first stable
beta was available.

3. Are there any known cases of Retrospect Client having port conflicts with
other TCP/IP services? Not with other services per se. The client issues we
see are almost always to to configuration issues. Each TCP/IP host has an
internal routing table. This has to be set up properly. Each network router
needs to properly support multicasting and subnet broadcasting. Of course,
you could force our software to conflict by setting http (or some other
service) to step on our well-known port, but that's an unlikely scenario.

Troubleshooting a multiple NIC system:
I'm going to cover the simplest case, where your system has 2 NICs and each
NIC has one address.

1. The first thing to do is install the client 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 client name as displayed in the control
panel, 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 or 2000, and b) 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 and want to force the client to bind to a FIXED
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 "" to the desired address.
4. Start the client service, open the control panel & verify the status is
Ready or Waiting for first access.

Hope this helps everyone,

Paul Mackinney
Dantz Development Corporation

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

Reply via email to