can't connect to client

Question

hello all&nbsp;i have the status 58 in our netbackup (job failed) and look this command when i was maked&nbsp; and how you can advice me to troubleshooting the issue&gt;bptestbpcd.exe -client MPX-VM-NAVINT01 -verbose -debug14:59:18.771 [12420.13224] &lt;2&gt; bptestbpcd: VERBOSE = 014:59:19.802 [12420.13224] &lt;8&gt; async_connect: [vnet_connect.c:1709] getsockopt SO_ERROR returned 10061 0x274d14:59:21.443 [12420.13224] &lt;8&gt; vnet_vnetd_pbx_c_supported: [vnet_vnetd.c:3508] VN_REQUEST_PBX_C_SUPPORTED 13 0xd14:59:21.474 [12420.13224] &lt;8&gt; do_vnetd_service: [vnet_connect.c:2036] remote host supports PBX, but PBX is not running 0 0x014:59:21.474 [12420.13224] &lt;8&gt; vnet_vnetd_service_socket: [vnet_vnetd.c:2030] VN_REQUEST_SERVICE_SOCKET 6 0x614:59:21.474 [12420.13224] &lt;8&gt; vnet_vnetd_service_socket: [vnet_vnetd.c:2044] service bpcd14:59:21.599 [12420.13224] &lt;2&gt; logconnections: BPCD CONNECT FROM 10.0.100.20.62200 TO 10.0.112.250.13724 fd = 64014:59:22.630 [12420.13224] &lt;8&gt; async_connect: [vnet_connect.c:1709] getsockopt SO_ERROR returned 10061 0x274d14:59:24.521 [12420.13224] &lt;8&gt; vnet_vnetd_pbx_c_supported: [vnet_vnetd.c:3508] VN_REQUEST_PBX_C_SUPPORTED 13 0xd14:59:24.552 [12420.13224] &lt;8&gt; do_vnetd_service: [vnet_connect.c:2036] remote host supports PBX, but PBX is not running 0 0x014:59:24.552 [12420.13224] &lt;8&gt; do_vnetd_service: [vnet_connect.c:2072] connect VNETD CONNECT FROM 10.0.100.20.62203 TO 10.0.112.250.13724 fd = 66014:59:24.552 [12420.13224] &lt;8&gt; vnet_vnetd_connect_forward_socket_begin: [vnet_vnetd.c:455] VN_REQUEST_CONNECT_FORWARD_SOCKET 10 0xa14:59:24.552 [12420.13224] &lt;8&gt; vnet_vnetd_connect_forward_socket_begin: [vnet_vnetd.c:480] ipc_string 2327914:59:24.599 [12420.13224] &lt;2&gt; ConnectToBPCD: bpcd_connect_and_verify(MPX-VM-NAVINT01, MPX-VM-NAVINT01) failed: 4614:59:25.630 [12420.13224] &lt;8&gt; async_connect: [vnet_connect.c:1709] getsockopt SO_ERROR returned 10061 0x274d14:59:27.568 [12420.13224] &lt;8&gt; vnet_vnetd_pbx_c_supported: [vnet_vnetd.c:3508] VN_REQUEST_PBX_C_SUPPORTED 13 0xd14:59:27.630 [12420.13224] &lt;8&gt; do_vnetd_service: [vnet_connect.c:2036] remote host supports PBX, but PBX is not running 0 0x014:59:27.630 [12420.13224] &lt;8&gt; vnet_vnetd_service_socket: [vnet_vnetd.c:2030] VN_REQUEST_SERVICE_SOCKET 6 0x614:59:27.630 [12420.13224] &lt;8&gt; vnet_vnetd_service_socket: [vnet_vnetd.c:2044] service bpcd14:59:27.662 [12420.13224] &lt;2&gt; logconnections: BPCD CONNECT FROM 10.0.100.20.62207 TO 10.0.112.250.13724 fd = 64014:59:28.693 [12420.13224] &lt;8&gt; async_connect: [vnet_connect.c:1709] getsockopt SO_ERROR returned 10061 0x274d14:59:30.615 [12420.13224] &lt;8&gt; vnet_vnetd_pbx_c_supported: [vnet_vnetd.c:3508] VN_REQUEST_PBX_C_SUPPORTED 13 0xd14:59:30.646 [12420.13224] &lt;8&gt; do_vnetd_service: [vnet_connect.c:2036] remote host supports PBX, but PBX is not running 0 0x014:59:30.646 [12420.13224] &lt;8&gt; do_vnetd_service: [vnet_connect.c:2072] connect VNETD CONNECT FROM 10.0.100.20.62211 TO 10.0.112.250.13724 fd = 66014:59:30.646 [12420.13224] &lt;8&gt; vnet_vnetd_connect_forward_socket_begin: [vnet_vnetd.c:455] VN_REQUEST_CONNECT_FORWARD_SOCKET 10 0xa14:59:30.646 [12420.13224] &lt;8&gt; vnet_vnetd_connect_forward_socket_begin: [vnet_vnetd.c:480] ipc_string 2329114:59:30.693 [12420.13224] &lt;2&gt; local_bpcr_connect: got an exit status error message: &lt;?xml version="1.0" encoding="utf-8"?&gt;&lt;StatusMsgDoc&gt;&lt;StatusMsg NBUStatus="46" Severity="2" VXULoid="137" VXULtid="114"&gt;&lt;P pos="0"&gt;mpx-py-bkup02.snmvt.intra&lt;/P&gt;&lt;P pos="1"&gt;10.0.100.20&lt;/P&gt;&lt;P pos="2"&gt;MPX-VM-NAVINT01.snmvt.intra&lt;/P&gt;&lt;P pos="3"&gt;10.0.112.250&lt;/P&gt;&lt;MsgString&gt;Request&amp;#32;from&amp;#32;host&amp;#32;mpx-py-bkup02.snmvt.intra&amp;#32;(10.0.100.20)&amp;#32;to&amp;#32;host&amp;#32;MPX-VM-NAVINT01.snmvt.intra&amp;#32;(10.0.112.250)&amp;#32;is&amp;#32;not&amp;#32;allowed&amp;#32;access.&lt;/MsgString&gt;&lt;StatusMsg NBUStatus="46" Severity="0" VXULoid="137" VXULtid="115"&gt;&lt;P pos="0"&gt;mpx-py-bkup02.snmvt.intra&lt;/P&gt;&lt;P pos="1"&gt;10.0.100.20&lt;/P&gt;&lt;P pos="2"&gt;mpx-vm-navint01.snmvt.intra&lt;/P&gt;&lt;MsgString&gt;Host&amp;#32;mpx-py-bkup02.snmvt.intra&amp;#32;(10.0.100.20)&amp;#32;is&amp;#32;not&amp;#32;an&amp;#32;authorized&amp;#32;server&amp;#32;for&amp;#32;host&amp;#32;mpx-vm-navint01.snmvt.intra.&lt;/MsgString&gt;&lt;/StatusMsg&gt;&lt;/StatusMsg&gt;&lt;/StatusMsgDoc&gt;14:59:30.693 [12420.13224] &lt;2&gt; ConnectToBPCD: bpcd_connect_and_verify(MPX-VM-NAVINT01, MPX-VM-NAVINT01) failed: 46&lt;16&gt;bptestbpcd main: Function ConnectToBPCD(MPX-VM-NAVINT01) failed: 4614:59:30.709 [12420.13224] &lt;16&gt; bptestbpcd main: Function ConnectToBPCD(MPX-VM-NAVINT01) failed: 46&lt;16&gt;bptestbpcd main: Request from host mpx-py-bkup02.snmvt.intra (10.0.100.20) to host MPX-VM-NAVINT01.snmvt.intra (10.0.112.250) is not allowed access.Host mpx-py-bkup02.snmvt.intra (10.0.100.20) is not an authorized server for host mpx-vm-navint01.snmvt.intra.14:59:30.740 [12420.13224] &lt;16&gt; bptestbpcd main: Request from host mpx-py-bkup02.snmvt.intra (10.0.100.20) to host MPX-VM-NAVINT01.snmvt.intra (10.0.112.250) is not allowed access. Host mpx-py-bkup02.snmvt.intra (10.0.100.20) is not an authorized server for host mpx-vm-navint01.snmvt.intra.&lt;2&gt;bptestbpcd: server not allowed access14:59:30.771 [12420.13224] &lt;2&gt; bptestbpcd: server not allowed access&lt;2&gt;bptestbpcd: EXIT status = 4614:59:30.771 [12420.13224] &lt;2&gt; bptestbpcd: EXIT status = 46server not allowed accessI&nbsp;was&nbsp;searched&nbsp;more in the&nbsp;Veritas&nbsp;web can't&nbsp;&nbsp;fix&nbsp;this issue,please help&nbsp;

