Forum Discussion

Kaio_Tonheiro's avatar
Kaio_Tonheiro
Level 4
9 years ago

Error 58

I need help with error 58 (can't connect to client), which says it can not connect to the client, however, client connection through ping tests to the master are ok, and the master to the client is also ok, how else can I perform solution to this problem ???

Master connected to the client through mstsc and everything is ok.

7.5
Backup and Recovery
Error messages
NetBackup
Windows Server (2003-2008)
  • sdo's avatar
    sdo
    9 years ago

    If this fails:

    # telnet client-name.com 1556

    ...then your issue is at least a firewall issue, and not necessarily a NetBackup issue.  If that command fails then there is either software FW on client, or a hardware FW in the LAN network.

5 Replies

Sort By
  • sdo's avatar
    sdo
    Moderator
    9 years ago

    If this fails:

    # telnet client-name.com 1556

    ...then your issue is at least a firewall issue, and not necessarily a NetBackup issue.  If that command fails then there is either software FW on client, or a hardware FW in the LAN network.

  • Marianne's avatar
    Marianne
    Level 6
    9 years ago
    NetBackup needs two things to ensure connectivity : 1. Forward and reverse name lookup between master and client and between client and server(s). If you have media servers, then everything applies to those as well. 2. Port connectivity between server(s) and client in both directions. NBU 7.5 needs port 1556 in both directions. Check that Windows firewall is disabled.
  • Michael_G_Ander's avatar
    Michael_G_Ander
    Level 6
    9 years ago

    Check that Netbackup Client Service and Symantec Private Branch is started on the client

    Go through the steps in this post:

    https://www.veritas.com/community/forums/general-connectivity-troubleshooting-status-23242558-often-6

    Remember that connections actually is

    Master        Client

    high port -> 1556

    1556 <- high port

    Seen from a firewall perspetive, especially important if there is a "hardware" firewall like an ASA or Checkpoint along the network path.

     

     

     

  • TS10's avatar
    TS10
    Level 3
    9 years ago

    check if the server name along with the IP exist in the host file.The entry should in both master as well in media server.

    secondly check telnet on the server

  • sdo's avatar
    sdo
    Moderator
    9 years ago

    Thanks Kaio.

    To be fair, that command could also fail:

    i) if there is a "name to IP" translation issue

    AND/OR

    ii) a LAN gateway/routing issue

    AND/OR

    iii) the client is powered off.

    .

    But most typically it's a FW issue  :)

    .

    Need some help with example commands for Windows FW, and/or Linux FW rule addition?