I believe you need to look at the "NSR peer information" on the client.

If you delete this resource it will be recreated.

On 21/06/2006, at 6:35 PM, Oscar Olsson wrote:

Say that I have server A and client B. Both are running networker 7.3.1 . Lets say that there's a key mismatch between these two hosts, which makes nsrauth fail. What is the best way of getting nsrauth to work again? I assume keys or certs need to be cleared somehow on both hosts. How? Then I also assume that new cers or keys need to be issued. How? Or is there a better way to reset certs/keys? Do I need to do this on the local agent? If so, I assume that I have to edit the local agent with nsradmin on the client, in order to let my backup server configure it?

Things are not very clear to me when it comes to nsrauth, and I assume I'm not alone either. So a good response on this would probably be appreciated by many members of the networker list.. :)

//Oscar

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 wit 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

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
wit 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