For future reference-

STATUS CODE 58: Can't connect to client. Troubleshooting procedures for
Status 58 errors.
http://support.veritas.com/docs/321172



-----Original Message-----
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of
Donaldson, Mark
Sent: Wednesday, May 20, 2009 9:48 AM
To: dave.markham AT fjserv DOT net; veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] Windows Client Status 58 with a difference

Error 58 is a can't connect error.  Err 57 is if it can't reverse
correctly and authenticate the server or if the list of allowed servers
in the client is wrong.

We just pounded a bunch of these to death on a handful of servers.

A quick test is to "telnet <host> bpcd" from the master server.  If you
get a "connection refused", then the service might be down on the client
(usually).  If you just hang, before getting to the server,  check your
firewalls.

We ended up reinstalling the client in a number of NT boxen to fix the
problem.  One server had to be manually stripped of all things NB,
rebooted, and then reinstalled before it worked.

Usually, though, the service on the client needs to be started or, if
already on, bounced.

HTH -M

-----Original Message-----
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Dave
Markham
Sent: Wednesday, May 20, 2009 4:24 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Windows Client Status 58 with a difference

Guys i'm a unix/solaris engineer day to day and while i have XP on my 
laptop from day to day work, administrating Windows at a high level is 
not necessarily my forte.

I have Netbackup 5.0MP7 (dont ask, due for upgrade shortly). with 
various unix/windows clients.

We have added some new windows 2003 clients and are having trouble with 
connection status 58.

There is no DNS involved and the Master server (solaris) can telnet to 
client ports 13782 and 13724
Vnetd has been configured for the clients with bpclient -client <client>

-add -no_callback 1.

The issue we have is the Windows client itself doesnt seem to look for 
entries in %systemroot%/system32/drivers/etc/hosts  and i can't figure 
out why.

I can connect to the master server by ip on ports 13724 and 13782 but 
not via name we have configured.

If we configure the name in lmhosts it can telnet via name but Netbackup

doesnt' work properly and can't connect.

I've googled but had no joy as was pointed to a reg key which may be 
affecting things but its not on this system.

Anyone any ideas?

Dave
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu