bpclntcmd -pn showing no output on the windows client

[Ankur_Kumar]

Hi guys

I am doing a bpclntcmd -pn on the windows client box, but it does not throw any output even when the
1) the master server name is there in the SERVER tab
2) the master server entry is there in the host file both the short name and the FQDN
3)telnet from the master on the client can be established on port 13782
4) telnet from the client to the master can be established on port 13720
5) bpclntcmd -self resolves to current hostname perfectly, no dichotomy here

and the backups are happening successfully for the client.

Looking forward to your help and support in these regard.

Chiao
Ankur Kumar

[Stumpr2]

client entry in the local master's host file?

[Ankur_Kumar]

Hi Bob,
The client entry is available in the master host file.

Chiao
Ankur Kumar

[Stumpr2]

Do you have the client configured into a policy?

Example of successful response: Master server = master Client server = client
The Command is run on client.
C:\Program Files\VERITAS\NetBackup\bin>bpclntcmd -pn
expecting response from server master
client.domain.com client 10.82.108.42 1117

where:
"expecting response from server master" returns the master server entry from the server list on the client.
"client.domain.com client 10.82.108.42 1117" is the connection name (peername) returned by the master server. The master server obtained this name through "gethostbyaddr()"
Client is client name configured in the NetBackup class client list.
10.82.108.42 is the IP address of the client connection.
1117 is the port number of the connection on the client.

[Ankur_Kumar]

Bob, the client is configured in the policy as well as the master server entry is available in the server list on the client side.

Wier issue mate.

[Stumpr2]

running out of ideas here..
Check the actual registry entries? any typo's?

[Anton_Panyushki]

You know, fellows.

I have the same problem

On the master server side
root@master # ping -s ms-client
PING ms-client: 56 data bytes
64 bytes from ms-client (192.168.xx.xx): icmp_seq=0. time=1 . ms
64 bytes from ms-client (192.168.xx.xx): icmp_seq=1. time=0 . ms
64 bytes from ms-client (192.168.xx.xx): icmp_seq=2. time=0 . ms
^C
----ms-client PING Statistics----
3 packets transmitted, 3 packets received, 0% packet loss
round-trip (ms) min/avg/max = 0/0/1
root@master # bpgetconfig -s ms-client
Client of master
PC, Windows2000
6.0.0
NetBackup
6.0
600000
C:\Program Files\VERITAS\NetBackup\bin
WindowsNET 5
root@master # telnet ms-client bpcd
Trying 192.168.xx.xx...
Connected to ms-client
Escape character is '^]'.
^CConnection to ms-client closed by foreign host.
root@master # bptestbpcd -client ms-client
1 1 1
192.168.xx.xx:49558 -> 192.168.xx.xx:13724
192.168.xx.xx:51795 -> 192.168.xx.xx:13724
192.168.xx.xx:51986 -> 192.168.xx.xx:13724

I can sucessfully resolve client name and client Ip-address from master server.


============================================================

On the client side

In the bpcd log there is a strange and ambiguous message
10:58:27.414 [15188.15328] <16> bpcd main: read failed: The operation completed successfully.

These guys At Symantec really know how to write logs. ;)
C:\Program Files\VERITAS\NetBackup\bin>bpclntcmd -self
gethostname() returned: ms-pieeai001
host ms-pieeai001: client at 192.168.xx.xx (0x31b3a8c0)
checkhname: aliases:

C:\Program Files\VERITAS\NetBackup\bin>bpclntcmd -sv

C:\Program Files\VERITAS\NetBackup\bin>
C:\Program Files\VERITAS\NetBackup\bin>
C:\Program Files\VERITAS\NetBackup\bin>bpclntcmd -pn
expecting response from server master

I don't know how to interprete all this output.

[Amit_Karia]

Do you have multile interfaces on your client or master server??

[rj_nbu]

 Anton,

From the master server , you are checking connectivity for server name  ms-client
whereas on the client, bpclntcmd -self returns   ms-pieeai001


-Rajeev

[Srikanth_Gubbal]

i agree with rajeev and amit; what they were questioning is related to the issue,
bpclntcmd -self gives a different host name on the client.
so if you have multiple hostnames and interfaces; enter those details in bp.conf and /etc/host
once add it ; try to ping your master server; see if it resolves on correct name; then try telnet; then try bpclntcmd -pn
if all these are not working; get an DNS entry for that server.

i have faced same problem; but i can give u complete solution only with more details.

[Anton_Panyushki]

This trouble has surprisingly vanished. It is a pure magic. Concerning hostname mismatch - it is solely my fault or, more precisely a slip of a pen, in attemt to disclose real host names. It is now real naming error.