marianne · Accepted Answer

netbackup22&nbsp;
Now, please go back to your opening post and see what you posted there:
netbackup22&nbsp;wrote:
hello all&nbsp;
i have the status 58 in our netbackup (job failed) and look this command when i was maked&nbsp; and how you can advice me to troubleshooting the issue
&gt;bptestbpcd.exe -client MPX-VM-NAVINT01 -verbose -debug......

Why did you you perform bptestbpcd if you are doing agentless Hyper-V backup?&nbsp;We have waisted exactly one week trying to troubleshoot status 46 instead of status 58.
Can you please rather show us all the text in Activity Monitor details of the Status 58 job?&nbsp;(You may need to re-run the policy that had this error because the failed backup from a week ago will be gone from Activity Monitor.)

marianne · Answer

netbackup22&nbsp;
Did you install NBU Client software on&nbsp;mpx-vm-navint01 ?&nbsp;(It seems you or someone else did.)
Is&nbsp;mpx-py-bkup02 your master server or a media server?&nbsp;
When you installed the software, there was&nbsp; a screen where it asked for Master Server Name and Additional servers, right?&nbsp;Was&nbsp;mpx-py-bkup02.snmvt.intra&nbsp;added in the Master Server or Additional Server text box?&nbsp;
When you do that, it add the host names into the registry of the client as Server names.&nbsp;(Computer\HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\NetBackup\CurrentVersion\Config)Maybe the Server Name was added as&nbsp;mpx-py-bkup02, not as&nbsp;mpx-py-bkup02.snmvt.intra.&nbsp;
What is happening now is that client mpx-vm-navint01 is receiving a connection request from&nbsp; server&nbsp;mpx-py-bkup02 IP address -&nbsp;10.0.100.20. The client now tries to resolve the IP address to a hostname.&nbsp;On this client, it resolves the IP address to hostname&nbsp;mpx-py-bkup02.snmvt.intra.Next, it checks the NetBackup Server entries in it's own registry.&nbsp;If hostname&nbsp;mpx-py-bkup02.snmvt.intra is not listed as a Server, the connection request is rejected. Status 46.&nbsp;
You need to add&nbsp;mpx-py-bkup02.snmvt.intra in the Client's Server entries.&nbsp;
Please read up in NBU Admin Guide I chapter 3 about Host Properties.&nbsp;

