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

Hi Craig,
hi Tim,

i followed your kind advice but it´s still not working.


Let us assume this:

Client1:

Hostname -> frankfurt

/etc/hosts:

10.198.15.10     frankfurt
10.198.20.20     frankfurtbackup
10.198.20.1       legato  legatobackup  nsrhost

/usr/var/nsr/res/servers:

legatobackup

Client2:

Hostname -> frankfurt

/etc/hosts:

10.198.15.10   frankfurt
10.198.20.30   frankfurtbackup2
10.198.20.1     legato  legatobackup  nsrhost

/usr/var/nsr/res/servers:

legatobackup


Networker-Server:

Hostname -> legato

/etc/hosts:

10.200.200.1   legato
10.198.20.1     legatobackup
10.198.20.20   frankfurtbackup
10.198.20.30   frankfurtbackup2


Clients configured as frankfurtbackup and frankfurtbackup2.

I am able to backup frankfurtbackup, but when i try to backup
frankfurtbackup2, networker pops up with a rap error, that user root on
frankfurtbackup2 has no remote access privileges to frankfurtbackup.

Are you certain?  It's not saying "frankfurt"?

If
i give him the privileges he backs up the files of frankfurtbackup even
though i started frankfurtbackup2. It seems like that frankfurtbackup2
returns his primary nic name (frankfurt) to legato?? If i give
frankfurtbackup2 temporarily another primary hostname with "rcmgr set
hostname frankfurtbackup2" it works.

Absolutely desperate... :-(

No experimenting in the client configuration with aliases or server
networkinterface helpes.

Ok, then there are at least two other things you can try.  The first is
in the client resource for each client, with "View->Details" set, try
adding a setting in the "Backup command" field, basically

        save -c the_client_name_you_want_to_use

If that doesn't work, you also may wish to *try* deleting any aliases
you've specified.  Normally, if you're not using the name that the host
actually reports, you need to have that name listed as an alias, but in
this case it may be causing problems because you have two clients with
exactly the same entry for alias.

If neither of those things work then there is a last resort option that
I know will work, but I don't know if it will meet the regulatory needs
you're operating under.  It involves using the runtime loader's ability
to do function replacement by pre-loading a custom version of one or more
functions in a shared library that you create.  In this way, you can
insert functions that return what you want them to return (e.g. a
gethostbyname() function that returns a struct hostent that has the info
in it that you want).  This can be done on a per-process basis and once
you understand what's going on it's actually very easy.  It's what tools
like "dmalloc" and "electric fence" use.

Contact me off-list if using save -c doesn't work and you're
interested in trying the function replacement method.  Check out the
man page for

        loader

on Tru64 if you want to do some background research, and pay attention
to the _RLD_LIST environment variable.

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