In regard to: [Networker] Problem with new domain client..., Goslin, Paul...:

We are running NW 7.6 on Win2008 64bit. Just added a new Windows client
from a new domain we are in the process of rolling out. Networker
refuses to back it up. Keeps failing with:

* INTVS07.cincomsys.local:Probe 90067:savefs: Cannot access nsr server 
'legatobuserver': Authentication error; why = Invalid client credential

"Invalid client credential" can happen for a couple reasons, but the
underlying problem is that when the "nsrauth" mechanism is used and
the "NSR peer information" certificates on one end of the connection or
the other don't agree.  This frequently happens when you install the
client under one name and let the NetWorker client start up (at which
point it generates a certificate that has the pre-production hostname)
and then later rename the client when it goes production.

Search the mailing list for "NSR peer information" or "Invalid client
credential", you'll turn up a procedure that should help you verify what's
in the certificates.  Once you know what's wrong, you delete the incorrect
peer information and let it be regenerated.

There are other reasons why the "Invalid client credential" might happen,
but verifying and probably regenerating the client "NSR peer information"
is the place to start.

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