Is it in the bp.conf?
CLIENT_NAME = myhost

-----Original Message-----
From: Shaffer, Justin [mailto:Justin.Shaffer AT mlb DOT com]
Sent: 09 August 2002 18:15
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Error 54 Unix Client


Hi All,

Quick question for you. We have a Solaris Server, and all solaris clients.
One of our clients has recently started failing with error 54. While I've
debugged name service issues with netbackup authentication before, this does
not seem to be the issue. However, bpcd is logging the following:

13:00:58 [3759] <2> bpcd main: offset to GMT 18000
13:00:58 [3759] <2> bpcd main: setup_sockopts complete
13:00:58 [3759] <2> bpcd main: output socket port number = 650
13:00:58 [3759] <8> bpcd peer_hostname: gethostbyaddr failed :
HOST_NOT_FOUND (1)
13:00:58 [3759] <16> bpcd peer_hostname: gethostbyaddr failed to return peer
host, herrno = 1
13:00:58 [3759] <16> bpcd main: Couldn't get peer hostname

the client name is in hosts and dns for the server, and the same goes the
other way around. 

Any suggestions would be appreciated.

Thanks,

Justin

============================================================================
==
"WorldSecure Server <mlbaseball.com>" made the following
 annotations on 08/09/02 13:16:48
----------------------------------------------------------------------------
----------------------------------------------------------------------------
----
[INFO] -- Virus Manager:
No Viruses were detected in this message.

============================================================================
==

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


------------------------------------------------------------------------------
This message is intended only for the personal and confidential use of the 
designated recipient(s) named above.  If you are not the intended recipient of 
this message you are hereby notified that any review, dissemination, 
distribution or copying of this message is strictly prohibited.  This 
communication is for information purposes only and should not be regarded as an 
offer to sell or as a solicitation of an offer to buy any financial product, an 
official confirmation of any transaction, or as an official statement of Lehman 
Brothers.  Email transmission cannot be guaranteed to be secure or error-free.  
Therefore, we do not represent that this information is complete or accurate 
and it should not be relied upon as such.  All information is subject to change 
without notice.