Cant select destination sub-folders

Is this a mapped drive?  If so, use Windows File Explorer to refreash your network.  If you are using Windows 10 and have not restarted your machine since the install of 2017 you might do that as well.

Yes, this is a mapped drive.  I did an uninstall of ATI 2016 using REVO to clean everything, then restarted, then installed ATI 2017, restarted.

I found a resolution.

If I map the drive using the DNS name (\\knas), I can't reach the subfolders.
If I map the drive using the IP address (\\10.0.0.10), I can reach the subfolders.

Any ideas?  I can reach \\knas from the command prompt with no issue.

That would indicate a host name resolution problem.  You might try flushing the DNS cache.  From an admin command prompt ipconfig /flushdns.

Did that, but the fact that I can resolve the DNS name in windows and everywhere else but in ATI leads me to one concusion.

Hello ChrisK,

I got exactly the same problem like yours.  On a WIN10 Desktop i can't access the subfolders on my mapped NAS devices. This is only a problem for the 2017er acronis software. All the rest can access the subfolders without problem, also the older version before I did the update to 2017.

Good to know I'm not the only one with this issue.     

Frank, does using the IP help in your case too?  If so, please do submit feedback from within the application, reference this thread and submit the system report too.  I can't reproduce this behavior on a WD-Mycloud.  What type of NAS devices are you and Chris using - just curious if they are from the same manufacturer or not (in case there is a bug that is occuring for that particular type). 

I am using a QNAP Turbo NAS (TS-419P II).

I have the same problem with a WDMyCloud-NAS. The workaround with the IP address does not work in my case.

Furthermore Acronis True Image "recognized" my NAS at the backup source page as WDMYCLOUD.FRITZ.BOX. That does not make any sense. The host name of my NAS is simply "WDMYCLOUD". Manually changing the name has no effect.

"Fritz.Box" ist the host name of my router. There was the posibility to use the USB port of my router to connect a USB hard disc and use it as NAS. But I use the USB port to connect a printer!

I have found up to now no possibility to backup my personal files of my WDMyCloud-NAS to a usb hard disc.

Alex - your router assigns the DNS name for all systems on the network (unless you have a DHCP server or other DNS service doing this from another system or device).  I suspect that what you are seeing here the fully qualified domain name as DNS is configured on the router.  If your router shows the attached device names, you may see it listed with the .fritz information their too.    

Is everyone using the new "NAS" area of the application?  What happens if you create a new test backujp and use the traditional "browse" method instead and enter the UNC path name of the NAS with IP and the complete share path.  I get prompted for credentials, enter them and it works.  (see screenshot)

I am using a WD-MyCloud 4TB with firmware WDMyCloud v04.04.03-113 : Core F/W and am not having issues with SMB or FTP connections.  I have made sure that all of my NAS shares have been password protected with an account and am using those credenitials to connect in Windows and in via Acronis at this time.  

***EDIT***

For those with a WD device, do you have the network "network name" set as workgroup or whatever your local PC workgroup is named as?  Have you tried rebooting the NAS in awhile - perhaps too many failed connections and it's preventing access from Acronis?  I'm seein g a lot of forums with those that have WD NAS devices only capable of runing version 2.x firmware still having problems. 

What if instead of just using the NAS username, you enter the NAS device name/username ? 

Hello Bobbo,

thanks, you are right: "wdmycloud.fritz.box" is the fully qualified DNS name of my NAS.

If I try the traditional way to create a file backup and I use the IP address plus the name of the share, the connection test is successful.

However, after establishing the connection I see no additional share in the list, so I can nothing select.

I am also using a WD My Cloud 4TB with firmware v04.04.03-113. The share is password protected.

Workgroup Name in the NAS settings is "WORKGROUP". I do not use a windows home group, because I do not need one and I have installed the newest WD My Cloud drivers without modification.

I will try a reboot of the NAS, but I think, that this is not the problem, because I have never problems establishing connections to the NAS outside Acronis True Image.

Thanks,

Alex

I have a Thecus N5200XXX NAS.  This share is password protected, same like AlexZ.

I rebooted the NAS and now I have a different behavior. 

Klick on the "+" of the "Y" Device. Then a sahort checking of credentials and the OK Button is ready to take this directory as Target.  But I want to select a subdirectory, not the mapped directory itself.  No chance.

Tomorrow I will try if a mapped subdirectory would be accepted as a backup target.           

Meanwhile I tried a reboot. I have still the same problem.

Perhaps we're getting too into the weeds on the router (since as you mention it's working in Wndows outside of ACronis), but for what it's worth, I have my router DNS pointed to Google (8.8.8.8 and 8.8.4.4).  I also have UPNP disabled (if you disable it and you can't stream with your XBOX, turn it back on). I also do not have a domain name set on the router - I always leave that blank.

For Alexz - the fact that Acronis is trying to use the fully qualified domain name, makes me think it is trying to authenticate to the router as the domain and not the workgroup - I'm just guessing though.  When I run ping -a 192.168.1.100 it resonds with just the NAS name - does yours return the fully qualified name or just the NAS name?

Router's aside though - have you guys also tried clearing the existing Acronis SMB informatoin in the registry, closing down ACronis, rebooting the PC (for good measure), starting the PC, connecting to the NAS from within Windows (and authenticating if need be), then opening Acronis and attempting to authenticate after entering the new credentials again?  

And don't map to the root of the NAS when using the traditiona UNC method, try mapping to the full name of the NAS share where the backups will be located - enter the complete path before pressing enter and see what happens. 

I am seeing the same problem with my Synology NAS. If I recall correctly this issue was picked up during beta testing (Beta 2) - I am sure I reported it (there were other associated issues that have been fixed in the release build). In Beta 1 it worked as expected.

My Synolgy NAS is still not listed under NAS, I have to access it by Network. One thing I noticed, that I am sure was not in the Beta, is the ability to select other Cloud Providers (DropBox and OneDrive). This seems to be picked up via Win10 libraries (but I could be wrong).

Ian

An interesting read here from all posters to this thread.  I believe that your experiences are associated with a change to how the True Image application accesses Network shares of connected devices.  I suspect that this change could be the adoption of SAMBA security fixes.

Reading the posts above it appears that users can gain access to the root of a mapped drive but cannot gain any further access.  This is indicative of an enforced permissions behavior.  Correct setup of user accounts and shares on network devices using SMB is critical for proper security of data on SMB connected devices.

With Windows 8 up the use of Guest accounts over SMB/CIFS shares became prohibited.  Access to SMB shares via Windows 8 up can only be accomplished using authenticated accounts.  What this means is that user accounts must be established on connected devices in order to enable access. 

My suspicion here is that this permissions security is being enforced by Windows to these devices all of which use SMB/CIFS protocol where in the past this may have not been the case.

The correct way to get this to work is to setup user accounts on your NAS device with username/password.  When prompted by True Image for credentials these credentials are the ones needed to gain access.  User accounts should hold associated shares specific to that user and not a general root Public/Guest account.  If you do not have user accounts setup on your NAS you should do so and then create new mapped drives under those user accounts.  It is my belief this should solve the issues here for those whom are not currently using user accounts on their NAS devices.

If you are using user accounts and still have this issue I would suggest that you remap the drives to your NAS setting them up via your NAS control panel under a user account which I believe should resolve the issue.

Hello,

I have the same issue on at least two machines. Setting sepcific user accounts and passwords is not solving the problem. Selection of a subdirectory of either a NAS or a network drive below the root directory is not possible, neither for selecting as a source nor for the destination folder.

Furthermore I tried to use the UNC path instead of the mapped drive letter. This is also not working.

Once I got access to a network drive while I was using the administrator account of that network server. But how shall standard users get access?

In the actual version/build ATI2017 it is not usable with any kind of network connections and I will go back to ATI2016.

Since you have likely been trying this to some degree already you should clear out any previously entered credentials as outlined in Look here:

https://kb.acronis.com/content/58004

