Aller au contenu principal

How to set network credentials (userID / password) to backup to a network share

Thread needs solution

Previously used ATI 2012 and there was a place to set the user ID & password to use to connect to a network share (in my case a Thecus NAS Simba shared folder). Evaluating ATI 2016 and see nowhere to provide this information.

0 Users found this helpful

The application relies on Windows credentials for such connections. Question, I take it you can see your NAS under the Network directory tree from within the application? If so then you are fortunate as I have found this troublesome in the released 2016 version of the product.

I recommend that if you can see the device in the application but cannot gain access to the shares on the device that you double click on either the share you wish to use or the device itself if you cannot see the shares depending on how your device is setup. This should trigger the appearance of the Credentials logon box where you can enter Username and Password. If you find that at a later time you cannot access the share anymore it means that your credentials have been lost which happens for example when a new network session is started for example if you shutdown and then restart your PC. My advice is to set your credentials using Windows Credentials Manager so that Windows maintains your logon to the device. This should remedy any problems with accessing the device. To find the Windows Credentials Manager just use Windows search feature and type in Windows Credentials Manager then choose it from the resulting list and setup your device and logon credentials there.

I'm using TIB 2014 "Premium" on a Win 7 Ultimate box (only account on it is me) that backs up to a server running Windows Home Server 2011 software via a share- the backup location has a drive letter assigned under Win 7, and TIB sees & accesses it when I set up the backup. I got this latest annoyance ("Enter credentials") when again trying to set up a daily backup after seeing it had not run in 6 days. It seems that I must redo the backup about once a month. It runs OK for a few days and then it doesn't run anymore, hence my username.

No hardware has changed on either machine during this time. I had cloned the SSD and replaced it with a larger drive last month, but the program ran OK for several days after doing so (I found the "fix" for that problem in the knowledge base by recreating the BU). In the backup settings, "Run backup as a different Windows user" has always been blank and remains blank.

In over a year of use, I've never had to enter any account credentials to set up a daily backup, and don't like the idea of my server user & PW being on another piece of software.

Is there a way around this latest inconsistency or do I need to find an alternative software?

Search your Win 7 machine for Windows Credential Manager, open the manager and make certain that your Windows Home Server is listed there.  If not (I suspect it isn't) you can add the server to the list along with your logon credentials and that should solve your issue.

Enchantech wrote:
Search your Win 7 machine for Windows Credential Manager, open the manager and make certain that your Windows Home Server is listed there.  If not (I suspect it isn't) you can add the server to the list along with your logon credentials and that should solve your issue.

Thanks for the advice. I ran the program, and my server is properly listed under Windows Credentials, with a modified date from December 2014. Looking at the drop-down for it, the Win 7 machine account is properly listed there and shows a multi-star password. "Persistence" is listed as "Enterprise", so this does not appear to be the problem.

There are two other listings there, both named "TERMSRV" with a different IP address. One has a modified date of December 2014 and the other March 2015. Each shows the same Win 7 user account as the server and a starred password. Each shows "Persistence" as "Local Machine". I suspect these are log ins using Remote Desktop Connection (RDC).

There are no certificate-based or generic credentials.

Having done computer repair for a number of years, I realize problems like this tend to occur after something has changed. Since nothing was changed (forgot to add I do not automnatically update Win 7 or Acronis), I'm at a loss as to why the backup now operates differently.

I've reverted to the built-in Windows Home Server backup until this is resolved.

Is your server assigned a static IP address or is that address dynamic?  If setup as dynamic I could see that as the problem.

Another might be network folder share permissions, you might wish to check your username of the backup folder under the Security tab in Properties of the backup folder to make sure you have full control for your username.

Enchantech wrote:

Is your server assigned a static IP address or is that address dynamic?  If setup as dynamic I could see that as the problem.

Another might be network folder share permissions, you might wish to check your username of the backup folder under the Security tab in Properties of the backup folder to make sure you have full control for your username.

The router has it set as static/reserved. I looked at the server folder and the Win 7 account is listed as full control.

Well, I"m at a loss here.  Given all that you have posted it should just work.  You might try adding your server to your Win 7 host file.  I have resolved some connection issues that way.  If that works it would indicate some DNS issues with your network.

Thanks for all of the advice. I'm tired of battling a substandard backup program, and will go with the path of least resistance here via the WHS built-in backup since that is working properly.