error code 54 - Veritas Net Backup

This is a discussion on error code 54 - Veritas Net Backup ; Hi, I have a master server (unix) and client server (w2k) in DMZ and have a error code 54 "client timeout connection" I check the all firewall ports (13720, 13721, 13722, 13723, 13724, 13782, 13783, 13701 and 13711) by telnet ...

+ Reply to Thread
Results 1 to 3 of 3

Thread: error code 54

  1. error code 54


    Hi,

    I have a master server (unix) and client server (w2k) in DMZ and have a error
    code 54 "client timeout connection"

    I check the all firewall ports (13720, 13721, 13722, 13723, 13724, 13782,
    13783, 13701 and 13711) by telnet and all opened.

    DNZ name resolution is fine.

    When I check the network status by netstat -an, it shows me
    " TCP 192.168.187.137:13782 192.168.181.40:548 ESTABLISHED"

    but I still have error code 54.

    Can anybody help me?

    THanks

    Kevin Kang

  2. Re: error code 54

    Were your telnet tests in both directions? If you have a separate media
    server, did you test also from the media server? Is the NetBackup
    Client Service running on the client? In an install reboot was noted,
    was it done? If you have turned logging up (and created appropriate
    directories on client & server), what do you see in the logs?

    cheers, wayne

    Kevin wrote, in part:
    > I have a master server (unix) and client server (w2k) in DMZ and have a error
    > code 54 "client timeout connection"
    >
    > I check the all firewall ports (13720, 13721, 13722, 13723, 13724, 13782,
    > 13783, 13701 and 13711) by telnet and all opened.
    >
    > DNZ name resolution is fine.
    >
    > When I check the network status by netstat -an, it shows me
    > " TCP 192.168.187.137:13782 192.168.181.40:548 ESTABLISHED"
    >
    > but I still have error code 54.


  3. Re: error code 54


    "W. T. Smith" wrote:
    >Were your telnet tests in both directions? If you have a separate media


    >server, did you test also from the media server? Is the NetBackup
    >Client Service running on the client? In an install reboot was noted,
    >was it done? If you have turned logging up (and created appropriate
    >directories on client & server), what do you see in the logs?
    >
    >cheers, wayne
    >
    >Kevin wrote, in part:
    >> I have a master server (unix) and client server (w2k) in DMZ and have

    a error
    >> code 54 "client timeout connection"
    >>
    >> I check the all firewall ports (13720, 13721, 13722, 13723, 13724, 13782,
    >> 13783, 13701 and 13711) by telnet and all opened.
    >>
    >> DNZ name resolution is fine.
    >>
    >> When I check the network status by netstat -an, it shows me
    >> " TCP 192.168.187.137:13782 192.168.181.40:548 ESTABLISHED"
    >>
    >> but I still have error code 54.


    From the client, try:

    bpclntcmd -pn [tests connection to the master server]

    bpclntcmd -hn media_server_name

    bpclntcmd -ip media_server_IP

    They should all come back OK. If not, the client configuration is not quite
    right.


    Scott

+ Reply to Thread