Client can't connect

[Andre_Torres]

Hi everybody,

I made a installation in a HP-UX client, the installation gives me ok, but in the master server it gives me that it cannot connect to client. First I thought it was firewall, but the server administrator said it doesn't have a I firewall in this server. Tried telnet from master to this server and connected to port 13724. Ping works.

So I tried another test, pick the java administration console on my desktop and tried to connect to this server. Didn't work. Try to execute jnbSA with putty and Xming, and worked. With this window open, I've tried to make a manual backup, it gives me VxSS authentication error.

Both Master and Client HP-UX 11.31 in 7.5.0.4.

[Marianne]

Your Connect Options have been modified:

Connect options:        1 0 2

See mine (NBU defaults, using NBU 7.5.0.4 on server and my laptop):

bpclient -client Marianne-Win7 -L

Connect options:        2 2 3

/root >bptestbpcd -client Marianne-Win7 -verbose

1 1 1

10.1.1.130:39943 -> 10.1.1.105:1556

10.1.1.130:59038 -> 10.1.1.105:1556

PEER_NAME = master

HOST_NAME = marianne-win7

CLIENT_NAME = marianne-win7

VERSION = 0x07500004

PLATFORM = win_x64

PATCH_VERSION = 7.5.0.4

SERVER_PATCH_VERSION = 7.5.0.4

MASTER_SERVER = master

EMM_SERVER = master

NB_MACHINE_TYPE = MEDIA_SERVER

10.1.1.130:36202 -> 10.1.1.105:1556

See Commands Manual about meaning of Connect Options  (I have highlighted your settings):

-connect_options 0|1|2 0|1|2 0|1|2|3
 

First set of arguments, Ports, represents the following:

0 = Reserved Port: Use a reserved port number.

1 = Non-reserved Port: Connect to the client’s bpcd by using a non-reserved

port number. If you select this option, enable Allow Nonreserved Ports for

the selected client.

2 = Use Default: Use Default is the default. Use the value that the

DEFAULT_CONNECT_OPTIONS configuration entry on the server defines.

The second set of arguments, BPCD Connect Back, represents the following:

0 = Random Port: NetBackup randomly chooses a free port in the allowed

range to perform the traditional connect-back method.

1 =VNETDport: This method requires no connect-back. The Veritas Network

Daemon (vnetd) was designed to enhance firewall efficiency with NetBackup

during server-to-server and server-to-client communications.

2 = Use Default: The default option. Use the value that the

DEFAULT_CONNECT_OPTIONS configuration entry on the server defines.

The third set of arguments (Daemon Connection Port) represents the

following:

0 = Automatic: This option means that VNETD is used if possible; otherwise

Legacy is used.

1 = Use the VNETD port.

2 = Use the Legacy port number.

3 = Use Default: The default option. Use the value that the

DEFAULT_CONNECT_OPTIONS configuration entry on the server defines.

The following means that the client is unable to connect to the master server via port 1556:

bpclntcmd -pn:

didn't do nothing

Client's attempt to connect should be logged in master's bprd log.

Have you tried to remove the client software and reinstall? Seems you've been having problems with software installation in your environment...

[Andre_Torres]

Called support, but they couldn't solve the problem. They said it was that the machine was overloaded with connections. He asked logs, and asked to wait for the night backup.

Solved the problem in the simpliest way, killing the directory openv and reinstalling it. I didn't done this in the  first place because there was a lot of scripts (created by the DBA) running under openv.

[Marianne · Accepted solution]

So - you have followed my advice in my previous post??

Have you tried to remove the client software and reinstall? Seems you've been having problems with software installation in your environment...