After enabling VOPIE on a Windows Client, the backup fails with Status 58: The server was unable to connect to the client.

Article:TECH52513  |  Created: 2007-01-04  |  Updated: 2008-01-03  |  Article URL http://www.symantec.com/docs/TECH52513
Article Type
Technical Solution


Environment

Issue



After enabling VOPIE on a Windows Client, the backup fails with Status 58: The server was unable to connect to the client.

Error



Error bpbrm(pid=6672) cannot connect to client_name, An existing connection was forcibly closed by the remote host. (10054)
can't connect to client(58)

Solution



The Master Server is unable to communicate with the Client after VOPIE was enabled.

To troubleshoot the Master Server execute the following command (the result will display in the cmd window):

Windows:
D:\Program Files\VERITAS\NetBackup\bin\admincmd>bpauthorize -M client_name -debug -verbose
<16>bpauthorize main: Function connect_to_remote_server(client_name) failed: 25
<2>bpauthorize: cannot connect on socket
<2>bpauthorize: EXIT status = 25
cannot connect on socket

Check client bpcd log:

<2> bpcd main: offset to GMT 18000
<2> bpcd main: Got socket for input 448
<2> logconnections: BPCD ACCEPT FROM 10.66.16.25.620 TO 10.66.16.26.13782
<2> bpcd main: setup_sockopts complete
<2> vauth_acceptor: ..\libvlibs\vauth_comm.c.364: Function failed: 15 0x0000000f
<16> bpcd main: authentication failed: 15

These two indications point to a problem with name resolution on the Master Server.

On the Master Server open methods_allow.txt file.
Example contents:

vopie : master_server_name
vopie : client_name

Using the client name, execute bpclntcmd -hn client_name
Record the IP address.

Next, execute bpclntcmd -ip <ipaddress>

This should return the same host name that's in methods_allow.txt file.
In this example the name was different than the client_name.

Corrective action:
Modify DNS or the Master Server hosts file to ensure that the correct host name and IP address of the client named in the methods_allow.txt file is present.

Once the hosts file has the correct records execute bpauthorize.exe
Example:

D:\Program Files\VERITAS\NetBackup\bin\admincmd>bpauthorize -M client_name -debug -verbose
vopie_vauth.c.263: Function vauth_set_port_window_function: min_port = <0>
vopie_vauth.c.265: Function vauth_set_port_window_function: max_port = <0>
vopie_vauth.c.269: Function vauth_set_port_window_function: vopie_min_port = <0>
vopie_vauth.c.271: Function vauth_set_port_window_function: vopie_max_port = <0>
vopie_vauth.c.91: Function vauth_connect_function: user_name = <:Administrator>
vopie_private.c.88: Function vopie_admin_user: user = <:Administrator>
vopie_path.c.411: Function vopie_read_key_file: path = <D:\Program Files\VERITAS\NetBackup\var\auth\vopie\unhashed\master_name\client_name.txt>
vopie_path.c.427: Function vopie_read_key_file: key = <jXiy>@.>"otY-$I=TQw*50B(/koK1NJAT79g"^^GP&?`v%W<5Rc~l=U8>
vopie_path.c.557: Function vopie_get_secret_key: key = <jXiy>@.>"otY-$I=TQw*50B(/koK1NJAT79g"^^GP&?`v%W<5Rc~l=U8>
vopie_challenge.c.102: Function vopie_answer_challenge: challenge = <otp-md5 452 ha3000 ext>
vopie_challenge.c.103: Function vopie_answer_challenge: key = <jXiy>@.>"otY-$I=TQw*50B(/koK1NJAT79g"^^GP&?`v%W<5Rc~l=U8>
vopie_challenge.c.108: Function vopie_answer_challenge: response = <DF86 5975 BCB5 5CFE>
vopie_path.c.302: Function vopie_get_key_file: tempnam path = <D:\Program Files\VERITAS\NetBackup\var\auth\vopie\hashed\master_name\856236281856036vopie2>
IS_SERVER = 1
IS_MEDIA_SERVER = 1
IS_ADMIN = 1
IS_OPERATOR = 1
AUTHENTICATION_REQUIRED = 1
<2>bpauthorize: EXIT status = 0

Client bpcd log:

<2> bpcd main: offset to GMT 18000
<2> bpcd main: Got socket for input 460
<2> logconnections: BPCD ACCEPT FROM 10.66.16.25.582 TO 10.66.16.26.13782
<2> bpcd main: setup_sockopts complete
<2> bpcd main: authentication method: 128, local_name = client_name, remote_name = master_server, user_name = :Administrator
<2> bpcd peer_hostname: Connection from host master_server (10.66.16.25) port 582
<2> bpcd valid_server: comparing master_server and master_server
<4> bpcd valid_server: hostname comparison succeeded
<2> bpcd main: output socket port number = 13782
<2> vnet_vnetd_pop_ipaddr: ..\libvlibs\vnet_vnetd.c.1606: ip_len: 4 0x00000004
<2> vnet_vnetd_pop_ipaddr: ..\libvlibs\vnet_vnetd.c.1622: bptr[i]: 10 0x0000000a
<2> vnet_vnetd_pop_ipaddr: ..\libvlibs\vnet_vnetd.c.1622: bptr[i]: 66 0x00000042
<2> vnet_vnetd_pop_ipaddr: ..\libvlibs\vnet_vnetd.c.1622: bptr[i]: 16 0x00000010
<2> vnet_vnetd_pop_ipaddr: ..\libvlibs\vnet_vnetd.c.1622: bptr[i]: 25 0x00000019
<2> vnet_vnetd_pop_ipaddr: ..\libvlibs\vnet_vnetd.c.1629: port: 13724 0x0000359c
<2> vnet_vnetd_connect_back_socket: ..\libvlibs\vnet_vnetd.c.248: ipc_string: 2673
<2> vnet_vnetd_connect_back_socket: ..\libvlibs\vnet_vnetd.c.296: hash_str1: e850decdcdc612a02aecd02949252d6c
<2> vnet_vnetd_connect_back_socket: ..\libvlibs\vnet_vnetd.c.309: status: 0 0x00000000
<2> vnet_vnetd_connect_back_socket: ..\libvlibs\vnet_vnetd.c.326: pushed hash_str1: e850decdcdc612a02aecd02949252d6c
<2> vnet_vnetd_connect_back_socket: ..\libvlibs\vnet_vnetd.c.340: pstatus: 0 0x00000000
<2> get_vnetd_socket: connected to vnetd socket 720
<2> bpcd main: Duplicated vnetd socket on stderr
<2> bpcd main: <---- NetBackup 5.1 0 ------------initiated
<2> bpcd main: Not using VxSS authentication with master_server  
<2> bpcd main:
<2> bpcd main: BPCD_GET_VERSION_RQST
<2> bpcd main: BPCD_GET_VERSION_RQST
<2> bpcd main: BPCD_GET_PRIVILEGES_RQST
<2> bpcd main: BPCD_DISCONNECT_RQST
<2> bpcd exit_bpcd: exit status 0  ----------->exiting

Note: This client is using VNETD.


Supplemental Materials

SourceError Code
Value58
Descriptioncan't connect to client, The server was unable to connect to the client.


Legacy ID



289796


Article URL http://www.symantec.com/docs/TECH52513


Terms of use for this information are found in Legal Notices