Solved!
Go to SolutionS
surjeet_singh
1 Rookie
•
21 Posts
1
28972
March 4th, 2014 03:00
Authentication error; why = Client credential too weak.
Hi guys,
I have a problem with using the NMC.
I can connect with the NMC but when I click on "Configuration/Divices" I get:
unable to connect to server: unable to authenticate with server : Authentication error;why= client credential too weak .
I recently changed the authentication method from nsrauth/oldauth to just oldauth and then again bach to nsrauth/oldauth.
I run NetWorker 7.6.5.4 and NMC 8.0.1.
Regards,
Surjeet Singh
18035
0
Posted March 4th, 2014 03:00
I moved this to the "Networker Support Forum", as the "EMC Forum" page on ECN is about the event series. Please post in the relevant solution support community for a quick answer.
18050
0
Posted March 4th, 2014 04:00
well done
18050
0
Posted March 4th, 2014 04:00
I hope you did that on the backup server ! Also, on the client
- stop the services
- rename /nsr/res/nsrladb
- start the services
18035
1
Posted March 4th, 2014 04:00
You will have to delete the peer information for this machine on the backup server. Once you delete the peer information this error should go away.
18050
0
Posted March 4th, 2014 04:00
Hi,
I have already done this thing (peer delete informations) :-(
18050
0
Posted March 5th, 2014 00:00
Thank you Pawan.... It's a currect answer
18050
0
Posted March 5th, 2014 01:00
Hello Surjeet,
Please mark my answer as helpful or correct if it has worked for you
Thank you,
Pawan
18050
0
Posted March 5th, 2014 02:00
Yes .. It's worked for me.
but I am unbale to mark your answer is currest.... there is no such options here.And thank you once again !!
1679
0
Posted March 5th, 2014 04:00
Hello all,
This error message comes up because in NW 8.x is MANDATORY to have enabled nsrauth, otherwise you will get this error message when you try to access the "Devices" tab in NMC.
crazyrov in NW 8,x we have to be careful when deleting the nsrladb folder. This is no longer a good practice, as this could introduce further issues, so instead of removing/renaming the nsrladb folder, we should delete the peer information with nsradmin.
Thank you,
Carlos
pawankumawat
355 Posts
18050
1
Posted March 4th, 2014 04:00
Hello Surjeet,
Please try following steps -
Add nsr auth back in as an authentication method.
To change the authenction method from the GUI attempt to change the Auth Methods for the client resource from the above instructions to: 0.0.0/0,nsrauth/oldauth
*note you may receive the following error* Error User 'administrator on machine 'nsrserver is not on 'administrator' list.
If the above method from the GUI gives an error, use the below method to change the authentication method via the command line.
Run the following from your networker server in a command window: nsradmin -p nsrexec
NetWorker administration program.
Use the "help" command for help.
nsradmin> . type: nsrla
Current query set
nsradmin> show auth methods
nsradmin> print
auth methods: "0.0.0.0/0,oldauth";
nsradmin> update auth methods: "0.0.0.0/0,nsrauth/oldauth"
auth methods: "0.0.0.0/0,oldauth";
Update? y
Once the authentication method has been updated to include nsrauth, you then need to restart the Networker services by running the below commands:
:Net stop nsrexecd
*This stops both the Networker Server and the EMC GST services.
:Net start nsrd
:Net start gstd
Once the services start again log back into the NMC and the clients and devices can be viewed.
Regards,
Pawan