> I'm guessing > that some part of the NetBackup client is needing a package and the > protocol-less NetBackup is swallowing up the message, never to be seen by > humans.
One trick I've used is to telnet to the client on various NetBackup ports and see if any error messages come back. For example: telnet clientnode 13782 <error message about not being able to load a library> Or try starting various NetBackup binaries manually on the client and see if any errors result. - Bluejay Adametz "The ocean is so bountiful - it spreads from coast to coast." - Joan Bayez -- NOTICE: This message, including any attachments, is only for the use of the intended recipient(s) and may contain confidential and privileged information, or information otherwise protected from disclosure by law. If the reader of this message is not the intended recipient, you are hereby notified that any use, disclosure, copying, dissemination or distribution of this message or any of its attachments is strictly prohibited. If you received this message in error, please contact the sender immediately by reply email and destroy this message, including all attachments, and any copies thereof. _______________________________________________ Veritas-bu maillist - Veritasemail@example.com http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu