NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

STATUS CODE 58: Can't connect to client. Troubleshooting procedures for Status 58 errors.

STATUS CODE 58: Can't connect to client. Troubleshooting procedures for Status 58 errors .
TECH68832 | 2015-01-12
Technical Solutions | CMS-XML

Media Manager status code 58

Media Manager status code 58
HOWTO104439 | 2014-11-20
How To | CMS-XML

Device management status code 58

Device management status code 58
HOWTO104681 | 2014-11-20
How To | CMS-XML

Device configuration status code 58

Device configuration status code 58
HOWTO104594 | 2014-11-20
How To | CMS-XML

NetBackup status code: 58

NetBackup status code : 58
HOWTO103988 | 2014-11-20
How To | CMS-XML

GENERAL ERROR: Cannot connect to socket (25) and Backup fails with Status code 58: Can't connect to client.

GENERAL ERROR : Cannot connect to socket (25) and Backup fails with Status code 58 : Can't connect to client.
TECH130453 | 2014-03-28
Technical Solutions | CMS-XML

Vmware Backups Fail with Status 58 Or " connect failed STATUS (18) connect_failed " Or "status: FAILED, (44) connect_timeout; system: (10061) No connection could be made because the target machine actively refused it" Or "getsockopt so_error returned 10061 0x274d"

Vmware Backups Fail with Status 58 Or " connect failed STATUS (18) connect_failed " Or " status : FAILED, (44) connect_timeout; system: (10061) No connection could be made because the target machine actively refused it" Or "getsockopt so_error returned 10061 0x274d"
TECH192643 | 2014-01-08
Technical Solutions | CMS-XML

Status 58 when connecting to bpcd on a client or server; unable to connect to client.

Status 58 when connecting to bpcd on a client or server; unable to connect to client.
TECH66431 | 2013-12-16
Technical Solutions | CMS-XML

VMware Backups using multiplex with load balancing option fails with Status 58

Detail Status: 6/12/2012 9: 58 :49 AM - started process bpbrm (13952) 6/12/2012 10:05:32 AM - Info bpbrm(pid=13952) connect failed STATUS (18) connect_failed
TECH195891 | 2013-11-26
Technical Solutions | CMS-XML

Status 58 when adding EMC Celerra NDMP host credentials

Unable to validate the filer wide credentials. NDMP failed to verify host ( 58 )
TECH167314 | 2013-11-18
Technical Solutions | CMS-XML

Novell backups fail with status 58 and "<8> bpcd::bpcd_wait_for_request_state: WRN - bad request token (13312)" in the bpcd log.

Novell backups fail with status 58 and "&lt;8&gt; bpcd::bpcd_wait_for_request_state: WRN - bad request token (13312)" in the bpcd log.
TECH34333 | 2013-10-23
Technical Solutions | CMS-XML

GENERAL ERROR: Network errors during Oracle RMAN backups when using xinetd resulting in status 6, status 23, status 25, status 41, or status 58

GENERAL ERROR : Network errors during Oracle RMAN backups when using xinetd resulting in status 6, status 23, status 25, status 41, or status 58
TECH58196 | 2013-10-24
Technical Solutions | CMS-XML

WIN 2003 R2 Server failing backup with status 24/54/58

WIN 2003 R2 Server failing backup with status 24/54/ 58
TECH169380 | 2011-09-12
Technical Solutions | CMS-XML

GENERAL ERROR: The Volume Manager daemon "vmd" fails to start - error 58: "daemon cannot obtain socket"

GENERAL ERROR : The Volume Manager daemon "vmd" fails to start - error 58 : "daemon cannot obtain socket"
TECH71457 | 2010-01-24
Technical Solutions | CMS-XML

STATUS CODE 58: "Can't connect to client". Backups fail with status code 58 after enabling Veritas Security Services (VxSS) and NetBackup Access Control (NBAC).

A Status 58 will occur when the server cannot connect to the client. This can occur for standard backups when there are problems with hostname resolution or network routing. This can also occur during catalog backups when the master server cannot make a network connection to a media server in order to read the catalog data.
TECH34288 | 2010-01-18
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?