Skip to main content

Build 6581 prompted for authentication when attempting to recover

Thread needs solution

Last night upgraded my three PCs from 2016 to 2017, two systems seem to be working but on my wife's PC I seem to have an issue with authentication. This AM at 0126 hours the scheduled incremental BU successfully ran, an incaremental TIB file was created. This afternoon at 1938 hours I successfuly ran a 2nd test using the only task I have on her system. This time a full BU TIB file was created. The target for the BU files is a shared drive on my desktop. Looking at the BU folder I noticed that I had several very old TIB files. In an attempt to determine what TI was aware of, on her system I clicked on the "Recover disk" button and I'm prompted with an "Authentication Settings" window for a path of \\s4\S4-Q-WDBlk6TB-BU (this is the shared drive on the desktop), the user name has my email address and a hidden PW. If I click on the "Connect" button it fails. I had assumed that the user name and PW was correct in that it was filled in when the window opened. 

I hate to be a dummy but I have no idea what really should be here. I also tried my user name, e.g. the user name I see when I boot my desktop. Everything I've tried it fails to connect. For the PW I used what I enter when booting the system. I'm really confused, especially since the BU task seems to have successfuly ran on her system.

When the share was originally created on my desktop it was done under windows and EVERYBODY has full access.

From my wife's PC via xplorer2 or the windows file manager I can access the shared drive, create files and delete files.

Please provide help at the dummies level. 

0 Users found this helpful

The password needed is that of the machine on which the backup phsically located. 

if you have mapped drives in Windows and Acronis 2017 5554 installed (current release) there is also a bug with authenticating to connected shares (or mapping to new ones in Acronis).  There is a hotfix patch you can apply

https://kb.acronis.com/node/59051

Alternatively, you can stop/start the workstation service from within Windows computer managment >>>> services just before attempting to connect to the NAS.