Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. NetBackup™ Troubleshooting Guide
  3. Troubleshooting procedures
  4. Resolving network communication problems with Windows clients
NetBackup™ Troubleshooting Guide

Resolving network communication problems with Windows clients

The following procedure is for resolving NetBackup communications problems, such as those associated with NetBackup status codes 54, 57, and 58. This procedure consists of two variations: one for UNIX clients and another for Windows clients.

Note:

In all cases, ensure that your network configuration works correctly outside of NetBackup before trying to resolve NetBackup problems.

This procedure helps you resolve network communication problems with PC clients.

To resolve network communication problems

  1. Before you retry the failed operation, do the following:

    • Increase the logging level on the client (see the NetBackup Administrator's Guide, Volume I, under "Client Settings properties").

    • On the NetBackup primary server, create a bprd debug log directory and on the clients create a bpcd debug log.

    • On the NetBackup server, set the Verbose level to 1.

      See the NetBackup Logging Reference Guide for help changing the logging level.

  2. If this client is new, verify the client and the server names in your NetBackup configuration.

    See Verifying host name and service entries in NetBackup.

  3. Verify network connectivity between client and server by pinging from the server to the client and vice versa. Use the following command:
    # ping hostname

    Where hostname is the name of the host as configured in the following:

    • NetBackup policy configuration

    • WINS

    • DNS (if applicable).

    • hosts file in system directory %SystemRoot%\system32\drivers \etc\hosts

    If ping succeeds in all instances, it verifies connectivity between the server and client.

    If ping fails, you have a network problem outside of NetBackup that must be resolved before you proceed. As a first step, verify that the workstation is turned on. A workstation that is not turned on is a common source of connection problems with workstations.

  4. On Microsoft Windows clients, ensure that the NetBackup Client service is active by checking the logs. Use the Services application in the Control Panel to verify that the NetBackup Client service is running. Start it if necessary.

    • Check the bpcd debug logs for problems or errors. See the NetBackup Logging Reference Guide on how to enable and use these logs.

    • Verify that the same NetBackup client service (bpcd) port number is specified on both the NetBackup client and server (by default, 13782). Do one of the following:

      Windows

      Check the NetBackup client service port number.

      Start the Backup, Archive, and Restore interface on the client. On the File menu, click NetBackup Client Properties. In the NetBackup Client Properties dialog box on the Network tab, check the NetBackup client service port number.

      Verify that the setting on the Network tab matches the one in the services file. The services file is located in:

      %SystemRoot%\system32\drivers\etc\services (Windows)

      The values on the Network tab are written to the services file when the NetBackup client service starts.

      UNIX NetBackup servers

      The bpcd port number is in the /etc/services file. On Windows NetBackup servers, see the Client Properties dialog box in the Host Properties window.

      See Using the Host properties to access configuration settings.

      Correct the port number if necessary. Then, on Windows clients and servers, stop and restart the NetBackup Client service.

      Do not change NetBackup port assignments unless it is necessary to resolve conflicts with other applications. If you do change them, do so on all NetBackup clients and servers. These numbers must be the same throughout your NetBackup configuration.

  5. Verify that the NetBackup Request Service (bprd) port number on Microsoft Windows is the same as on the server (by default, 13720). Do one of the following:

    Windows clients

    Check the NetBackup client service port number.

    Start the Backup, Archive, and Restore interface on the client. On the File menu, click NetBackup Client Properties. In the NetBackup Client Properties dialog box on the Network tab, check the NetBackup client service port number.

    Verify that the setting on the Network tab matches the one in the services file. The services file is located in:

    %SystemRoot%\system32\drivers\etc\services (Windows)

    The values on the Network tab are written to the services file when the NetBackup client service starts.

    UNIX NetBackup servers

    The bprd port number is in the /etc/services file.

    See Using the Host properties to access configuration settings.

    Windows NetBackup servers

    Set these numbers in the Client Properties dialog box in the Host Properties window.

    See Using the Host properties to access configuration settings.

  6. Verify that the hosts file or its equivalent contains the NetBackup server name. The hosts files are the following:

    Windows

    %SystemRoot%\system32\drivers\etc\hosts

    UNIX

    /etc/hosts

  7. Verify client-to-server connectability by means of ping or its equivalent from the client (step 3 verified the server-to-client connection).
  8. If the client's TCP/IP transport allows telnet and ftp from the server, try these services as additional connectivity checks.
  9. Use the bpclntcmd utility to verify client to primary server communications. When the -pn and -sv options run on a client, they initiate inquiries to the primary server (configured in the server list on the client). The primary server then returns information to the requesting client.

    See About the bpclntcmd utility.

  10. Use the bptestbpcd utility to try to establish a connection from a NetBackup server to the bpcd daemon on another NetBackup system. If successful, it reports information about the sockets that are established.

    A complete description of bptestbpcd is in the NetBackup Commands Reference Guide.

  11. Verify that the client operating system is one of those supported by the client software.

Feedback

Was this page helpful?
Previous

Resolving network communication problems with UNIX clients

Next

Troubleshooting vnetd proxy connections

Feedback

Was this page helpful?