If you have not attempted to correct problems by rebooting your network hardware followed by your PC then you should do so.  For other network troubleshooting look here and if you still have issue then contact Acronis support with the information collected as outlined here:

https://kb.acronis.com/content/58000

Admin level user account must be used in network authentication.

I have always used user accounts and passwords to access my NAS box.  It's something else.

Side note:  Nothing is avaialble at all under the NAS backup location, my work around is browse>to a mapped drive.

Same problem with Windows 7 machine accessing a WD Mybook Live DUO NAS. It simply doesn't work. Tried EaseUS freebie download instead and this works perfectly. Now looking for a refund from Acronis.

Hi Chris,

Instead of using NAS, if you use browse and type the full UNC path \\routerIP\entiresharepath (not the root) and press enter - does that work too, or still nothing?

It is starting to look like an issue.  I've reached out to some of the support engineeres to see if they can find out more.

Rob, I can recreate this issue too with my Synology NAS where an existing backup that I created with ATIH 2016 will run fine to the NAS but any attempt to create a new backup to the same NAS fail.

ATIH 2017 will show the root of the NAS by IP address only and refuses to test the connection successfully using the same credentials that the working task uses.  Attempting to enter the full path on the NAS which worked with 2016 doesn't want to work with 2017.  

Not sure if it is relevant but my NAS is setup to not allow root folder access for the credentials being used, these can only be used for the specific sub-folder (\backup)

Hi Bobbo_3C0X1,

you asked me yesterday (#13):

For Alexz - the fact that Acronis is trying to use the fully qualified domain name, makes me think it is trying to authenticate to the router as the domain and not the workgroup - I'm just guessing though.  When I run ping -a 192.168.1.100 it resonds with just the NAS name - does yours return the fully qualified name or just the NAS name?

The answer is: Ping returns the fully qualified DNS name of my nas system: wdmycloud.fritz.box

It does not matter if I enter in acronis \\WDMYCLOUD\[share name], \\WDMYCLOUD.fritz.box\[share name] or [IP address of my NAS]\[share name], I simply cannot see sub directories afterwards.

The connection test is always succesful. After "establishing" the connection, the displayed directory tree remains unchanged.

I have the problem both in the selection of the backup source selection and in the selection of the backup destination.

This definitely seems to be a major bug of Acronis True Image 2017, which makes it unusable for many NAS users.

Out of interest, has anyone tried "create new folder"? Not a solution, just may help understand what is causing the problem.

Am I correct that some users are still getting the error message when testing the connection; in Beta 2 that turned out (at least in my case; Synology 414) to be 'phantom'; the connection worked.

Ian

Thanks all.  I am going to return to my ASUS TM-AC1900 router and enable SMB on it later tonight and see if I can produce this behavior on another device, other than my WD-MyCloud (which is currently working fine).

So far, I've done 2 upgrades from 2016 6571 to 2017 beta 1, to beta 2 to the final release, with no issues connecting to my WD-Mycloud.

I have also built 4 different VM's with fresh Windows 10 installs (all using the anniversary update) and trial versions of Acronis 2017 beta 2 which worked fine.

I am going to build a few more VM's from scratch with the 2017 final release and test connections to the MyCloud and the ASUS router SMB share this weekend and report back on Saturday. 

Hi Chris,

Instead of using NAS, if you use browse and type the full UNC path \\routerIP\entiresharepath (not the root) and press enter - does that work too, or still nothing?

It is starting to look like an issue.  I've reached out to some of the support engineeres to see if they can find out more.

------------------------------------------------

That does not work.

This doesnt work either from ATI->   IP 10.0.0.10 is my NAS  \\10.0.0.10\backup\chris  - I get nothing.

From Win10 ANV, \\10.0.0.10\backup\chris works fine.

Whatever method I have used to create a NAS backup, ATI 2017 always stores the the location as \\DISKSTATION\home for the credentials.

Ian

Anyone with this issue willing to try this other fix as a possible solution?  I know it's for different behavior, but it was confirmed to work by another user for the initial problem (launching Acronis would cause the cable modem/router to bootloop).  

if you open the .bat file script you'll see it's adding firewall blocks to Acronis NAS search criteria.  It can be reversed as well and am wondering if this would put the NAS behavior back to that of 2016 (note the drawback that you can't use the "NAS" button after this, but would have to use the browse or network option to connect instead). 

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

OK.  This went faster than expected.  I loaded up a new UEFI Windows 10x64 vm in VMWare Workstation 12 using the Windows 10 anniversary update (version 1607 build 14393.82)

I took all the default fast settings to speed things up, I activated it, I ran all Windows updates, rebooted, and checked for updates again - there were no more. 

I installed VMWare tools, rebooted.

I installed Acronis 2017 build 5534 (see screenshots to make all of yours is exactly the same in size, version, etc - curious Steve as you have that small office name on your WinPE)

NOTE:  AT NO TIME DID I EVER CONNECT to the NAS shares from directly within Windows during testing - everything was done strictly through Acronis with no NAS connections ever being made from within Acronis yet. 

TEST 1

I created 1 new backup task.  Selected source as the vmdrive using "disks and partitions" and the destination as "browse" then expand "network".  Upon expanding "network" I see both my WD-Mycloud and my newly revived ASUS AC-1900 router smb share.  I pick the ASUS AC-1900 device and expand it.  It sees the test folder I put there ahead of time.  I click on it and am prompted for credentials. I enter them (this one requires the routername/username for the user) and it says successful for the test.  I "connect" and get a success.  As an additional test, I create a new folder in the first test folder through Acronis - it works. I configure the rest of the backup, launch it and it completes with no issues.

Results = PASS

TEST 2

I created a 2nd new backup task.  Selected source as the vmdrive using "disks and partitions" and the destination as "browse" then expand "network".  Upon expanding "network" I see both my WD-Mycloud and my newly revived ASUS AC-1900 router smb share.  I pick the WD-Mycloud device and expand it.  It sees the test folder I put there ahead of time.  I click on it and am prompted for credentials. I enter them (this one only requires the username for the user, unlike the ASUS AC-1900 which requires routername/username) and it says successful for the test.  I "connect" and get a success.  As an additional test, I create a new folder in the first test folder through Acronis - it works. I configure the rest of the backup, launch it and it completes with no issues.

Results = PASS

So, this is a brand new Windows install with a brand new Acronis 2017 final release install and two different NAS devices connect without issue in my testing.  I also have a desktop and a laptop that upgraded from 2016 to 2017 beta 1 then beta 2 then the final release that can access both of these NAS devices without issue as well.  

On my VM, I only have Windows Defender.  On my PC and laptop I use Windows Defender and Malwarebytes Antimalware Pro.  

Could it be your antivirus not liking the new build and blocking some traffic?  Are any of you able to build a fresh window install as a test to rule out some kind of credential issue stored in Windows from a past install?  Can you all verify that your install file looks exactly like mine? If you build WinPE does yours show Acronis True Image 2017 like it should, or is it showing "Acronis Small Business, which may suggest a problem with your installer or application?)

One other note... after the backups, I just expanded both of my NAS devices in Windows and could navigate these shares from within Windows without ever having to enter credentials in Windows.  Apparently, they are being passed onto Windows from Acronis automatically once the backup has connected.

This leads me to wonder if you are experiencing a connection issue I reported in Windows before - that Windows 10 no longer likes it if you connect to a NAS device with multiple credentials.  

I originally found that when I mapped my NAS devices in Windows, if I used the same credentials for the NAS, all is well.  However, if i map them in Windows first, and then connect with Acronis (or any other backup software) with a different NAS account, Acronis connects fine, but then cannot acces the shares in Windwos anymore.  I would then get prompted for credentials in Windows, and Windows would never take the original credentials until I logged off and logged back in, or I manually removed the SMB credentials from Acronis in the registry.  

IF you want an easy test.  Create 2 nas shares with different user accounts.  Map one share in Windows and make sure you can navigate.  Then try to map the other share in windows with the other account.  Does the second share map?  If it does, can you still navigate the first share now? 

Hooray Bobbo!

You have proven that the issue is not the True Image application.  You have proven that with properly configured authenticated smb shares in place navigation of smb shares works fine.  You have proven the issue here is a Windows issue and not that of the True Inage application.  Great work!

I believe your issue with user accounts to the same share with a different user from the same machine if I understand that corectly is that Windows does not allow 2 user logon in a single session.  So log out of first user session then log in with new user session should eliminate the issue.

Bobbo,

Look here for help with the user issue: http://superuser.com/questions/95872/sambawindows-allow-multiple-connec…

I will try this approach and see if it works for me.

One odd thing is that under Network one of the available locations is one of my PVRs (a Beyonwiz T2). The Topfield TF-T6211 would probably also show up as it has SAMBA as part of its Android firmware.

Ian

Enchantec,

Thanks for the link.  I found that if I deleted the smb share in the registry, then I could connect in Windows again.  I'll try the netuse command as well this weekend.  Better security is good; just wish I could have my media share mapped in Windows and have Acronis connect and drop the 2nd session automatically with the scheduled backup so that the disconnect from the media was only temporary and self-healing.  If netuse works, I may try adding a post command to kill the connection and see if running the scheduled task would then automatically connect or prompt for credentials. 

In my earlier tests, I didn't have any luck fooling windows using the mapped drive in Windows with IP and the Acronis connection via hostname.  Been awhile though so I'll probably need to test again to be sure.  

OK, Net use, is a no-go unless you've actually mapped the share as a drive letter - it just says that ther are no active sessions, because I have not actually mapped one with a drive letter.  Instead, I'm just expanding "network" in Windows Explorer.

However, getting closer.  When I have not connected to any shares in Windows yet (via the expansion of "network" in Windows file explorer), and then run the backup in Acronis to the NAS share... I can then can navigate those shares directly in Windows file explorer without needing to provide additional credentials...  BUT,  when I close the Acronis console, that does appear to close the network session and I am once again prompted for credentials in Windows file explore again - which is good.  I believe that is what was throwing me off before as I assumed it was keeping it open indefinitely for the active Windows logon session, but doesn't seem to be the case.  I was thrown off because I was keeping the Acronis console open during all of that testing and that was preventing me from being able to use another NAS account to authenticate with my media shares.  

I think I'm all set now and have a better understanding of how the credentialing is working in both Windows and Acronis now. I hope it helps everyone else who is having credential issues too. 

Indeed Acronis seems to have a problem, if you want to select a network share as backup source or backup destination, if this share is currently mounted in the windows explorer.
If I start acronis as adminstrator within a regular user session, i.e. regular user means user without administrator rights, I have the subdirectory problems. If I start windows as adminstrator and use acronis
I have no problems to browse in subdirectories of my NAS share at all! The reason for that seems to be obvious. I have my personal data (documents, music, pictures, videos) on my NAS. The share is automatically mounted logging in as regular user into windows,
but not, when I use the admin account to login.

Would it be workaround to login as admin and start all backups involving my NAS share manually?

No! After using acronis, logged into windows as admin, my network configuration for my share is destroyed for the regular user, as soon as I log in as regular user. I have to reconfigure everything!

It might be, that the deeper problem for this is a windows 10 speciality (I use the new release 1607), but other backup programs have no such problems to deal with such circumstances.

I have no problems doing the backup jobs on my NAS with AOMEI Backup, for example.

I read all the posts and possible fixes and workarounds.  THX for analysing this problem.  I use the requested user configured in the NAS to secure the access to the NAS devices.  In this case I use the same User/Pw Combination to logon to Win10 and to the NAS devices. (Later on I will try this with different credentials)   

Meanwhile I try to use the IP adress of the NAS instead of the mapped device.  With the IP adress I can access all subfolders without problems.  The IP accces is shown under the "Network tree" in Acronis. This access can be done while other connections with the same user via explorer and mapped devices to the NAS are open.   

I still can't access the mapped devices to the NAS shown under "This PC". If i do so, the will be a short message "Checking credentials" und then A"Please wait". No more reaction of the program and i have to kill it via the taskmanager. No Error message or so. 

This is a behavior a good program should not show. I'm not convinced that the Acronis 2017 have no issue. Until I updated from the Acronis 2014 (!) to the 2017 no backup issue came up. The rest of my system didn't change. All other access to the NAS devices are still in best condition

I didn't get the derivation why the credentials suddenly with the 2017 acronis are getting a problem.

2014 can handle it, 2017 no more ?? 

It is most perplexing; these issues were not in the first beta of ATI 2017. They appear to be due to something that changed after the release of that beta. Backup tasks to NAS created under beta 1 still work, but I can no longer successfully create backups to folders.

Ian

Many users state, that using the ip address instead of the host name is a possible workaround to connect to the share, because windows is not intelligent enough to recognize that it is in fact the same host.

I assume that windows became more intelligent with the anniversary release (release 1607), because the workaround does not work for me.

I do not understand up to now, why Acronis tries to establish a further connection if a connection to the NAS share already exists.

All other windows programs I have tested do not have any problems to read and write files.

Alex

HI guys, I think you missed a note I provided above.  

You are all correct that there is a limitation (kind of) that only one Windows credential can be used at a time.  However, I am successfully using a setup on my NAS that has 2 sets of credentials
 

1) the first is directly in Windows using one NAS account to my media folder - this is saved in Windows credential manager and automatically connects to those shares in Windows as soon as I log on

2) the second is an account in Acronis that also goes to the NAS, but a different network share with a differen nas account.  When I configure this in Acronis, it connects successfully and runs the backup