sdo · Answer

Status 58 can be caused by many things, such as: no route to client, hosts file entry overrides DNS entry, hosts file entry has wrong IP, DNS name has wrong IP, client is down, client powered-off, client lost networking, client changed IP, ports not open across firewall, client not installed, client stopped, client un-installed, VM was deleted, network cable fallen out of back of physical server, someone crept into the data centre and has stolen the server... anyway, status 58 effectively means that the server was unable, for whatever reason, to reach the client... my advice is start by checking name resolution and then check network path and then check firewall(s) on backup server and on backup client and on network hardware / switches / routers / firewalls.

But you have status 46.

sdo · Answer

One example of solution is here, from&nbsp;Marianne&nbsp;https://vox.veritas.com/t5/NetBackup/Status-46-server-not-allowed-access/td-p/351889&nbsp;

marianne · Answer

netbackup22&nbsp;
The problem is actually very clear from the output that posted:
Request from host mpx-py-bkup02.snmvt.intra (10.0.100.20) to host MPX-VM-NAVINT01.snmvt.intra (10.0.112.250) is not allowed access.Host mpx-py-bkup02.snmvt.intra (10.0.100.20) is not an authorized server for host mpx-vm-navint01.snmvt.intra.
So, this means that there is no SERVER entry for&nbsp;mpx-py-bkup02.snmvt.intra on host&nbsp;mpx-vm-navint01.snmvt.intra
Have you tried to add Server entry?&nbsp;

netbackup22 · Answer

hello&nbsp; i don't understand&nbsp; "no SERVER entry for&nbsp;mpx-py-bkup02.snmvt.intra&nbsp;on host&nbsp;mpx-vm-navint01.snmvt.intra"&nbsp;how can i add ? please&nbsp; (it men to add the ip&nbsp;@ of mpx-py-bacup02.snmvt.intra into /et/host of mpx -vm-navint01.snmavti.intra ) but the vm mpx-vm-navint01 in hyper-v

Forum Discussion

can't connect to client

12 Replies

Related Content

Client can't connect

Cannot connect to client

Status 58 = can't connect to client.

Error connecting to the client

New LINUX client connect failure

Recent Discussions

Data migration for LTR images of 3 clients

Installing a New Media Server and Transferring the Media Server Role

Silent Uninstall Switch for Veritas NetBackup Client

How to update netbackup agent java version?

Netbackup 10.4 Malware Scanning Installation