NAS drive not authenticating
Hello and thank you,
The 2 HOT FIXES solved my authentification problem to my Windows 10 backup desktop.
Did not even have to use the IP address of the backup server.
It even remembered, correctly, the old back tasks, and all the option configurations for each task.
Dietmar
Dietmar, that's great to hear about the hot fixes resolving the authentication problem for you, thanks for giving feedback.
Hi all
Ok, just to add my name here, as I spent another night away with ATI. Using it since 2009.
First I had to find out that TI 2017 doesn't support actual email policies and I needed to make Gmail accept 'old unsecure' clients. (yes, offtopic, but, you know, what the heck, this is 2017... ?)
Tried to change backup settings. Password fails. Then backuptask fails too, no login. Well, after finding infobits here and there that the new NAS-managemant fails on devicenames like 'diskstation', I tried to move the backup from //diststation to //192.168.1.41, what failed (didn't want to loose all versions, again). TI ccould not find the snapshot-libraries after that. PC Restart does not help. Repairinstall TI (again).
Finding more information. Deleting credentials in the registry. Disconnet Nas-drives in explorer. Backup task runs and validates (without asking for any login). Phew. Changing options still do not work: asking for win user account credentials, what fails. (?)
Now I hope and pray that I can trust validation. I don't feel like boot save mode and tinker some more. Guessing the two files hotfix could work in my case. But mybe next year. :p Windows 10, DSM 6, all and every software up to date. Need to say: I use a 512GB M.2 drive, no SATA, ASUS board (linux recovery does not work, needs bartPE; killed my PC activating rescue boot option F11 once).
With the notebook (all the same symtoms) Changing to ip adress works as intended. New backup task.
Im bound to TI till 2018 now. But guessing buying the more expensive webspace (as in fact I do not need the performance and availability) in EU afterwards and move on with Synology (Cloud Station, it backup to webspace). This I use also since years and, mostly, just works. Plus some simple imaging software without those neat gimmicks. (Synology's DSM 4, 5 and 6 was/is just a better user experience over time, imho. Minimal, but does the job.)
I'm aware of that this is complex software -- but failing on sending email and common networkconnections after update, leaving users to boot save mode after reading for hours: That's just **** you know. If I were a salesman making deals like this... no good. How much work doing a quick installer? Half an hour?
I reactivated my network share and will see what will happen next backup run. Enough rant for now.
Samuel
Hi all,
Where can i download the last build 6116 of ATI 2017 ?
Thanks
See webpage: http://www.acronis.com/en-us/homecomputing/thanks/acronis-true-image-2017-premium/ but please understand that if you have a perpetual license currently, that installing this update will convert you to a subscription license at an additional cost.
The alternative is to wait until you are advised that an update is available for your installed version of the product, which should be expected in a month or less.
Because of the authentication issues with TIH2017 (build 5554), AND getting an update email from Acronis for TIH 2017 Next Generation (NG), I installed NG just to find out that it was a trail license. This was very upsetting since I had just upgraded from 2015 a few weeks ago. I did not even try NG and tried to reinstall 2017 with the 2 hot fixes, but could not get it to authenticate.
I installed the reliable 2015. I also was told that 2017 NG was not an upgrade to "regular" 2017, and will have to wait for the update to regular 2017. What a bust!
... getting an update email from Acronis for TIH 2017 Next Generation (NG), I installed NG just to find out that it was a trail license. This was very upsetting since I had just upgraded from 2015 a few weeks ago. I did not even try NG and tried to reinstall 2017 with the 2 hot fixes, but could not get it to authenticate.
I installed the reliable 2015. I also was told that 2017 NG was not an upgrade to "regular" 2017, and will have to wait for the update to regular 2017. What a bust!
My thoughts on upgrades like this. (Other people surely have other opinions.)
Even if NG were an upgrade to "regular" TIH 2017, installing it before checking on forums like this would not be a good move. All new releases can have bugs or peculiarities that might make it inappropriate. I would advise checking here before upgrading just to see what people are saying about an upgrade.
Hi Patrick,
A new update ATI 2017 build 8029 is now available, AND IT'S WORK !!! the nas authentification problem is resolved ! Amazing.
Ditto for me, I had this problem on my computer with build 5554 and the issue is resolved after upgrading to build 8029. I deliberately ignored the patch 5555 in order to prove this would be the case.
I saw that and installed it yesterday. Looks pretty good. I won't have a chance to test things for a couple days, but I'm glad to see it's getting good reviews.
One thing that isn't fixed (and may not be an Acronis problem): ATI still cannot connect to a Western Digital Gen 2 MyCloud FTP server. I was hoping (without reason) that it might be fixed by something in that list of corrections but it wasn't. I think the problem is on the Western Digital side.
Hi Guys,
Thanks for the ATI 2017 Build 8029 information.
I updated my sytem and so far the issues with NAS login has been fixed and also the issue with ATI not been able to delete old backups from NAT was also fixed.
It took a while, but I am glad they fixed it.
... but NOT fixed in Bootable-Media :-(
Neither with Linux nor WinPE-Media I can login to the network-path of my Synology.
Have you recreated the Bootable Media since the upgrade?
It works for me in WinPE. I havent' tried the Linux media as I must use WinPE for my RAID setup and NVME hard drive.
With all WinPE, you must use a command prompt net use command to first map the drive as a letterr - this is a Windows limitation of networking in WinPE. Or, you can use command prompt to navigate to A43 file explore and once launched, it has a map network drive option that does this via a GUI. Better yet, build your WinPE using the MVP WinPE Builder and use A43 and see how that works - if you use the advanced version of the tool, you can easily open a43 from the launch bar without needing to deal with the command prompt. Link for the tool is below and also in Steve's signature.
For reference, take a look at net use commands so you understand how they work.
https://www.lifewire.com/net-use-command-2618096
We'll add a mapped drive option in the next release of the MVP tool... still can't say when that will be, but it won't be too far along.
... but NOT fixed in Bootable-Media :-(
Neither with Linux nor WinPE-Media I can login to the network-path of my Synology.
Same here for my NAS setup at home (external drive attached to a TP-LINK router) as far as Linux and I have created bootable media for build 8029. When I have some time I'll try again with WinPE but I'll need to download and create that media.
I have a Synology NAS at my office but I won't have a chance to test there until Monday or Tuesday.
How do I stop getting email notifications on this thread? I tried to stop getting notifications by clicking on the link in my email, but that is not working...
Dietmar, there is an option on each post that you submit to the forum, where you can untick the box for "Notify me when new comments are posted" which should unsubscribe you from further notices on that single topic.
For those with bootable media Nas logon issues...
I just tried 8029 - default linux rescue media that the .iso was mounted into the virtual CDROM of a test VM and booted directly to.
I'm running Windows 10 x64 1607 (14393.693) on all of my home systems and VM's.
I'm using a WD MyCloud 4TB with slightly older firmare - v04.04.03-113 (haven't bothered to upgrade to the latest as this has been working great and am afraid WD is going to break things if I upgrade again).
The rescue media logged into my NAS share using both the "computers near me / workgroup" option and the "my nas connections" where my NAS was listed there as well. In both cases, I did NOT need to enter the NAS IP (Or name)\password as the username. I just used the logon name and password of the NAS and both connected successfully the first time. In older versions of the media, I seem to remember having to enter the username as NASNAME\Username and then the password - have you tried both methods?
I will note - all shares on my NAS are in a seprate folder, and not connecting directly to the root folder of the NAS. I have heard of NAS devices not liking remote authentication directly to the root folder - if your share is the root, try creating a folder in it and making a new share to that and connecting to that instead.
----------
On another note, my Windows share was interesting. Using the same rescue media, when I map the share from another computer, I have to use my livemail account email address and my livemail password. However, on the Linux rescue media, that fails everytime. This account was originally a local account windows acount and converted to a livemail account. From the Linux rescue media...
livemail email + livemail password = fail
livemail email + local account password = fail
local account name + local account password = fail
local account name + livemail password = success
No idea why that is.
local account name = livemail passsword = success
No idea why that is.
I tried the other un/pw combinations but not that one. I'll give it a shot and see what happens.
I'm on a Windows 10 machine by the way.
local account name = livemail passsword = success
No idea why that is.
I tried the other un/pw combinations but not that one. I'll give it a shot and see what happens.
I'm on a Windows 10 machine by the way.
local account name = livemail passsword did not work for me
Steve, is your share on a NAS or another Windows box though - you mentioned up above that you're trying to connect to a synology share? The Synology NAS credentials would be something different than what you would use to authenticate to Windows so a livemail account would not come into play for that at all.
On the synology share:
1) Is it the root folder or something else? If it is the very root, try creating a share that is at least one folder deep.
2) Try NASNAME\Username and password
3) Try just username and password
Steve, is your share on a NAS or another Windows box though - you mentioned up above that you're trying to connect to a synology share? The Synology NAS credentials would be something different than what you would use to authenticate to Windows so a livemail account would not come into play for that at all.
On the synology share:
1) Is it the root folder or something else? If it is the very root, try creating a share that is at least one folder deep.
2) Try NASNAME\Username and password
3) Try just username and password
I have two different locations using ATI; my home and my office.
At my home my "NAS" is an external drive attached to a TP-Link router. At my office I have a Synology NAS.
The testing I'm doing now is at my home so what I'm trying to do is access the ATI backup on the external drive attached to the router's USB port. ATI can back up to it fine, and restore using the installed ATI application, but I can't get past authentication using the Linux bootable media. At my home location I can always just move the external drive from the router to the the PC if I need to restore the PC using bootable media so it's not the end of the world. I would just like to figure out now to make it work as it should (or at least how I think it should which may not be one in the same).
I haven't been to my office to test bootable media restore from the Synology. I won't be there for a couple of days yet but I'll report back on that configuration once I've tested.
None of my backups are at the root by the way. They're all one level below root.
Steve C,
Have you tried connecting to the share at home by using the "Computers near me" path and the "My NAS connections"? Does your TP Link router appear in both of those locations? What error do you get when you try to connect? Can you drill down into the share to the folder level where you wish to store the backup or not? Is your error a "Connection Failed" error after entering your username password? You are on an upgraded install?
Hello,
I just updated to build 8029 and I am really getting crazy now. With build 5555 evrything worked for the NAS. Now with the actual build I have no chance to get any backup on the NAS. Credentials will work for the root of the NAS but unfortunately we have subdirctories where the useres are located. Getting to one subdir leads to a second request for credentials which fails. I tried all possibilities now (IP, NASname, etc.) but still it is impossible te get any beckup to run.
In detail the procedure that fails is as follows:
1. connecting to \\root -> ATI requests credentials -> NAS accepts but user is not allowed to write as it is not its home directory
2. connecting to \\root\xxx -> ATI requests credentials again -> failure, no connection possible
3. connecting to \\root\xxx\user_home -> ATI requests credentials again -> failure, no connection possible
Why is ATI always asking for credentials? It has the access from connecting to the root directory.
Does anyone have an idea how to get it to work?
At the moment this build is not usabel for me in its actual version. I will switch back to build 5555 now until this bug is fixed.
Nico
Nico,
Are the credentials for root and user share the same? I would think not. When asked for credentials do you see an "Edit Credentials" button on the credentials popup? Using the location field at the top of the destination screen can you manually input the path to the user folder using the keyboard then, once you have the path threre look to the right side of the path acn click the carat that you should see. This will bring up a popup that should allow you to Edit credentials. Input the credentials for the user here and see if that makes a difference. You whould try this after you have completely shutdown your computer and then powered it back on.
Hi Enchantech,
thanks for the reply. Unfortunately it is not working in any case.
To clarify the situation. We connect by the user credentials on the root directory level, not as root user. The user and the pwd are then the same to have access for the home directory that is located two levels below.
ATI is requesting user credentials at the very first level to access the server. I can put them in and be allowed to go on to the subdirecotry where ATI asks me for the credentials again. The user and pwd are still the same as we are working on user_level but ATI tells me that connection is impossible (maybe because I am still locked in.
Trying to start directlc with \\root_dir\dir_lev_1\home results in the same error message and no connection is possible.
As a last consequence it also means that I do not have access to the former backups as ATI cannot get them.
Situation is really worse.
Hi Enchantech,
thanks for the reply. Unfortunately it is not working in any case.
To clarify the situation. We connect by the user credentials on the root directory level, not as root user. The user and the pwd are then the same to have access for the home directory that is located two levels below.
ATI is requesting user credentials at the very first level to access the server. I can put them in and be allowed to go on to the subdirecotry where ATI asks me for the credentials again. The user and pwd are still the same as we are working on user_level but ATI tells me that connection is impossible (maybe because I am still locked in.
Trying to start directlc with \\root_dir\dir_lev_1\home results in the same error message and no connection is possible.
As a last consequence it also means that I do not have access to the former backups as ATI cannot get them.
Situation is really worse.
Hi @ Nico Scharnagl ,
Is this when backing up, or restoring?
If Restoring, are you using the Bootable Rescue CD or using a copy of Acronis True Image to restore from another partition = operating system, on the same computer?
Have you tried to Map a Specific Folder to the operating system as a Drive Letter?
> As a last consequence it also means that I do not have access to the former backups as ATI cannot get them.
Use Add existing Backup.
The problems with credentials exists for any activity. There is nor difference neither at backup nor for restore. In any case ATI is blocking the access to the home directory where the data are saved. This is also the truth if I use IP instead of server name or if I address the directory by a drive letter.
I know the way how to include former backups. As soon as I try to access the home directory ATI requests credentials and is not accepting them although the credentials would be correct.
I tried all thing I described again on a second, what shall I say. Same behavior no effort.
Switching back to build 5555 worked at once. So what was changed to build 8029 that makes it useless for me?
Steve C,
Have you tried connecting to the share at home by using the "Computers near me" path and the "My NAS connections"? Does your TP Link router appear in both of those locations? What error do you get when you try to connect? Can you drill down into the share to the folder level where you wish to store the backup or not? Is your error a "Connection Failed" error after entering your username password? You are on an upgraded install?
I have tried connecting to the volume on the router through "Computers Near Me" and "My NAS Connections". I see it only in "Computers Near Me". For what it's worth, I've never seen the device listed under "My NAS Connections" using bootable media or using the ATI 2017 application installed on my PC.
I've attached a couple of screen shots of what I'm seeing when trying to drill down to the backups. The error message is "Connection failed. Please verify user name and password" The backup files would be found in a path of "volume1\Acronis Backups\Dell 3650 Desktop\"
I am on an upgraded ATI install, build 8029. I downloaded and burned the iso for this build.
Seems that the problem is not only with me.... Also here the problem is coming up while certain directory levels below the root_dir are used....
Let me cite an old wisdom - removing one bug creates ten new bugs..... :-(
These issues keep rebounding. I'm testing out todo backup as an alternative. So far, it handles windows mounts and direct network addresses just fine for both sources and destinations. I've really lost faith in Acronis. The last straw was the $9.99 upgrade offer. When I followed the link, the fine print said if I accept the $9.99 offer, "a yearly fee of $149.99 is due starting with the next billing cycle."
This fiasco appears to have no end. I have been trying to work with the product since they diminished it in 2015. Prior to that, I was a happy customer.
The inability to handle simple tasks reliably, like network accesses, has been a disappointment.
Nico, have you tried the user credentials when prompted at the root instead?
I don't have root shared out at all. however, the moment I click on the NAS, it prompts for credentials. I enter the credentials for the share and then that works for me. However, my shares are just one folder above the root.
Maybe this is just me (did it work before, or is this new for you too?).. but it seems flawed to have no account with access to the root and subfolder and that may be the problem. I believe you need to provide an account that can step all the way though the folder path. If one account only has root access, but not to the next folder, that may not work. Likewise, if you use an account that doesnt' have access to all the folders before it, how can it get there?
I guess, I've always just used an account that can access all folders, so if it is (or has been an issue), I've never noticed it before. Perhaps Linux needs to step through the entire path, folder by folder. Have you tried WinPE instead, which allows you to map directly to the share name (although will require net use commands or the extra tools from the MVP winpe builder). I'll have to play around wiht the Linux media to see if I can replicate the issue - but it's been awjile since I've used it since the WinPE media works really well.
Just about every other backup product uses winPE by default to build the media. Acronis defaults to Linux because it is open source and can be distributed "pre-built". However, you can build winPE with acronis as well and the MVP tool makes it pretty easy. The difference is that you have to download the ADK seperately first, but if you seleect the winPE option in Acronis rescue media builder, it will take you to the download. Then build the winpe with the MVP tool.
I fully agree with Daniel Reinhart. I have installed the latest build of True Image and sure enough it can see my NAS (Public Folder, no credentials) on Win 10 Anniversary Edition (Build 1607). Created rescue media Win PE version and no, it doesn't see my NAS. Click on 'My NAS Controler' and it asks for an ID and a write key - what rubbish. 'Computers Near Me' also no help. ALL of these things including encryption are available on a free program I have mentioned in this thread before - and they work!. I too have been an Acronis customer and user for many many years and actually used to sell it (I run a small IT support business). I had been trying the new version with a view of recommending to a couple of my customers. What a laugh - the product is not worthy of my support at all.
And talking about the upgrade offer which very sneakily then means that you are suddenly a subscription customer rather than a licence owner - have you also noticed that the so called protection against ranswomeware is only available in the New Generation version which appears to be subscritpion only. I wonder if their ransomeware protection only applies to backups on their Cloud rather than backups created on the users PC, removable media or NAS,
I certainly won't be trying to find out that's for sure. Absouletly woeful Acronis. Please send me a customer survey so I can tell everyone how it really is.
I'm not going to defend any bugs. I'm curious how to fix the issue you're experiencing and what is causing it. Why can I authenticate to both my NAS shares in the Linux version and the WinPE, but not you? Why are you prompted to enter credentials before even expanding the shares? Perhaps it is how you are trying to access them? Could you take a look at my screenshots and compare what you see when you try?
- Please note that I never am prompted to authenticate, until I have expanded my shares and then specifically pick one of them. All of my NAS shares (which require a username and password) are seen automatically by the Acronis default rescue media 8029. It is not until I actually click on a share folder that I am presented with the need to enter any credentials. At that time, I enter the credential for that share, and it just works as expected.
- Please also note that on my WD MyCloud - I do NOT have to enter the NASNAME\Username and password. I only need to enter the NAS share username and password. It connects without any issue.
- Please also note I can see the NAS device and shares 3 different ways: "MY NAS Connections" menu (it's listed in the right pane - capture #4) and under "workgroup" (capture #5) and NFS (capture #8).
Screenshots available for review - comparison. For those having issues, it would be great if you could step through each shot of your own and provide them as well.
As for some of the other recent comments/feedback to this thread...
1) WinPE will never connect directly to a NAS share. WinPE requires "net use" to map a network share as a drive letter first. This is explained a few times already. To use "net use" you minimize the Acronis GUI in WinPE and utilize the command prompt in the background. However, mapped shares can also be created using A43 file explorer (which uses net use, but presents it in GUI) and this tool is built into the defaul WinPE rescue media. If you use the Acronis WinPE builder, A43 can be found by navigating to it from command prompt in C:\programfiles\Acronis\TrueImageHome\A43\A43.exe. Otherwise, please try the MVP WinPE creator tool which will make you some nice Acronis WinPE that has a file explorer and puts both A43 and Explorer++ right on the Start Menu so you can do this from there. Has anyone tried to create WinPE rescue media with this tool yet - I'd highly encourage you all to try this. A43 is not Acronis - it is it's own application and has been working for years to connect to network shares. If you can't connect to a share directly with A43 in WinPE, then the problem is something else, not Acronis.
2) $149.99 comment.... The current full price for NG is $80 - there are promos all year long, but that's besides the point. Acronis offered NG as a free upgrade (or at a deep discount) for those who had previously purchased a 2017 subscription as a perk for already being a 2017 subscription holder. For the rest of the year, if you accepted the offer, you get the NG extra security features and and additional free 1TB cloud storage for free or, in your case, possibly $10. 50GB bumpped up to 1TB for $10 or free is pretty decent upgrade for cloud storage space. However, NG is a not just extra features, it is a premium product that costs to have the extra security and 1TB of space. (Like Adobe offers standard and PRO with different features). If you want to keep the premium NG features beyond the prompo that Acronis offered, then, yes, you pay for if you want to keep them when it comes time to renew. This is a common sales tactic throughout the world - let people try it for cheap, some will fall in love and want to keep it and then they charge regular rates. You do NOT have to auto-renew a subscription, if you opted to auto renew at purchase, that was a personal choice. However this can be changed by contacting customer support at any time. When the subscription ends, you can then manually choose to renew NG, or return to the standard subscription, or get a perpetual license, or go in a different direction if you want. If you have auto renewal and don't change before it auto renews, then yes, you'll auto-renew at NG prices since that's what's installed. If you are charged for NG with autorenewal, this can be alleviated by contating Acronis before it auto-renews (makes good personal sense to monitor your financials if you have opted into a subscription plan with auto-renewal), or, you have 30 days from any purchase to ask for a refund or downgrade and receive the difference. None of this is hidden.
You can find pricing on the main page: http://www.acronis.com/en-us/personal/computer-backup/
I googled Acronis return policy and had no issue finding it either - it's the first hit on Google for "Acronis refund policy): https://kb.acronis.com/content/21242
Hi Bobbo_3C0X1,
believe me, I tried all possibel way to put the credentials in. The strucutre of the server is as followos. The server is connected by its name, therefore we need credentials of the users. The home directory is two levels below. We do have no access to any file or directory but our home dir but we have to logon at the root level. However ATI is asking at any level for the credentials and alway tells me they are wrong.
This had worked for build 5555 very well (as well as for all former builds, and still does). Why is this not working with build 8029?
Our IT will never change the way of logon to the servers. So either Acronis comes back to the way before or I have to skip it for the future and keep built 5555.
Nico, given that your situation here looks to be the opposite of that for many other users with regards to the changes introduced in build 8029 to resolve network issues, I would strongly recommend opening a Support Case with Acronis for this issue.
For myself (and other users) upgrading to 8029 fixed the network issues I was seeing, mainly with 'consolidation' (aka automatic cleanup) for backups stored on my Synology NAS where the main backup was 100% successful but the attempt to cleanup old version chains failed with an authentication error (despite having correctly authenticated to make the backup).
It seem from the dialogue above, that you were working fine on 5555 and earlier versions but this is broken for you on 8029 hence the recommendation to open a Support Case. Only Acronis development will be able to get to the source of this new problem in 8029 that you are seeing.
Nico,
You continue to mention a server in your posts but you do not say what that server is. Is this server a Linux based box, a Windows Server based machine, or an off the shelf NAS unit of some sort?
You should not be having to login to the root level of your device and then subsequently log into your user account. I presume when True Image asks for credentials you are supplying the same credentials each time? If not you should be as you should not have access to the root of your device via a user share. If you do have to first logon to the device as root then you have a security flaw in your network.
You should have a look at the KB article below for some suggested troubleshooting guidelines:
https://kb.acronis.com/content/59051
In light of that I agree with Steve in opening a support ticket with Aconis to resolve the issue.
... but NOT fixed in Bootable-Media :-(
Neither with Linux nor WinPE-Media I can login to the network-path of my Synology.Same here for my NAS setup at home (external drive attached to a TP-LINK router) as far as Linux and I have created bootable media for build 8029. When I have some time I'll try again with WinPE but I'll need to download and create that media.
I'm able to see the ATI backups on the external drive attached to my TP-LINK router using the basic WinPE based restore. No credentials required to access.
Just used the ATIH 2017 build 8029 standard (Linux) rescue media this afternoon to backup a Ubuntu desktop to my Synology NAS with no problems after just filling in the prompt for my credentials - this was over a cabled network connection.
Just used the ATIH 2017 build 8029 standard (Linux) rescue media this afternoon to backup a Ubuntu desktop to my Synology NAS with no problems after just filling in the prompt for my credentials - this was over a cabled network connection.
I just tested access to ATI 2017 backups on my Synology NAS using the basic WinPE media a few minutes ago. No problems at all. I was prompted to enter credentials from the net use command, as expected, and all was find from then on. I haven't tried the Linux version but I will when I get a little downtime here at the office.