HOWEVER, while the backup is running, or while the Acronis GUI window is open after this connection as been made, then my original NAS connection using the Windows stored credentials does fail to connect.  This is by Windows desgign (I believe).  The problem in all of my testing, which took me some time to figure out is that as long as the Acronis GUI is open after running that backup, the 2nd credentials take presedence in Windows, preventing the first stored credentials from working.  BUT, once the backup is complete, when I close the Acronis GUI and close Windows file Explorer (any open folders) and open again, then my original stored credentials in Windows work again.  So, it is working as designed, but you have to close the Acronis GUI to close that session out.

I believe Macrium has figured out how to close the session as soon as the backup has completed, even if the GUI remains open.  I will have to test that more today.  However, neither method is wrong - just a different way of approaching it.  With Macrium's method (if this is correct), you would have to provide credentials to map to that location again, but would have easier access to your media shares.  With Acronis method, they are keeping the path to the backup open so you can get to it more easily, but this is preventing the media shares from being accessible while the GUI is open.  

Simply closing the Acronis GUI, gets everything working for me and most of the time, my NAS backups are scheduled anyway, so the GUI doesn't come into play anyway.  I think we're all leaving the GUI open and tring to have more than one connection going at a time and that's why we're seeing this behavior.  

I just tested with Macrium Reflect Free version 6.2.1502 - actually, the behavior is worse (for me) in Macrium than Acronis and here's why:

While I have my media share credentials stored in Windows credential manger so that I can access my videos and music on the NAS more easily, within Macrium Reflect, I am unable to authenticate to the same share location within Macrium as I am always prompted for Windows Credentials (as initiated by Macrium).  The result is, that you get a Windows message stating that only one connection can be made using the same account and it won't let you proceed.  Acronis handles this differently and appears to do this better (in my opinion) as this does work in Acronis just fine.  

That said, if you are using multiple backup accounts/shares with different products (like Acronis and Macrium), then you should use a completely different share and set of credentials for each backup product - using the same account is going to cause more headaches than they're worth since each product is handling authentication slightly different.  Again, I repeat, if you're using different backup software products, please make sure you have separate NAS folders and use a different NAS credential for each product.  See attached screenshot of the Windows authentication error.

I also want to point out that the behavior in Macrium with the Windows credential is the same as Acronis.  If you have your media credentials stored in Windows Credential center and can access your shares in Windows file manager directly, but then run a backup (in any backup product - Macrium or Acronis) that uses different NAS credentials, you will get access denied trying to access your media share in Windows during this time.  However, here is where (to me), Acronis is handling this better than Macrium.  Unlike Acronis, which releases the used credentials in the backup after you close the application GUI, Macrium does not (at least not in my testing).  After the backup to my NAS runs in Macrium and I close the GUI, I can still only access the backup share through Windows File Explorer and my media shares that use the stored Windows credential manager are denied access.  

The only way to resolve this is to open an elevated command prompt and run "net use" which will show a persitent mapping of the share that Macrium created.  You can then type "net use \\whatever_netuse_shows_you /Delete" to kill that persistent connection, refresh Windows file explorer and you'll have access to your media shares (the ones using your stored Windows Credentials in credential manager) once again.

Hi Bobbo,

my problem is, that I want to use the NAS share as backup source, not as backup destination.

I want to backup all my documents, pictures, videos and music to a usb drive.

I always start my backups manually.

This was always possible with Acronis True Image 2015 or AOMEI Backup.

I do not want to unmap the share before, because I do not want to interrupt my work while backupping.

Is there any solution to backup my user data with Acronis True Image 2017 without unmounting my share in the windows explorer?

I believe the same applies for source and/or destination when it comes to Windows credentials now.  I can repeat this behavior in Macrium and Acronis so don't think it's product specific.  I didnt' try AOMEI or EASEUS yet, but I think it's going to be the same... if using different credentials to try and access the NAS at the same time, Windows will hold the last credentials provided and that's what is available in Windows.  Afterwards, when you close the Acronis GUI, then it will revert back if you have different credentials being used in Acronis on one share, but different credentials for a different NAS share that connects to Windows explorer automatically.  This looks to be a Windows limitation now, not Acronis or Macrium.  

I think you'll be OK though.  If you are already mapped to you NAS with a Drive letter after using the "map network drive" feature in Windows file explorer, when you select your source, go to "files and folders" >>> expand "desktop" >>> expand "this pc"  >>> expand the drive letter you have it mapped in Windows as.  You shouldn't need to do anything else since it's already mapped in Windows and you're accessing it as a Windows drive and not a NAS drive at that point.   

I don't have any issues accessing sub folder(s) (no matter which method I choose) while using Macrium.

I don't have this issue with any software I use - just ATI 2017.

Chris

Bobbo_3C0X1 wrote:

I believe the same applies for source and/or destination when it comes to Windows credentials now.  I can repeat this behavior in Macrium and Acronis so don't think it's product specific.  I didnt' try AOMEI or EASEUS yet, but I think it's going to be the same... if using different credentials to try and access the NAS at the same time, Windows will hold the last credentials provided and that's what is available in Windows.  Afterwards, when you close the Acronis GUI, then it will revert back if you have different credentials being used in Acronis on one share, but different credentials for a different NAS share that connects to Windows explorer automatically.  This looks to be a Windows limitation now, not Acronis or Macrium.  

I think you'll be OK though.  If you are already mapped to you NAS with a Drive letter after using the "map network drive" feature in Windows file explorer, when you select your source, go to "files and folders" >>> expand "desktop" >>> expand "this pc"  >>> expand the drive letter you have it mapped in Windows as.  You shouldn't need to do anything else since it's already mapped in Windows and you're accessing it as a Windows drive and not a NAS drive at that point.   

 

 

Dear all,

I am using the same credentials for Windows AND the NAS. Win 10 is the latest build now and everything worked fine with Acronis TI2016. After switching to ATI2017 ii did not work anymore, neither using mapped drives nor listings of directories or anything else as source or destination. Maybe all your explanations describe the behavior correctly. But as a customer I do not want to think about what has to be changed for my actual operation system if the latest software version did its job perfect and the newest does not.

For me it is obvious that Acronis changed something that worked in 2016 with the actual Win 10 but does not in the 2017 version.

ChrisK wrote:

