Windows client is not resolving alias name as a valid server

[Jesse_Holloman]

When the master or media server attempts to connect to the client using one of the alias names or the FQN (ie: master1.domain1.com) it gets error code 59 .

(not recognized as a valid server).

Is there any way to get the client to recognize the alias name as a valid server without adding every possible alias to every client ?  

Help in understanding the rules that apply here  or resolution would be greatly appreciated.

Here is what the configuration looks like.

MASTER

bash-3.2$ sudo nbemmcmd -machinealias -getaliases -machinename master1 -machinetype master
NBEMMCMD, Version:7.1
The following aliases were found for the alias: "master1"
11.111.11.11
master1
master1.domain1.com
master1.domain2.com
master1.domain3.com
 

Windows client has these entries in the server list.

master1

media1

media2

media3

[revarooo]

Jesse,

What IP address is the media and master server coming into the client with?

Find out then ensure that resolves back to a hostname that is in the SERVER list.

[J_H_Is_gone]

have dns setup with the alias names

example

M:\>nslookup myserver
Server:  dnsserver.maindomain.com
Address:  xx.x.xxx.xx

Name:    myserver.otherdomain.com
Address:  xx.xxx.x.xxx
Aliases:  myserver.maindomain.com

if you can get dns setup correctly you should work just fine.

[Jesse_Holloman]

It does resolve back to the alias name.

and it is in dns with FQN an shortname.

master1 and  master1.domain1.com  resolve back to the same ip on both client and master.

[revarooo]

Is the alias name in the bp.conf as a SERVER = aliashostname 

??

[Jesse_Holloman]

Unfortunately these are windows clients so there is no bp.conf.

But they do appear in the server list in the client gui.

[Jesse_Holloman]

I think this is a real problem.  All of the defined aliases are  being ignored.

[revarooo]

Ok, bring up the NEtBackup Admin GUI:

Click on Host Properties -> Clients -> <name of the client> open up the properties then click on Servers

Is the alias name and the hostname of the media server in there? If not add both.

Also ensure the client can resolve both names (alias and hostname).

On client what does this output give you?

bpclntcmd -hn <alias_name_of_media>

bpclntcmd -hn <normal_name_of media>

[J_H_Is_gone]

if your master and media server reside in mediaserver.maindomain.com

than that name needs to be in the other server list for the client (gui /client properties /servers)

from the master server do an nslookup of your client - does it come back with client.otherdomain.com

then you can put that name in the policy for the client.

from the master server go to client properties for the client and check the client name - it should have the clients name either short or long will work.

now log into the client

do a nslookup for the master server and the media server - then do the lookup for their ip address.

do the master and the media server come back? do they have an alias set up they should show otherdomain as well as maindomain

quite often when I get new clients in another domain - I have to make sure the dns guys add my master and media server to dns in the new domain.  If you cannot do a nslookup of the master and media server from the clients domain than it will never work.

[Marianne]

Neither master nor media server connects to client using a hostname.
Only IP address arrives at client during connection attempt.
Now client tries to resolve incoming IP address to hostname.
Next, client tries to find resolved hostname in SERVER list in registry.
If resolved name cannot be found in SERVER list, connection attempt is rejected (status 59).

Please do the following:

Create bpcd log folder on client under ...\netbackup\logs.

Try to connect again from master and media server (you can use 'bptestbpcd -client <client-name> -debug -verbose')
Check client's bpcd log file for incoming IP and how this is resolved to hostname and then compared with SERVER entries.
To fix SERVER entries, you can open NBU Backup, Archive & Restore GUI on client. Go to File ->  Specify NetBackup Machines. Add additional SERVER entry/entries based on what you saw in bpcd log file. This will update registry entries.