TI2017 - Network test connection authentication fails - but works if I use IP address instead !!

Neil,

In most cases like yours the issue is a problem with the Domain Name Server or DNS.  You should investigate if the DNS is working on your network.

Or it's the possible bug with 2017 v5554 not liking mapped drives when you go to test or pick the destination. Several of us are reporting that if you have the same mapped drive in Windows already, even if using the same UNC patch and network credentials, this version fails the test. The work-a-round is to drop the mapped drives in Windows temporarily, setup the NAS connection in Acronis and test/authenticate and once successful, then you can run the backup and go back and map the drives in Windows again. The backups to the NAS should continue to work, but if you test the connection with the mapped drives in place, the test will still show that it fails, but the backups should still run fine.

https://forum.acronis.com/forum/126528?page=1#comment-395178

Cross posts:

https://forum.acronis.com/forum/125800#comment-395366

https://forum.acronis.com/forum/126528?page=1#comment-395276

and this one now: https://forum.acronis.com/forum/126839

Bobbo_3C0X1 wrote:

Or it's the possible bug with 2017 v5554 not liking mapped drives when you go to test or pick the destination. Several of us are reporting that if you have the same mapped drive in Windows already, even if using the same UNC patch and network credentials, this version fails the test. The work-a-round is to drop the mapped drives in Windows temporarily, setup the NAS connection in Acronis and test/authenticate and once successful, then you can run the backup and go back and map the drives in Windows again. The backups to the NAS should continue to work, but if you test the connection with the mapped drives in place, the test will still show that it fails, but the backups should still run fine.

https://forum.acronis.com/forum/126528?page=1#comment-395178

I Ditched the map drives to my Win 7 server and re-tried browsing the network to the backup location. It went straight to it and the backup runs too. So almost certainly the bug Bobbo described above and nothing to do with DNS. Thanks, Neil

Hello all,

If you still experience the issue with access to NAS, please proceed with the steps described in the artcile, where we have posted all available workarounds and custom fixed .dlls (you'll need to install build 5554 in order to apply .dll files with fix) 

59051: Acronis True Image 2017: Connection to NAS fails with errors "Connection failed", "Failed to check credentials", "Can not find files and folders".

Thank you!

 Genius Bobbo! I'd been searching for a solution to my authentication issue for a couple of hours and tried many things before I came across your post - and it worked first time.

Many thanks, Geoff

Glad to help Geoff.  Acronis has since created a temporary patch in the meantime so you don't have to drop the network shares each time until the updated version is released:

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

Oops, disregard my post above.  KB59095 is actually for a different bug.  If you've already replaced the files mentioned in Ekaterina's post above, you don't want to install the 5555 patch as it will replace those.

Another easy way to get around the bug, without having to drop the network shares is to go to control panel >>> administrative tools >>> computer management >>> services 

Locate the "workstation" service and simply stop and start it again before you go to setup a new NAS connection or edit an existing one.  That seems to do the trick as well and may be easier if you have a lot of mapped drives to reconnect. 

Thanks for the update. Fortunately I just have a single NAS share, so it's easy - and now it has accepted the password, I can use True Image fully without dropping the share again. I'll keep this thread bookmarked in case it starts objecting again.

Geoff

Enchantech wrote:

Neil,

In most cases like yours the issue is a problem with the Domain Name Server or DNS.  You should investigate if the DNS is working on your network.

sorry , but how did you get MVP when this is such an obvious and well known issue..DNS..major facepalm I'm afraid! Thanks Bobbo

DNS is a common issue with some NAS if using DHCP in the network as the pc or NAS may pick up a new up at some point, but not register with the other device until it is rebooted or flushes its local DNA cache. 

In other versions where this bug is/was not present, I would also suggest it as a possible fix if other solutions haven't worked. It took awhile to identify the bug and Encantech and I were some of the first to test and troubleshoot. Prior to that, the KB wasn't available for the fix.

Main thing is we have an Acronis provided workaround now. All of the MaVPs offer their own personal time and expertise and if you note Enchantech's nearly 5000 posts, you'll see why he has a volunteer badge.

Switching the workstation service off and back on did not solve the problem.  Still getting the connection error when trying to change the original back up to the NAS drive.  I have also installed the 5555 patch.

Kent, I don't see any previous posts from you in this topic so not really sure what problem you are having here?

What do you mean "Still getting the connection error when trying to change the original back up to the NAS drive."  Are you able to connect when using the IP Address but not when using the NAS device name?

Hi,

Sorry, I thought I posted to a thread with similar issues I am having.

I am using ATI 2017 and bacfking up to a shared drive another computer on my network.  I created my back up scheme sucessfully and actually ran a back up.  Now I want to make changes so I bring up the back up, click on options and I get a screen that asks me for my credentials.  I enter the credentials in exactly the same way as I did when I created the back up, and get a connection failed message. I have full control access to the shared drive on the other computer which is mapped on the sending computer.

Another strange thing is when I cancel out of the authentication settings screen, is seems to connect with the drive anyway.

Windows 10 Prof. on both computers

I believe you have encountered what I consider to be a bug in the credentials prompt given by the application.  It is safe to cancel out the prompt and proceed with your intended action.  If you do enter credentials under this particular circumstance then the connection failed message is being intiated by Windows rather than the application and is due to the fact that Windows only allows one authenticated connection to a connected network device during any one computing/network session.  As you are already logged in to the network share any further attempt will result in the error given.

Thank you.  Do you see a solution to this annoyance in the forseeable future?

I would think that it would be fixed in a future update or newer version of product.  There have been a number of changes with Windows 10 security, SMB protocol, and network security which have brought problems for network connectivity in general.  Such things eventually get ironed out but I would have no idea of a time frame for fixes.

Kent, did you apply the hotfix files form this thread as well?  If not, that is the solution until the next official Acronis release

59051: Acronis True Image 2017: Connection to NAS fails with errors "Connection failed", "Failed to check credentials", "Can not find files and folders".

Resolution

1. Replace TrueImage.exe and ti_managers.dll with fixed versions

Bobbo_3C0X1 wrote:

Or it's the possible bug with 2017 v5554 not liking mapped drives when you go to test or pick the destination. Several of us are reporting that if you have the same mapped drive in Windows already, even if using the same UNC patch and network credentials, this version fails the test. The work-a-round is to drop the mapped drives in Windows temporarily, setup the NAS connection in Acronis and test/authenticate and once successful, then you can run the backup and go back and map the drives in Windows again. The backups to the NAS should continue to work, but if you test the connection with the mapped drives in place, the test will still show that it fails, but the backups should still run fine. https://forum.acronis.com/forum/126528?page=1#comment-395178

I tried your suggesting of unmapping \\DS415\Media Library, then I was able to authenticate in Acronis.  However, I am unable to drill down into any directories on the NAS.  I tried remapping the drive, then started Acronis, and same thing.  I am not prompted for credentials, I just am unable to see any subdirectories.

-Thanks

Bernard, same question for as posed to Kent - have you applied the hotfix?

FYI, new version of 2017 was released today, so far, in the little testing I've done, NAS connectivity is better - especially in regards to authentication

I would also avoid using the hostname of a remote share or even the new NAS setting in Acronis. I stick to the full UNC path using IP address, and have not had most of the issues that others report when they use hostname or the NAS automatic setting.

Click on destination >>> network .... at the top, there is a path bar you can type in directly.  Type in the full UNC path using IP address such as:

\\192.168.1.50\NAS_Backup_Share\Acronis_Backups (or whatever you would use instead)

At present there is only a new build for 'subscription' customers. You could always install the subscription version and request a trial serial number.

Ian

Thanks I'll give that a try.