Rich:

All I can offer is something you have probably already investigated. I
am a Solaris/AIX guy so Wintel is not my strong suit.

What changed?
General network connectivity okay?
Can the client properly resolve the name of the master server?
Within UNIX-land you can run /usr/openv/netbackup/bin/bpclntcmd. Can you
do that with favorable results in the Win2K?
What about the bp.conf?

This is all I can think of off the top of the head...

Good luck,

Bill

--------------------------------------------------------
     Bill Jorgensen
     CSG Systems, Inc.
     (w) 303.200.3282
     (p) 303.947.9733
--------------------------------------------------------
     UNIX... Spoken with hushed and
     reverent tones.
--------------------------------------------------------

-----Original Message-----
From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of Rich McGee
Sent: Wednesday, April 06, 2005 12:02 PM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Status Code 54 in NetBackup DataCenter?

Backup Folks;

About two weeks ago, one of my Windows 2k backup clients started
returning 
a status code "54" when the Veritas backup manager attempted to contact
it 
for either a full or an inc dump. If I try a restore to that client, I
get 
a status code "58".  Yet the backups to all my other clients off the
same 
manager continue to work just fine. I've even gone as far as deleting
and 
re-installing the backup client software. No change. The server can't 
exchange any data with the client, nor can the client see the server.
Both 
are on the same switch, and, outside of the normal Windows automatic 
updates, nothing appears to have recently changed. This backup system,
and 
the policies behind it, are about 1 1/2 years old, and have worked great

until this point.

The error message:
Error 54 - Timed out connecting to client
The server could not complete the connection to the client. The accept 
winsock call timed out after 60 seconds.
It then refers me to network troubleshooting, and the company support
site.

I did try a manual config/backup from the client side, raising the 
time-out. No difference except for the timeout displayed value.

Environment:
Veritias - NetBackup DataCenter 4.5 (MP 4.5)
Server - Solaris 9 with an L8 auto cart loader
Client - Dell with Windows 2k and all current patches, no firewall
Note - Dell client is on a gig switch, so I upgraded the firmware per
the 
Veritas tech note. No change.

Suggestions, anyone? I'm leaning towards the idea that the port Veritas
is 
trying to use isn't available on the client, but that's just a hunch.

-Rich McGee

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