Forum Discussion

madhuri's avatar
madhuri
Level 4
11 years ago

Cannot connect to client

Hi

In my Environment one of the windows  server is failling with 58 ,i can ping the serverr host properites are loading, in client name if i remove the back end -e1 the host properties are not loading,if i keep the back end and if i run the backup it was failling with staus

 

nfo RUNCMD(pid=9272) exiting with status: 0         
Status 0
4/27/2014 11:49:11 PM - end Bare Metal Restore, End Notify Script; elapsed time: 00:00:00
Status 58
4/27/2014 11:49:11 PM - end Parent Job; elapsed time: 00:04:55
can't connect to client(58)

 

started backup (backupid=wcmdgwapt1-e1_1398664075) job for client wcmdgwapt1-e1, policy  NAme, schedule Incremental on storage unit XXXX-hcart-robot-tld-0
4/27/2014 11:47:56 PM - started process bpbrm (7968)
4/27/2014 11:48:38 PM - Info bpbrm(pid=7968) starting bptm           
4/27/2014 11:48:38 PM - Info bpbrm(pid=7968) Started media manager using bpcd successfully       
4/27/2014 11:49:11 PM - Info bpbrm(pid=7968) connect failed STATUS (18) CONNECT_FAILED        
4/27/2014 11:49:11 PM - Info bpbrm(pid=7968)     status: FAILED, (44) CONNECT_TIMEOUT; system: (10060) Connection timed out.; FROM 0.0.0.0 TO YYYYY-e1 135.9.247.28 bpcd VIA pbx
4/27/2014 11:49:11 PM - Info bpbrm(pid=7968)     status: FAILED, (44) CONNECT_TIMEOUT; system: (10036) A blocking operation is currently executing. ; FROM 0.0.0.0 TO YYYYY-e1 135.9.247.28 bpcd VIA vnetd
4/27/2014 11:49:11 PM - Info bpbrm(pid=7968)     status: FAILED, (44) CONNECT_TIMEOUT; system: (10036) A blocking operation is currently executing. ; FROM 0.0.0.0 TO YYYYY-e1 135.9.247.28 bpcd
4/27/2014 11:49:11 PM - Error bpbrm(pid=7968) Cannot connect to YYYYY-e1         
4/27/2014 11:49:11 PM - end writing
can't connect to client(58)

7.1.x and Earlier
Backup and Recovery
Error messages
NetBackup
Windows 7
  • Marianne's avatar
    Marianne
    11 years ago

    ... blocking operation is currently executing....

     

    Job details show that connection was attempted first on PBX (port 1556), then vnetd (port 13724), then bpcd (13782).

    So, it seems that there is either a firewall between the media server and the client, or else OS firewall on the client is blocking port connections. If OS firewall, disable it.

     NetBackup 6.x and 7.x firewall port requirements
    http://www.symantec.com/docs/TECH136090

  • ipmanyak's avatar
    ipmanyak
    Level 5
    11 years ago

    Be convinced that Windows Firewall on both sides allows connections and that the server and the client resolve each other.

    Some articles for help:

    Troubleshooting procedures for Status 58 errors.
    Article URL http://www.symantec.com/docs/TECH68832

    Windows Bare Metal Restore (BMR) restore fails with status code 58: can't connect to client.
    Article URL http://www.symantec.com/docs/TECH88078    

    Cannot connect to socket (25) and Backup fails with Status code 58: Can't connect to client.
    Article URL http://www.symantec.com/docs/TECH130453

  • watsons's avatar
    watsons
    Level 6
    11 years ago

    Follow the above suggestions by ipmanyak, and don't forget to check the client end YYYYY-e1 that:

    1) Netbackup client services are up and running.
    2) Netbackup registry key to ensure it can access by master server (or bp.conf for Unix client). I have seen many times that a client belongs to another master server. 
     

    3) bpclntcmd -pn  should returns the correct client hostname and IP address.

  • Marianne's avatar
    Marianne
    Level 6
    11 years ago

    ... blocking operation is currently executing....

     

    Job details show that connection was attempted first on PBX (port 1556), then vnetd (port 13724), then bpcd (13782).

    So, it seems that there is either a firewall between the media server and the client, or else OS firewall on the client is blocking port connections. If OS firewall, disable it.

     NetBackup 6.x and 7.x firewall port requirements
    http://www.symantec.com/docs/TECH136090