This issue is usually caused by incurrent auth method or corrupt peer information.
1. Check auth method:
Run the following commands on both NetWorker Server and the problematic client:
C:\>nsradmin -p nsrexec NetWorker administration program. Use the "help" command for help. nsradmin> . type: nsrla Current query set nsradmin> show auth methods nsradmin> print
Does it show as below on both NetWorker Server and the problematic client?
The error by OP seems to be case 2). And it should be said that it takes some amount of time (short) until it takes place (at least that is my personal experience).
TimQuan
4 Operator
•
1.2K Posts
3
August 1st, 2013 18:00
This issue is usually caused by incurrent auth method or corrupt peer information.
1. Check auth method:
Run the following commands on both NetWorker Server and the problematic client:
C:\>nsradmin -p nsrexec
NetWorker administration program.
Use the "help" command for help.
nsradmin> . type: nsrla
Current query set
nsradmin> show auth methods
nsradmin> print
Does it show as below on both NetWorker Server and the problematic client?
auth methods: "0.0.0.0/0,nsrauth/oldauth";
If not, run:
update auth methods:"0.0.0.0/0, nsrauth/oldauth "
2. Update peer information:
On the client:
nsradmin -p nsrexec
print type: nsr peer information; name:
delete
On the networker server:
nsradmin -p nsrexec
print type: nsr peer information; name:
delete
~~~~~~~~~~~
Best Regards,
Tim
Please mark my reply as “Correct Answer” or “Helpful Answer” if it helps you. Thanks.
Anonymous User
1 Rookie
•
13 Posts
0
March 4th, 2014 03:00
Good work!!!!
ble1
4 Operator
•
14.4K Posts
1
March 4th, 2014 04:00
The error by OP seems to be case 2). And it should be said that it takes some amount of time (short) until it takes place (at least that is my personal experience).
sokundu
1 Rookie
•
47 Posts
0
May 6th, 2015 23:00
Thanks Tim,
Its working fine.