Forum Discussion

nbustarter380's avatar
13 years ago

The status code 58 Can’t connect to client

I am having a issue with a Windows Client not backing up, I installed the NBU 7.1 client on a Windows 2008 server but's its not connecting to the master server.

  When I go to host properties then client the client list then SELECT the Client I  get the following

 “cannot connect on socket”

I can ping the client from the master server and I can ping the client from the NBU master servert

 The firewalls are turned off  can any give me some advice on what I might try to solve this issue?

 

Thanks

  • Thanks to all who responded!

     

    It turns out the IP address the clien was using needed to be put in the firewall rules after all.

6 Replies

  • Ensure the NetBackup Client service is running on the client

     

    Check that the client can resolve the master to the correct IP and the IP resolves back to the correct master name.

    Check that the master server can resolve the clients hostname to the correct IP address and it can resolve the IP address back to the client name.

    Run this from the Master

    bptestbpcd -client <clientname> -verbose

    what is the result?

    telnet <client> 1556

    telnet <client> 13724

    Does it connect?

  • Thanks revaroo,

     

    when I ran this >>> bptestbpcd -client <clientname> -verbose  from the master I got the following

      [root@nbuserver2 ~]# bptestbpcd -client daylight1.dov.state.ny.us -verbose

    <16>bptestbpcd main: Function ConnectToBPCD(daylight1.dov.state.ny.us) failed: 25

    cannot connect on socket

    I ran the following from the master also

    telnet <client> 1556

    telnet <client> 13724

    here are the results

     root@nbuserver2 ~]# telnet daylight1 1556

    daylight1/1556: Name or service not known

    [root@nbuserver2 ~]# telnet daylight1.dov.state.ny.us  1556

    Trying 10.77.12.21...

    telnet: connect to address 10.77.12.21: Connection timed out

    telnet: Unable to connect to remote host: Connection timed out

    [root@nbuserver2 ~]# telnet daylight1.dov.state.ny.us  13724

    Trying 10.77.12.21...

    telnet: connect to address 10.77.12.21: Connection timed out

    telnet: Unable to connect to remote host: Connection timed out

    [root@nbuserver2 ~]#

    Thanks

  • Have you tried traceroute and ping. You need to look at netstat and other networking troubleshooting techniques. This is obviously not an NBU problem, but a network problem. Few people realise that NetBackup is one of the best network trouble finders. :)

    Regards,

     

  • First of all ensure that Windows Firewall is indeed disabled on the client.

    Confirm that the following services are running on the client:
                    NetBackup Client Service
                    NetBackup Legacy Client Service
                    NetBackup Legacy Network Service
                    Symantec Private Branch Exchange

    When forward and reverse lookup has been confirmed between server and client using nslookup with hostname an ip address in both directions, do the following:

    Create bpcd log folder on client in <install-path>\netbackup\logs.

    Run the following on master/media server:

    bptestbpcd -client <client-name> -verbose -debug

    Please post output of bptestbpcd as well as client's bpcd log file.

    If client cannot resolve server IP address to valid hostname that appears in Client's SERVER list, either fix reverse lookup in DNS or add server to client's hosts file.

     

  • Thanks,

    Marianne, Patrick for your repsonses

     From the Windows client server

    D:\Program Files\Veritas\NetBackup\bin>bpclntcmd -hn  nbupower2.oit.state.ny.us

    host nbupower2.oit.state.ny.us: nbupower2.oit.state.ny.us at 10.25.21.36

    host nbupower2.oit.state.ny.us: nbupower2.oit.state.ny.us at 10.23.21.36

    aliases:     nbupower2.oit.state.ny.us     10.23.21.36     10.25.21.36

     

    D:\Program Files\Veritas\NetBackup\bin>bpclntcmd -self

    gethostname() returned: sungtong1.pr.state.ny.us

    host sungtong1.pr.state.ny.us: Sungtong1.pr.state.ny.us at ::1

    host sungtong1.pr.state.ny.us: Sungtong1.pr.state.ny.us at 10.62.12.21

    aliases:     Sungtong1.pr.state.ny.us     ::1     10.62.12.21

     

    D:\Program Files\Veritas\NetBackup\bin>bpclntcmd -pn

    expecting response from server nbupower2.oit.state.ny.us

    sungtong1.pr.state.ny.us sungtong1.pr.state.ny.us 10.62.12.21 50071

     

    D:\Program Files\Veritas\NetBackup\bin>bpclntcmd -ip nbupower2.oit.state.ny.us

    host nbupower2.oit.state.ny.us: nbupower2.oit.state.ny.us at 10.25.21.36

    host nbupower2.oit.state.ny.us: nbupower2.oit.state.ny.us at 10.23.21.36

    aliases:     nbupower2.oit.state.ny.us     10.23.21.36     10.25.21.36

     

    From the nbumaster server

     

     [root@nbupower2 ~]# ping sungtong1.pr.state.ny.us

    PING sungtong1.pr.state.ny.us (10.62.12.21) 56(84) bytes of data.

    64 bytes from sungtong1.pr.state.ny.us (10.62.12.21): icmp_seq=1 ttl=125 time=1.63 ms

    64 bytes from sungtong1.pr.state.ny.us (10.62.12.21): icmp_seq=2 ttl=125 time=1.44 ms

    64 bytes from sungtong1.pr.state.ny.us (10.62.12.21): icmp_seq=3 ttl=125 time=1.45 ms

     

    nslookup

     --- sungtong1.pr.state.ny.us ping statistics ---

    6 packets transmitted, 6 received, 0% packet loss, time 5000ms

    rtt min/avg/max/mdev = 1.464/1.519/1.581/0.066 ms

    [root@nbupower2 ~]# nslookup sungtong1.pr.state.ny.us

    Server:         10.26.16.23

    Address:        10.26.16.23#53

     Name:   sungtong1.pr.state.ny.us

    Address: 10.62.12.21

     

     Telnet

     [root@nbupower2 ~]# telnet sungtong1 bpcd

    sungtong1/bpcd: Name or service not known

    [root@nbupower2 ~]# telnet sungtong1.pr.state.ny.us bpcd

    Trying 10.62.12.21...

    telnet: connect to address 10.62.12.21: Connection timed out

    telnet: Unable to connect to remote host: Connection timed out

    [root@nbupower2 ~]#

      Notice this result from the master nbuserver

      [root@nbupower2 ~]# telnet sungtong1 bpcd

    sungtong1/bpcd: Name or service not known

    [root@nbupower2 ~]# telnet sungtong1.pr.state.ny.us bpcd

    Trying 10.62.12.21...

    telnet: connect to address 10.62.12.21: Connection timed out

    telnet: Unable to connect to remote host: Connection timed out

    [root@nbupower2 ~]# bptestbpcd -client sungtong1.pr.state.ny.us -verbose

    <16>bptestbpcd main: Function ConnectToBPCD(sungtong1.pr.state.ny.us) failed: 25

    cannot connect on socket

    [root@nbupower2 ~]#

     [root@nbupower2 ~]# bptestbpcd -client suntong1.pr.state.ny.us -verbose -debug  11:38:02.938 [32121] <2> bptestbpcd: VERBOSE = 0

    11:38:02.938 [32121] <2> ConnectionCache::connectAndCache: Acquiring new connection for host nbucore2, query type 223

    11:38:02.939 [32121] <2> logconnections: BPDBM CONNECT FROM 127.0.0.1.34953 TO 127.0.0.1.13721 fd = 3

    11:38:02.939 [32121] <2> vnet_get_user_credential_path: ../../libvlibs/vnet_vxss.c.1464: 0: status: 35 0x00000023

    11:38:02.939 [32121] <2> vnet_get_credential_path: ../../libvlibs/vnet_vxss.c.1094: 0: vnet_get_user_credential_path failed: 35 0x00000023

    11:38:02.939 [32121] <2> vnet_get_oc: ../../libvlibs/vnet_vxss_helper.c.3122: 0: Invalid Argument:: vxss_coninfo

    11:38:02.943 [32121] <2> db_CLIENTsend: reset client protocol version from 0 to 7

    11:38:02.983 [32121] <2> db_getCLIENT: db_CLIENTreceive: no entity was found 227

     

    Marianne, here is the output of the services that are running on the Windows 2008 client server

     

     COMMAND           PID      LOAD             TIME   MEM                  START

    vnetd           14068    0.000%            0.046  9.5M   4/30/12 09:36:25.687

    bpinetd         12388    0.000%            0.093   11M   4/30/12 09:36:25.749

    bpcd            13384    0.000%            0.078   10M   4/30/12 09:36:25.843

    bpps            15024    0.000%            0.577  8.2M   4/30/12 10:15:09.598

     

  • Thanks to all who responded!

     

    It turns out the IP address the clien was using needed to be put in the firewall rules after all.