from the client, can you run a traceroute to that hostname for master? Can
you do the same for the ip?
Couple of things to check, make sure ip/hostname of master is first in
client bp.conf and also in host file on client, and host file on master.
Does bplcntcmd -pn work? The master does not  have to be in dns to resolve
with the client command, it just has to be in the proper places. Does the
client that works on the same subnet or a different one. If it is different,
then the configuration is probably different, meaning the client failing
uses another defined hostname for backups.  I have a setup much like this
right now. Let me know if I can help. I have many more ways to troubleshoot
problems like this.


-djb



-----Original Message-----
From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu]On Behalf Of Lewick,
Taylor
Sent: Tuesday, May 25, 2004 10:00 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] bpclntcmd on Solaris 2.6 client fails


I can't get NetBackup to connect to an older Solaris 2.6 Server.
The client is patched, and the correct version netbackup client software
is installed, and looks fine, all networking issues are fine, DNS,
TCP/IP etc.

But whenever I try to do a bpclntcmd -hn master_server, I get the
following error message,
gethostbyname failed for master-server.

If I do this to another Soalris 2.6 machine in our environment, it works
fine.  Does anyone know if this is a known issue and if there is a patch
from either Solaris/Veritas that fixes this?

Thanks,
Taylor


_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu