Unsolved
This post is more than 5 years old
1 Message
1
6717
April 16th, 2019 07:00
Networker BMR Failing for Unable to create client connection with server xxxxxx Reason: Program not registered
Hi,
This is my first post so apologies if I've broken any forum protocols.
- I have a Networker server and a Networker Client. Communications between the Server and the Client were established using nsrauth.
- I ran an 'All' backup of the Client so that I could try a Bare Metal Recovery, the backup/save set completed successfully.
- I then shutdown my Client server and inserted a blank disk and then powered up the Client server and booted from the Networker BMR ISO image.
- Everything looks good with regard to the BMR wizard until I get to the 'Select Server' screen. I enter my Server (which contains the Client save set) in the 'Server' field and then enter the Client (which will be rebuilt) in the 'Client' field, click 'Next'.
- Here I see an almost instantaneous error message: Error trying to validate NetWorker server credentials:
Unable to create client connection with server xxxxxx.com Reason: Program not registered. - I have configured the NetWorker server to use oldauth
nsradmin> print
auth methods: "16.XX.XXX.117,oldauth/nsrauth",
"0.0.0.0/0,nsrauth/oldauth"; - I have added the recovering client to the Application Administrators group on the NetWorker server.
- I have also deleted peer information from the Networker server.
I am still seeing the issue mentioned above. Any pointers or help would be very much appreciated.
Thanks
No Events found!
DELL-Sam L
Community Manager
•
8K Posts
•
34.3K Points
0
May 21st, 2019 10:00
Hello Gasead,
Have you tried to use this guide to do you BMR? If you haven’t then I would try this to see if it helps with doing your restore. https://www.emc.com/collateral/TechnicalDocument/docu61098.pdf
Please let us know if you have any other questions.
Dayana_Gudac
1 Message
0
June 21st, 2021 02:00
Hello,
Any resolution on this? I have a similar issue.
Thanks
DELL-Josh Cr
Community Manager
•
9.7K Posts
•
43.4K Points
0
June 21st, 2021 10:00
Hi Dayana,
What errors are you getting? Did you do the steps previously mentioned? What storage device and what type of server and what OS?
Chazerqc
4 Posts
0
March 14th, 2022 07:00
Hi , BMR restaure server with this : error trying to validate networker server credentials ,
show the screen
But communication with server is ok i ping the server networker
DELL-Sam L
Community Manager
•
8K Posts
•
34.3K Points
0
March 14th, 2022 09:00
Hello Chazerqc
Are you following the steps in this guide for performing a BMR? https://dell.to/3Jcs9hM
Chazerqc
4 Posts
0
March 15th, 2022 05:00
Hi , this procedure NOT WORK ,
because step Select server want the credentiel
DELL-Sam L
Community Manager
•
8K Posts
•
34.3K Points
0
March 15th, 2022 11:00
Hello Chazerqc,
It is best to open a support case for this issue.
barry_beckers
393 Posts
0
October 12th, 2022 06:00
in out case this exact error seems to be due to setting the date/time/timezone, the time seems to be lying in the future, causing the nw server to reject the bmr client's nsr peer certificate (without clearly telling so however...). We set the date one day earlier after which the recovery continued.
Sadly also no nsradmin command available on the bmr client to be able to list the created nsr peer info certificate, so that you could use it to analyze it using openssl command to see what it states for the not before/not after values of the certificate between the tags BEGIN CERTIFICATE/END CERTIFICATE (including the tags themselves) and putting the cert into a file and have it analyzed by openssl command:
$ openssl x509 -in nw-client.crt -text -noout
CUT
Not Before: Oct 5 12:01:43 2022 GMT
Not After : Jan 18 03:14:07 2038 GMT
CUT
certificate as shown by "nsradmin -s localhost -p nsrexecd" command:
nsradmin> . type:nsr peer information
nsradmin> option hidden
nsradmin> pr
CUT
-----BEGIN CERTIFICATE-----
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
-----END CERTIFICATE-----
So sdaly the BMR client does not and cannot report this to see if something might be wrong with its nsr peer certificate (for example it lies in the future), nor does the NW server clearly state why or even that it rejected the nw client certificate...