Acronis authentication issues on Samba shares
So I have a wide open Samba share on a NAS. Windows can freely browse it. However, when I try to back up using Acronis 2016, it won't just browse to the share. It will ask for credentials even though it's a wide open share. Why? If I go to samba and add an account that is basically the same credentials as what the windows account is on the PC, it still won't work. If you test the credentials they work fine. When you try to back up, it goes very quickly to about 24MB and sits there and eventually gives you an error that the backup failed cause the file is in use by another application. The only work around I found its to create new and different credentials on the samba share then what the PC user. Then when acronis asks for the credentials, it seems to work.
This is a terrible bug. If Windows 7, Windows 8, and Windows 10 can browse directly to the share without credentials, why can't Acronis? Even worse, when you give it the credentials of the PC and add them to Samba it still doesn't work. As a matter of fact, if I map a network drive in Windows, and then point acronis at that network map, it still asks for credentials. That's ridiculous. Please get this fixed.


- Log in to post comments

As I said, if I map the NAS in Windows, Acronis still asks for a credentials. That makes no sense. I did use the IP instead of the NAS systems name. Still got asked for credentials. The NAS is a Raspberry PI using Open Media Vault. The base is debian using Samba. The share is mapped so everyone has read and write privileges. With Windows I can use file explorer to go to the share without any credentials and freely explore and read it and write it. So it is working fine in Windows. This is a bug in Acronis.
- Log in to post comments

As I said, if I map the NAS in Windows, Acronis still asks for a credentials. That makes no sense. I did use the IP instead of the NAS systems name. Still got asked for credentials. The NAS is a Raspberry PI using Open Media Vault. The base is debian using Samba. The share is mapped so everyone has read and write privileges. With Windows I can use file explorer to go to the share without any credentials and freely explore and read it and write it. So it is working fine in Windows. This is a bug in Acronis.
- Log in to post comments

Ken,
I agree that there is a bug.
Something you could try is to copy an old .tib file to the samba folder you want to use. Then in windows explorer, right click on the .tib file and mount the image. Then unmount, call up ATI and see if it will navigate to the folder without asking for credentials.
Not sure if this will work, but I believe it is worth a try.
FtrPilot
- Log in to post comments

"As I said, if I map the NAS in Windows, Acronis still asks for a credentials. That makes no sense."
Agreed.
When mapped as a drive in Windows already (with a drive letter.. like N: for NAS drive), did you select the option to "reconnect at logon" when you mapped the drive?
After that, how are you trying to access it in Acronis? If you create a new backup task, change the destination and select "browse"... then expand "computer" (not network, not ftp, and not nas connections), does it still prompt for credentials? If it it does, then I'm stumpped too. Rebooting the NAS may help if it is blocking access from the application because of too many failed connection attempts. Other than that, I don't see why a local drive letter would prompt for credentials if it's already authenticated in Windows and the SMB keys were removed form Acronis and Acronis relauched. If using one of the other 3 methods besides "computer", then it could require credentials again since those would not be directly in Windows, but through a different connection protocol that needs to be entered into Acronis first.
Not familiar with open media vault myself, but would be interested if you could show your open share setup on it with some screenshots?
https://www.scribd.com/doc/289550733/Build-Your-Own-NAS-With-OpenMediaV…
I understand that it works with no authentication in Windows, but there may be a limitation of having no authentication turned on. Could you create a test share with an account and password and try that too and see if it makes any difference with a new test Acronis task? You may have to authenticate using the NASname/username in the username properties of Acornis.
- Log in to post comments