STATUS CODE 54 or STATUS CODE 58: Some third-party software packages can link into the TCP/IP stack in Windows and cause a loss of connection between the Veritas NetBackup (tm) server and the bpcd process on the client.

Problem

STATUS CODE 54 or STATUS CODE 58: Some third-party software packages can link into the TCP/IP stack in Windows and cause a loss of connection between the Veritas NetBackup (tm) server and the bpcd process on the client.

Error Message

Timed out connecting to client (54)
Can't connect to client (58)
status 25: cannot connect on socket

11/10/2016 13:28:08 - Info bpbrm (pid=8344)     status: FAILED, (11) TIMEOUT; system: (10036) A blocking operation is currently executing. ; FROM 0.0.0.0 TO <ip address of client> <ip address of client> vnetd VIA pbx
11/10/2016 13:28:08 - Info bpbrm (pid=8344)     status: FAILED, (11) TIMEOUT; system: (10036) A blocking operation is currently executing. ; FROM 0.0.0.0 TO <ip address of client> <ip address of client> vnetd VIA vnetd
11/10/2016 13:28:08 - Error bpbrm (pid=8344) Cannot connect to <client name>
11/10/2016 13:28:08 - Info bpbkar32 (pid=0) done. status: 58: can't connect to client

Solution

Issue:
Some third-party software packages can link into the TCP/IP stack in Windows and cause a loss of connection between the NetBackup server and the bpcd process on the client.  This results in a Status 54 and/or status 25 errors in NetBackup.  A Winsock error code 10038 or 10036 can also be seen in the client's bpcd log.  

Troubleshooting:
The following is a partial list of software that this issue has occurred with:
  • AT&T Communications Manager
  • Aventail VPN
  • Citrix Extranet Client, Citrix Advanced Gateway Client
  • Citrix Metaframe Client Remote Admin
  • Columbitech WAP connector and Gateway
  • DIAMONDCS Port Explorer (This application shows up in the services query as "Port Explorer")
  • HTTPLook
  • Juniper Networks Secure Application Manager
  • Juniper Networks VPN Client
  • Lavasoft WC Assistant (WCAssistantService)
  • Microsoft Personal Firewall
  • Microsoft Forefront
  • Microsoft Proxy Server
  • Neoteris Application Proxy
  • NetSpective Terminal Server Agent.
  • NOD32 Anti-virus Software  (See workaround for NOD32 in the Related Documents section below)
  • Panda Antivirus
  • Permeo Application Security suite (client module)
  • PGP Desktop
  • OpenText SOCKS Client
  • SurfControl
  • Kaseya Agent
Log Files:
The following <install_dir>\VERITAS\NetBackup\logs\bpcd\<date>.LOG extract shows what is observed on the client side bpcd log when this error occurs:
<2> bpcd main: offset to GMT 0
<2> bpcd main: Got socket for input -1
<2> logconnections: getsockname(-1) failed: 10038
<16> bpcd setup_sockopts: setsockopt 1 failed:
<2> bpcd main: setup_sockopts complete
<16> bpcd main: authentication failed: 17
<2> bpcd main: offset to GMT 0

Resolution:
The error can be avoided by completely uninstalling the software on the client that is relative to the failure.  However, it is recommended to contact the respective software manufacturer to investigate if other configuration options or workarounds are possible.

When the error occurs, NetBackup is trying to set SO_REUSEADDR (allow local address reuse) on the inbound socket connection so the port can be handed off from bpinetd.exe (the NetBackup Client Service) to bpcd.exe.  Some products, such as those listed above, may not allow this functionality due to various methods that can be used to violate system security.
 

 

Terms of use for this information are found in Legal Notices.

Search

Survey

Did this article answer your question or resolve your issue?

No
Yes

Did this article save you the trouble of contacting technical support?

No
Yes

How can we make this article more helpful?

Email Address (Optional)