See if this helps-
STATUS CODE 58: "Can't connect to client" Troubleshooting
procedures for Status 58 errors.
http://support.veritas.com/docs/321172
From:
veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of McDonald II, James F.
Sent: Wednesday, April 01, 2009
7:34 AM
To:
veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] (no subject)
We are trying to get Red Hat Enterprise Linux 5.0 and NBU
6.5 to connect/talk. We have installed a NBU Linux client from the
Symantec download site and xinetd, but the two (Linux & NBU) do not see
each other. Do you need to configure the client service a certain way on
the Linux box, other than the typical, straight-forward install? Since
xinetd is for on-demand services, is there a config file that needs to be
altered to run correctly and start the NBU client? Does the NBU 6.5 Linux
client even support REHL 5.0?
I have seven Linux boxes I need to connect to NBU, and they
are used daily by developers, so they are the most important ones. I
created the backup policies on my backup server (running W2K3 server), but when
I try to specify the folders/directories to be backed up NBU is unable to
connect to the Linux box.