I don't have any issues accessing sub folder(s) (no matter which method I choose) while using Macrium.

I don't have this issue with any software I use - just ATI 2017.

Chris

I don't have the problem in either Acronis or Macrium and am trying to explain the limitation of the credential issues as to relates to Windows if you have multiple DIFFERENT logons trying to be established to the same NAS at the same time.    

Most people with a simple setup that use the exact same credentials to access their NAS in Windows as they do in Acronis  should not have an issue.

However, those of us that are trying to be security conscious and have some NAS shares open to Windows at all time (media shares), but other backup shares only accessible for the backup applications (Macrium or Acronis) that run under a different account to the same NAS device backups are the ones most likely to be seeing this issue.  

I can reproduce the error in both applications f using multiple NAS connections to the same device at the same time where different credentials are being used to access the NAS at the same time.  Again, if using only one set of credentials, there should be no issue.

Chris, if you care to test the theory, create a new test user account on your NAS and a new test backup folder that is not in the same directory as your existing one.  Run a backup to your test and then try to access your first (Original) location in Windows and see if it still connects - I'd bet money that it won't and that's what I'm trying to convey here.

If you're willing to let me webex onto your machine, I guarantee I can produce the same behavior in Macrium too.

Proof - straight from the Marcium Forum (instead of linking, I am just posting the screen grab).  This also explains what I stated above about needing to use net use to disconnect a Macrium NAS backup.  If you have both Macrium and Acronis running, anytime you launch Macrium, that mapped share trumps what is in the Acronis registry settings and will continue to break the Acronis NAS connection until you use net use to drop the connection or log off the Windows session to close the net use connection.  

Macrium and Acronis aside - you cannot have 2 different Windows logons to the same NAS device running simultaneously - it is a Windows limitation.  If you use use the same credentials in Windows as you do for your backup in either Macrium and/or Acronis, there is no issue and all products will function together just fine.  

Bobbo_3C0X1 wrote:

Proof - straight from the Marcium Forum (instead of linking, I am just posting the screen grab).  This also explains what I stated above about needing to use net use to disconnect a Macrium NAS backup.  If you have both Macrium and Acronis running, anytime you launch Macrium, that mapped share trumps what is in the Acronis registry settings and will continue to break the Acronis NAS connection until you use net use to drop the connection or log off the Windows session to close the net use connection.  

Macrium and Acronis aside - you cannot have 2 different Windows logons to the same NAS device running simultaneously - it is a Windows limitation.  If you use use the same credentials in Windows as you do for your backup in either Macrium and/or Acronis, there is no issue and all products will function together just fine.  

Hello Bobbo,

as said in an earlier post I use the same logon for Windows and the NAS. Also I use no other connection to the NAS while I'm trying to access the subfolders with the mapped device and there is the described issue.

I installed the acronis 2017 version over an installed 2014er version, may the issue caused in this fact ?  What about a try to make a clean deinstall und  a new plain installation of 2017 ? Can I use the clean utility link in your footage ? Can the tool be used for the 2017 version ?

I also use the same username/password combination both for mapping my share in windows explorer and in acronis. I have a fresh Acronis True Image 2017 installation and I cannot backup my NAS share to a USB drive, cause of the subdirectory problems. Before installation of AT 2017 I used the Cleanup utility.

I have not seen this issue with my backups to USB drives - I assume that the USB HDD are attached to your computer not to a NAS. However, the three USB 3 HDD that I am using are not recognised as removable media - they are treated the same way as hot-swappable internal HDD, which could explain why I have not seen this.

The drives I have are Seagate Expansion, WD Elemenets and a Hitachi.

Ian

Yes, my USB drive is connected with my computer. I want to backup my pictures, documents, videos and music of my NAS to the USB drive. This is not possible, because I cannot select the share or any subdirectories of my NAS, although I use the same user/password combination as I used to mount my share in the windows explorer. This is definitely not a problem of my USB drive, because the problems occur already when I want to select the NAS share as backup source. At this time I have not yet selected the USB drive as backup destination.