network communication failed for XP client

[gisele]

Retrospect Workgroup 5.6.132 is installed on windows 2000 version 5.0 service pack 4.

Retrospect Client version 5.6 is installed on XP 5.1 SP 1.

Whenever I try to backup the client, it start by copying files, then when it is time for comparing, it fails with error -519 (network communication failed).

Retrospect is unable to see or configure the client until I reboot the client.

 

Retrospect Server 5.0.238 is installed on MacOS X 10.2.8.

I backup the same XP client but this time with the Mac Server 5.0.238 version, and all goes well; no communication problem.

 

What could be the problem ?

 

Gisele

[AmyJ]

On the Windows backup computer:

 

1. Ensure that TCP/IP is installed correctly and is on the list of installed network components. This can be found in your control panel under networking.

 

2. Ensure there are no unnecessary activities such as disk optimization, screen savers, or memory-intensive or processing-intensive applications running on backup server during the backup. This includes things like mail servers, gateways, web hosting, virus checking programs, and other CPU and resource-intensive activities. It is generally fine to run file serving software on the same computer as Retrospect but keep in mind the more you ask your server to do, the more likely you will run into problems or conflicts.

 

3. Connect the machine to a different port on the hub. Swap ports and cables with a nearby client that is not experiencing network trouble or producing errors.

 

4. Try new transceivers, connectors, and a network cable.

 

5. Verify you have current versions of the network drivers on the backup computer.

 

6. Reinstall the networking software and drivers and trash any network-related preferences. Try a clean installation of the operating system.

 

7. SCSI problems can affect CPU performance and cause network disconnection's or hangs. Disconnect all external SCSI peripherals from the computer except the backup device and verify the SCSI bus is properly terminated. Then try backing up client computers. If the problem involves the backup drive itself, test another backup drive for comparison or, as in the next step, move the drive to another computer to see if the problems follow the backup drive.

 

8. Install a copy of Retrospect on a different computer. Try a backup from this computer to see if the original backup computer was causing the problem.

[gisele]

Hi,

 

The Retrospect Workgroup 5.6.132 is installed on a windows 2000 server on which reside active directory, file server and a print server.

these services work well and have no communication problems.

 

When you say <ensure there are no unnecessary activities such as disk optimization[...]>, does it meen that the server may not offer other services while doing a network backup?

Why is retrospect able to backup the server locally (when there are unnecessary activities going on) but cannot backup a network client in the same conditions?

 

Gisele