Forum Discussion

eric_lau's avatar
eric_lau
Level 3
12 years ago

server not allowed to connect (46)

I have my backup server able to ping to my client.

I can do the followings:

from the server

C:\Program Files\Veritas\NetBackup\bin>bpclntcmd -hn backupv-data
host backupv-data: backupv-data at 10.1.3.29
aliases:     backupv-data     10.1.3.29

C:\Program Files\Veritas\NetBackup\bin>bpclntcmd -ip 10.1.3.29
host 10.1.3.29: backupv-data at 10.1.3.29
aliases:     backupv-data     10.1.3.29

I also can do from the client:

C:\Program Files (x86)\VERITAS\NetBackup\bin>bpclntcmd -hn backup00-ndmp
host backup00-ndmp: backup00-ndmp at 10.1.2.19
aliases:     backup00-ndmp     10.1.2.19

 

However I can't connect to the client from the server.

The following is the bpcd log for reference. Any help is appreciated.

----------------------

C:\Program Files\Veritas\NetBackup\bin\admincmd>bptestbpcd -client backupv-data
-verbose -debug > c:\bpcd.log
22:28:06.962 [6176.6532] <2> bptestbpcd: VERBOSE = 0
22:28:06.977 [6176.6532] <2> vnet_pbxConnect: pbxConnectEx Succeeded
22:28:06.977 [6176.6532] <2> logconnections: BPCD CONNECT FROM 10.1.3.39.60957 T
O 10.1.3.29.1556 fd = 516
22:28:06.977 [6176.6532] <2> vnet_pbxConnect: pbxConnectEx Succeeded
22:28:07.586 [6176.6532] <8> do_pbx_service: [vnet_connect.c:2108] via PBX VNETD
 CONNECT FROM 10.1.3.39.60958 TO 10.1.3.29.1556 fd = 536
22:28:07.586 [6176.6532] <8> vnet_vnetd_connect_forward_socket_begin: [vnet_vnet
d.c:443] VN_REQUEST_CONNECT_FORWARD_SOCKET 10 0xa
22:28:07.866 [6176.6532] <8> vnet_vnetd_connect_forward_socket_begin: [vnet_vnet
d.c:460] ipc_string 62768
22:28:08.350 [6176.6532] <2> ConnectToBPCD: bpcd_connect_and_verify(backupv-data
, backupv-data) failed: 46
<16>bptestbpcd main: Function ConnectToBPCD(backupv-data) failed: 46
22:28:08.350 [6176.6532] <16> bptestbpcd main: Function ConnectToBPCD(backupv-da
ta) failed: 46
<2>bptestbpcd: server not allowed access
22:28:08.350 [6176.6532] <2> bptestbpcd: server not allowed access
<2>bptestbpcd: EXIT status = 46
22:28:08.350 [6176.6532] <2> bptestbpcd: EXIT status = 46
server not allowed access

----------------------

 

 

 

  • Here you are doing forward lookup to hostname backup00-ndmp.

     bpclntcmd -hn backup00-ndmp

    This resolves to IP address 10.1.2.19.

    But in bptestbpcd output we see connection attempt from IP address 10.1.3.39 TO 10.1.3.29.

    Client's IP is on same subnet as server's 10.1.3 IP (assuming you have them separated ito different  subnets with 255.255.255.0 netmask):

    backupv-data     10.1.3.29

    This is why server is using the 10.1.3. interface to connect to client.

    Client cannot resolve server IP address  10.1.3.39 and there is no SERVER entry.

    If you want to use 10.1.2 network for backups, you need to add 10.1.2 IP address for client's backup NIC.

     

5 Replies

  • the following is my enviroment.

    Master server - Backup00

                          Two interfaces - backup00 and backup00-ndmp (not really for ndmp, it is just a dns name)

                                                     backup00 is the admin interface

                                                     backup00-ndmp is the backup vlan interface

     Client server - Backupv

                           Two interfaces - backupv and backupv-data

                                                      backupv is the admin interface

                                                      backupv-data is the backup vlan interface

    The master server interface backup00-ndmp is already specified in the Backup, Archiver and Restore client,

    But the client under Host Properties still said "Server not allowed access".

    Thanks.

     

     

     

     

     

     

  • What is the output of this command on the server

    bptestbpcd  -verbose -client <client name>

    Is the server listed as a 'SERVER' entry on the client ?

    Martin

  • Here you are doing forward lookup to hostname backup00-ndmp.

     bpclntcmd -hn backup00-ndmp

    This resolves to IP address 10.1.2.19.

    But in bptestbpcd output we see connection attempt from IP address 10.1.3.39 TO 10.1.3.29.

    Client's IP is on same subnet as server's 10.1.3 IP (assuming you have them separated ito different  subnets with 255.255.255.0 netmask):

    backupv-data     10.1.3.29

    This is why server is using the 10.1.3. interface to connect to client.

    Client cannot resolve server IP address  10.1.3.39 and there is no SERVER entry.

    If you want to use 10.1.2 network for backups, you need to add 10.1.2 IP address for client's backup NIC.

     

  • I did have 10.1.2.x network for the backup. The backupv-data interface is on that vlan. However it seems to me that when the backup started it did not go to the 10.1.2.x network. So I did a route add which seems is working fine now.