Cant select destination sub-folders
Hello Bobbo,
Thx for your support to fix this issue. I deleted the registry entries for the folders like described. Rebooted and expanded networks. Find the mapped device of the NAS and try to expand it. No reaction.
Then I accepted the mapped directory as the backup destination. No credentials are requested. Then I tried to start an backup and the message "Failed to check credentials" is shown (see attachment).
The errorcode is not listed in KB.
Frank - if you want to Webex, I'll send you a link. Perhaps take a local OS backup first though as we'll be troubleshooting.
I kind of got the behavior you have when selecting the source using the NAS option - nothing showed up . However, I cancelled and then went to files and folders and expanded network and it worked that way. I then went back to NAS and then it worked again. Not sure if it's as simple as that or need to consider clearing some saved credentials or something else.
I can repeat the behavior of the "source" being the NAS not picking up the folders the first time I launch Acronis and perform this task.. nothing shows up below it except for the root share and then nothing. However, If I cancel and go back and do this again, everything is then listed there for me.
I then clicked on a deeper folder and same thing - didn't open. Canceled, selected NAS source, expanded root folder, clicked on a deeper level and now I can navigate through everything.
Does seem to be a bug, but relatively simple. Perhaps it will work for you too? Try it out.
Frank R.
I was able to reporduce your issue. I did this by attempting to access a USB WB MyBook external drive which I attached to a USB port on my router which is dedicated to the attachment of external drives. This in effect creates an NAS (Network Attached Storage) device out of an external drive.
I reproduced your issue because this device was NOT mapped as a drive. In your description above you mention that your DEVICE is mapped. This is not possible in Windows 10, are you using Windows 10 as your installed operating system?
The situation here for you and for other posters as well is the fact that Windows 10, with each new update/upgrade continues to tighten network security levels. What this means for the end user is that users must now rethink and relearn what they have come to know and expect with Windows networking. What was true and worked in the past is no longer so. The result of this is that users must learn how networking actually works now in Windows which because of security tightning has changed.
The most recent security patches from Microsoft have made changes to Group Policy settings to address "Man in the Middle" attacks. This change has impacted mapped drives for many users.
My suggestiion to all users experiencing issue with mapped drives is to delete any current mapped drives they currently have, restart their PC, then recreate the mapped drives. This should remove all current Group Policy settings and Registry entries for current mapped drives and make them anew after recreating them.
You may find that once you remap and you then restart your PC that connection is lost to the mapped drive. You will need to log into the mapped drive again in this case. If you tic the "Remeber Me" check box in the log on box Windows should store your sign on and apply it upon next restart. Be advised applying the Remeber Me will lessen the security access to your mapped drive.
Well, backups using the NAS as the destination are working fine.
However, after some additional testing, I can re-produce the issue with using the NAS as the source in a # of scenarios on a constant basis, so this does look like a big bug.
I can get past the issue with the subdirectories not showing up by simply cancelling and going back to the source a second (or third time). I actually have better luck just using the full UNC path starting with the IP in that regard. I set up the backup with the NAS as the source and selecting a small folder with some pictures on the NAS - no issues authenticating or getting there after I'm able to expand the folders using the cancel and re-pick source work-a-round. I then pick the destination as a locally attached SATA drive.
Everything looks good to go and when I press the "backup now" button, I immediately get an error that the source files cannot be found. I then go back to update the source and find that, that particular folder won't expand anymore. I can expand other NAS shares that use the same credentials, but after repeating the process with them, they hit the same problem.
I have to agree that using the NAS as the SOURCE, does not seem to be working. I've sent feedback and a system report. Pretty sure this one is not related to any credentials or account issues.
Ok, attempting again to backup a file inside a mapped network share now produces the same behavior on my machine. I have no idea why I could not get this to happen in the beginning, strange behavior for sure.
I too have submitted feedback with system report and suggest that all other posters to this thread please do the same.
I can report the following (Synolog 414):
- the NAS is not listed under NAS (looks like the Acronis engineers have not yet worked out a way to find Synology NAS)
- if I navigate to the NAS under network I can access the NAS and drill down to directories, and create new directories. I can successfully create a backup.
Normally I have a mapped drive to the NAS but I must have deleted it earlier when I was trying to get things to work. I think that the problem I was having before was that I had the Synolgy Administraion open (logged in as Administrator) on the same PC rather than local user. So it looks like the issue was muliple users accessing the NAS on same PC. Later today I will confirm this result on another PC that is running ATI 2017. Most are still running ATI 2016.
Ian
IanL-S,
You are probably right in your thinking about the multiple users. If you can create user accounts on the Synology NAS that correspond with the user on the PC it should work. The other way around it is by creating multiple users on the NAS of you can and then just use the correct credentials to access the shares.
I checked on another PC and it is working as expected. I will need to remember not to be logged in as Administrator in the administration module.
This is the first time I have tried it out on this PC with the release version of ATI 2017.
Ian
Alexz,
Enchantec and I can confirm the behavior of using the NAS as the source to be a problem. It is indeed an issue when the NAS is the SOURCE, but seems to work fine when the NAS is the destination. We have submitted feedback and system reports as well. For destination, NAS is not an issue if configured properly, but definitely a problem selecting folders from the NAS when the NAS is the SOURCE, as you mention. I know I had posted this in another thread recently, but I'm having a hard time finding it. If I can, I will reference the thread here too.
I will add here that I experienced an unsolvable issue with the use of a mapped drive and TI 2017. I do not use mapped drives in my configuration but created one for testing out the problem of subfolder navigation. I recently decided to remove the mapped drive which went fine however, after removal I could not get the TI 2017 app to forget the mapped drive location. This resulted in the application endlessly asking for logon to the deleted drive account even though I had cleared all credentials from the registry.
I uninstalled the TI 2017 application from my machine as a result. Have not reinstalled yet as I want to scan the registry for leftovers and File Explorer as well.
At this point I would suggest to anyone using mapped drives to investigate moving away from that and start using an SMB share instead. Much more secure and works much better than mapped drives.
I hit this problem this morning when trying to do a backup to my Synology NAS - I have had to implement the firewall blocks for KB 58630 as otherwise my cable modem immediately reboots when I start ATIH 2017.
The effect this is that the NAS does not show in the NAS list anymore, so I have to go through the Network branch instead.
I can input either the NAS \\mynas\backup\ path or use the IP address \\192.168.0.29\backup\ and can authenticate fine but then I never see an OK button or a folder listing.
I had a sudden 'light-bulb' moment and added a Hosts file entry for the NAS in the Windows Hosts file in C:\Windows\System32\drivers\etc and then tried again to configure the new backup just using \\mynas\backup\ and was shown a full listing of my folders on the NAS.
Note: You need to run Notepad as Administrator to be able to save any changes to the Hosts file (it doesn't have a file extension).
Hi Steve,
Thanks for posting your findings. With TI 2016 I had to add a Hosts file entry for my NAS to ge the app to recognize the device. After that it worked fine even after I removed the Hosts file entry from the Hosts file, wonder if yours would do the same? Hosts file enrty should not be necessary. It means that there are problems with the discovery methodology used by True Image in device discovery.
I have run into a new snag now. Having no issues with device discovery but issues with authenication. My dedicated NAS (FreeNAS Server) does not show up under the NAS List. It only shows under the Network which I attribute to the fact that it is a full fledged server and not a Network Attached Storage (NAS) device. I also have a WD MyBook drive which I attach to my ASUS router. That device does show up under the NAS List in True Image 2017 but I cannot athenticate the connection to it. I keep getting an athentication failed error. My gut feeling is that I use some special characters in the password and I suspect that either special characters are not allowed or certain ones are not allowed and that is my problem. I do not use special characters in my FreeNAS connection and that works without issue. Plan to investiagate and troubleshoot that in the near future.
I have now reinstalled TI 2017 (that's why I have the above goin on now). I did search the registry looking for a leftover logon entries and also looked through Windows for any Acronis leftovers and did not find any. I suspect now that my issue with the offending logon I had was due to a backup task script that remain in the database. If I have this happen again I will run Task Zap to see if that will fix the issue.
I have setup some File/Folder based test scenarios and am attempting to run them now. I think I will have some interesting results based on the first tests I ran so far. Will post the results here when ccompleted.
Ok to cut to the chase does anyone know if Acronis is fixing this issue and when the next release is ? It madening that they broke a feature (Backup to to network to computers near me) that worked in all the older versions of TI I have used. I.e. TI8, TI9 TI2009 TI2012 TI2015.
Neil, please see KB document: 58735: Acronis True Image 2017: List of Shared Folders on NAS Is Empty which has the following statement:
The issue is expected to be resolved in the next update for Acronis True Image 2017. Make sure to enable automatic check for updates at program startup so that you do not miss it when it becomes available:
See also linked KB document: 57992: Acronis True Image: NAS Is Not Detected whic has other related information.
I had this problem with ATI 2016 looking to backup to an ASUSTOR NAS using FTP to unmapped folders in Windows 10.
Test connection always worked but the sub folders wouldn't display.
Problem was solved by deselecting "Respond with External IP for Passive FTP request" in the NAS management software.
Thank you for sharing your solution with the community, Davanian!
The latest releases of the 2017 product have fixed this issue.