Unable to back up to network drive
The network drive we used to use for the Acronis destination was a Samba share without needing any authentication. We've been backing up for years to that drive. A few days ago it was changed to require Active Directory authentication. Now, all the network backups on all workstations are failing with "Cannot access backup file." Except, strangely enough, for two computers, both of which are running ATI 2017. Initially they too failed, but I went into those computers, deleted the network backup settings, recreated it, browsed to the network destination, and that was that. No problem.
I've tried the same on other workstations some running ATI 2016, some with ATI 2018 (I upgraded 2 of the ATI 2016 computers to ATI 2018 thinking this was a problem particular to 2016), but when I browse to the network location: \\OHPRSstorage\Backups, I get a dialog requesting "Authentication Settings". I did not get this dialog on the ATI 2017 computers. It doesn't matter what I type in this dialog for credentials, it always says "Connection Failed". If I map this drive using Windows Explorer (My Computer) it maps just fine without asking for credentials, as expected.
Any idea how to fix this? Currently, most of our office workstations are unable to backup to the network drive.
Steve, thanks for those links. I'll check them out shortly. In the meantime, I have confirmed that ATI 2017 works w/o problem. I had a 3rd, unused 2017 license and I used it to upgrade a workstation with 2016 that was failing according to my initial post. After upgrading to 2017 the backup to network drive worked without problem.
I'll post back if your links give me anything to go on with respect to 2018.
Later, more info:
I deleted the HKEY_CURRENT_USER\Software\Acronis\Connections\smb per your 1st link. Interestingly, that permitted one of the 2018 network drive backups to work (XP). However, when I went to create a 2nd network drive backup on that same machine, I got the credential dialog again. I tried deleting the registry key on another computer (WIN7), but I still get the credential dialog (which doesn't work). I'll try completely wiping out the Acronis installation and reinstalling from scratch.
OK, I uninstalled ATI 2018 from one machine and deleted the ATI 2013 and ATI 2016 registry entries as well. I deleted the C:\ProgramData\Acronis folder and I ran your cleanup program, then rebooted. I installed ATI 2018 from scratch. Same thing, credentials requested, nothing accepted.
Seems there is a bug in ATI2018.
I'm going to look through the rest of your suggested links, but I've already spent 5 hours trying to get ATI2018 to work and my probable solution will be to go to ATI2017 on the remaining workstations since that version had no problem accessing the network drive on all three workstations using 2017.
Tech,
Sounds like you have different operating systems on your workstations (clients), Win XP, Win 7, etc.. There are differences between these and Server versions in authentication which is at least part of your issue here I would say.
See this link for more on this:
https://technet.microsoft.com/en-us/library/hh831472(v=ws.11).aspx
Enchantech, thanks for that link -- lots of information, but I don't know that any of that helps me. We've been running Win7 workstations in an AD domain for years. The one XP is a legacy system, hosted on a VM, but I'd still like to back it up. The network drive to which we backed up was a Samba share with no ID/Password required. A security audit suggested we change that, so last week that was changed to authenticate with AD credentials. That worked fine, everyone could mount the particular network drives they needed w/o having to enter credentials. However, the workstations with ATI2016 started failing unable to access the network drive. The two ATI2017 workstations failed initially, but I just had to re-specify the destination in the ATI interface and they worked.
My initial thought was to upgrade the 2016 workstations to ATI2018 (since 2016 didn't seem to work, but 2017 did, I assumed something was fixed in 2017 with respect to AD authentication and that fix would be carried into 2018). We bought 10 ATI 2018 licenses, but they had the same problem as 2016, as stated above. I've installed ATI2017 on 3 more workstations and all backed up to the network drive with no problem. I didn't even have to uninstall the 2016 version and it remembered all the drives, options, etc.
5 of the workstations are now working fine with ATI2017, none are working with ATI2016 OR ATI2018. As mentioned, I've already spent a significant amount of time researching kindly provided links and experimenting. And while I'd love to spend even more time on this, that's not really productive for me. Given that ATI2017 works flawlessly with respect to domain credentials, my plan is to return the 10 ATI2018 licenses and get 5 or 6 more 2017 licenses. Maybe sometime during the next year the Acronis team will figure why domain credentials work with 2017 but not 2018.
Thanks to you and Steve for your feedback and suggestions.
That's really strange. I can say that 2016 had some issues with networking as did the first release or so of 2017 but those issues got sorted. I think you may have found an issue with SAMBA shares. What I find strange is that deleting the credentials in the Registry fails to get things working.
In the 2017 product what I found to work with SAMBA shares was to first access the shares with Windows Explorer supplying the credentials there, then close out the Explorer session. Then run True Image and enter the credentials again when prompted and that would get things working. A pain but it did work. You might try that with one of your 2018 installs and see what happens. Nothing to loose at this point!
Thanks. Did try that (accessing share via Windows first). Did not help in my case. I tried that on several machines.
One interesting thing is that on one of the workstations with 2018, when I deleted the HKEY_CURRENT_USER\Software\Acronis\Connections\smb, I was able to connect to the network drive and backup. And, I can still do a "backup now" on that backup. However, I cannot update the settings on that backup, nor can I add another network backup. I'd say 2018 still has some glitches.
The latest version of 2017 just works. It does not require me to map the share via Windows first. I've got 2017 working w/o problem on 5 workstations currently and will likely move the rest there very soon since, in the meantime, the other workstations are not getting backup up to the network drive at all.
Understood, please submit a feeback ticket for Acronis support using the in app feadback featrure. Included link to this thread and describe your issue in dome detail so that they can investigate the problem.
TI 2017 is a good product and I would use it if it works for you!
Feedback sent!
Great! That should get the ball rolling on the issue.