Open Location on back up failed with error Access is Denied when stored on NAS
I have been having this issue for year and just ignored it, but it is quite frustrating and is still present even though I just upgraded to ATI 2021.
I have a synology NAS which is accessible as an SMB share. I login to my Windows 10 system as myself and I am in the administrators group on my Windows 10 machine and those same user credentials/permissions are set on the NAS.
I always have full read/write access to the NAS via the \\MyNas\\ path. I have no issues with the backups completing either. However, after a backup if I choose the ‘Open Location’ option, ATI always throws the ‘Access Denied’ error. If I choose the ‘Search Files’ option, I am forced to authenticate with the NAS share using my windows user/pass again….even if the NAS is freely browsable from within the Win10.
So it seems there is a permission error of some kind, but I can’t figure out what it is.
I have read the KB articles about permission access, but they aren’t clear about how you should be setting permissions on your NAS. Everything seems to be fine from windows so I’m guessing the ATI process somehow doesn’t have access permissions to the NAS. However, I don’t understand how I might be able to fix that on the NAS side (if that’s where the problem lies)?
Do you have automatic backups enabled and ATI is able to remember the user credentials to the Synology in order to run the automatic backups?
Also any tips on how to get that specific acronis account accessible? I did create a separate 'acronis' user on the Synology, but when I try to access that shared folder from windows with the specific username and password created in DSM, Windows always says access denied?
Ok...this is very perplexing...if I create a new user in DSM and it doesn't match any Windows account and then if I browse to the SMB share of the Synology, I cannot connect to the synology by it's name. It invokes the user credentials request and fails, but if I access it directly via it's IP address, it does accept the user/pass...
I somehow think this must be linked together to ATI's problem with getting access denied, but I have no idea why or how to resolve this...
I have several different PC's all doing scheduled backups to my Synology NAS with no issues, all using the NAS \\name\backup_folder addressing though both that and using the IP address both work fine.
Have you ever set an entry in the Windows Hosts file for the NAS that might have used a different IP address at an earlier point? Look in the hosts file at C:\Windows\System32\drivers\etc to check.
By default the hosts file only contains the following commented out lines:
# Copyright (c) 1993-2009 Microsoft Corp. # # This is a sample HOSTS file used by Microsoft TCP/IP for Windows. # # This file contains the mappings of IP addresses to host names. Each # entry should be kept on an individual line. The IP address should # be placed in the first column followed by the corresponding host name. # The IP address and the host name should be separated by at least one # space. # # Additionally, comments (such as these) may be inserted on individual # lines or following the machine name denoted by a '#' symbol. # # For example: # # 102.54.94.97 rhino.acme.com # source server # 38.25.63.10 x.acme.com # x client host # localhost name resolution is handled within DNS itself. # 127.0.0.1 localhost # ::1 localhost
The above is from my own working PC that connects to my NAS without issue.
You might check Control Panel->Credential Manager to see if there is perhaps a bad credential for the NAS.
So it seems the issue might be that I'm now trying to follow Steve's advice and create a shared folder with different credentials to authenticate than what I use to access my Synology NAS for general daily use.
As best I can tell, Windows won't let you authenticate with a named location using two different credentials.
I have a folder for Video and Photos and general software downloads that I access throughout the day via CIFS/SMB using my Windows Account login credentials. I've now created a new shared folder specifically for Acronis storage that uses new authentication credentials for which I have no corresponding Windows account so that my backups can't get encrypted in a ransomware attack on my main system (it was interesting you pointed this out @steve smith as this was something I was already trying to figure out a solution for before you mentioned it in your post).
So it seems if my Windows account is auto-logging in to //MyNAS/Video using my Windows account, there is no way to then login to //MyNas/AcronisBackups using different credentials. That's why logging in via the ip of MyNAS (e.g. //192.168.0.2/AcronisBackups) *does* work. Windows sees it as a different named CIFS share and will allow alternate credentials. I was able to test/confirm this by looking at Get-SMBConnection and then killing all the SMB sessions by restarting the Workstation service. As soon as I successfully killed the SMB connections and attempted to authenticate using //MyNas/AcronisBackups I *was* able to authenticate with those non-Windows Account user credentials.
This doesn't seem to cause an issue when Acronis is running a backup even if I'm accessing files locally - however, I need to do more testing as I'm thrashing around quite a bit trying to make this all work.
Also, there is no entry in my hosts or lmhosts file for the NAS. SMB v1 is also disabled on the Synology and on my Windows10 system. My router does have the ability to act as a WINS server and I do have that set/configured/deployed via DHCP.
@Steve Smith - do you access your NAS for local network browsing via CIFS while also sending your Acronis backups to that NAS? Or is it strictly for backups and so you aren't trying to then access other shared folders via CIFS/SMB?
BrunoC - already had checked Windows Credential manager and that wasn't the issue either.
Uggh...this has also now created another issue...
I'm trying to move all my Acronis backups from the folder they were located in to the new Shared folder on the Synology NAS and I'm getting a Disk Full error. It's only about 200gb of of the full+incremental backups of my OS drive and the NAS has 5TB of free space available.
I only access the NAS via Acronis and have no shared folders to the NAS.
I have no problem accessing my Synology NAS. Like Steve, I use it strictly for backups. I have no troubles using Open Location from ATI, or using Windows Explorer. I do have a separate log in for the NAS.
Also, I use manually assigned IP addresses for devices on my local network. My NAS is always at the same IP address and I often use that instead of the name to access, but I have not had trouble with either.
If the backups are *.tibx, the move involves coping the files to the new location, then deleting the old folder. I suggest removing the backup tasks from ATI, then turn off Active Protection so you can move the files using Explorer. The add back the backups and confirm the configuration.
Ian
I had similar problem with WD NAS. Original backup would work, then after a while access denied and prompt for NAS username and password. Finally discovered that original backup was to \\mycloud\Public but login prompt was for mycloud.myISP.net, added an entry to hosts file to resolve mycloud.myISP.net to the correct IP and backups started working. FYI this only happend to the laptop backing up over wireless not to the wired PC. Strange?