Unable to authenticate NAS in bootable recovery interface
Hi,
I am trying to perform a Recovery from Boot Media. The backup images are stored on a WD My Cloud Home NAS (in the “Public” folder of the drive). I had to create WinPE-based media using the “Windows Assessment and Deployment Kit (ADK)” in order to see the NAS in the Recovery interface.
I am being prompted for a User Name and Password when trying to access the drive. However, within Windows a password is not required to access that Public folder, so I don’t know what credentials it needs. Everything I tried results in the message: "Connection failed. Please verify user name and password."
Here’s what I have tried, without success:
- I have tried the only User Name and Password that the drive uses, which is the email address (User Name) and Password used for the WD Web access to the drive.
- Altering the User Name format based on this article https://kb.acronis.com/content/58004#Different_forms_of_entering_NAS_us…
- Using no password, or checking off “Use NT authentication”
- Trying other suggestions from this forum
- Accessing the drive by adding \Public\ after the network device name
- Accessing the drive via IP instead of it’s network name
- Looking for solutions in WD (Western Digital) forums
As a note, I also receive the error below, but it just appears to be a result of not knowing the correct User Name and Password:
“\\Mycloud-xxxxxx is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions.
The Server service is not started.”
I appreciate any help that anyone can provide. Thanks.
My NAS -based backups are on private shares but I have a public share so I decided to copy a .tib file to it and give this a try.
On my first try I got the same errors mentioned about (including that peculiar "The Server service is not started.” ).
For my 2nd try I mapped the public share and could successfully access it using the ATI Browse function and using "This PC" (or "My computer" of whatever it's called in that list). Since the public share was mapped it showed up as drive on the computer. When I selected the .tib file I got a popup saying credentials had not been provided and asking if I wanted to continue anyway. I gave it a "Continue" and it just sat there for over a minute, but it eventually displayed the file with the usual entries in the context drop-down menu. (I picked Validate but cancelled the validation once it began.)
This is sort of odd. I have not been able to get the WinPE/RE ATI to access private shares on mapped drives. However, I won't argue with success: I can access .tib files on mapped public shares and unmapped private shares.
Thank you for the helpful responses! I apologize for the long delay in responding.
I ended up needing to map the drive from the command line, as suggested. I had to also include a generic user name/password:
net use x: \\ Mycloud-xxxxxx\Public /user:nobody nobody
As Patrick mentioned, I had to choose "This PC" (as opposed to "Network") to access the mapped drive.
After that I hit another snag, the destination drive wasn't showing up correctly in the recovery interface. The drive is an NVMe SSD, so I followed the suggestion from this post: Unable to restore disk backup, system drives not seen by True Image. I had to rebuild the Recovery Media with drivers relating to the SSD.
I hit other snags before that, like needing to disable Secure Boot in the BIOS in order to create the “Windows Assessment and Deployment Kit (ADK)” based Recovery Boot media image. See this post for more details: Media Rescue Builder geht nicht: Failed to mount the source .wim file
Thank you both very much for all the help! The recovery process now works perfectly!
Good to hear that you have this working now, thanks for the feedback.