In regard to: [Networker] Networker Client Authentication Tru64 Unix,...:

unfortunately in our environment, hardware to test air-traffic-control
software, we have to deal with non-unique hostnames and sometimes
ip-adresses as well. That is because the software must be tested on a
hardware environment absolutely identical to the operative systems,
before it is verified to go to the operative systems. Because of these
circumstances, we have to deal with clients (tru64 4.0f) which are
connected to a Networker Backup-Server on Tru64 5.1b. Networker Software
is 7.2, using th same hostname and sometimes even same ip-adresses.

I'm not certain I understand.  Are you saying that you have 2 distinct
NetWorker clients, each of which is named something like client1.t-online.de
and each of which has exactly the same IP address associated with its
"primary" network interface?

To
get around this problem, we introduced a backup-network, meaning that we
put in extra network card in each client giving it a unique interface
name and an address out of the backup-network.

So doesn't that too invalidate the "must be tested on a hardware
environment absolutely identical to the operative systems" requirement?
You're adding hardware and adding to the network configuration.

The problem is that i am
having problems registering the client in the networker server in a way
that the client ist not authenticated by its hostname but by the name of
the backup-interface. What i wanted to do, if possible, is that i
wanted!  to introduce the client to the server with its ip-address or
the name of the backup network interface, rather then the hostname. But
tru64 clients always seem to authenticate themselves with their
hostname.

We don't have Tru64 clients anymore, but we've been doing what you're
talking about for 10+ years, and it worked for us with all our clients
(including Tru64).

Craig provided some very valuable tips on how to do this in his response,
you should definitely follow his suggestions.  If you run into trouble,
ask again on this list.

You'll want to pay particular attention to the settings for

        Server network interface
        Aliases

and possibly (as a last resort)

        Backup command

A couple of those fields are probably only visible if you do
"View->Details" in the "Client Setup" window from within the 7.2.x
nwadmin/networker "Green GUI".

Tim
--
Tim Mooney                                             Tim.Mooney AT ndsu DOT 
edu
Enterprise Computing & Infrastructure                  701-231-1076 (Voice)
Room 242-J6, IACC Building                             701-231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164

To sign off this list, send email to listserv AT listserv.temple DOT edu and type 
"signoff networker" in the body of the email. Please write to networker-request 
AT listserv.temple DOT edu if you have any problems with this list. You can access the 
archives at http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER