Aller au contenu principal

Can't connect to server after upgrade

Thread needs solution

Hi all

I've been using ATI 2018 for years. I thought I'd upgrade to 2021 while it was still available but now I'm unable to connect to my server. I've double checked the username and password, but every time I get 'connection failed'. Everything else is able to connect to it fine. I remember having similar difficulties way back when I first started using ATI. The only other clue I can offer is that the server doesn't appear in Windows Explorer when you click on Network, but this hasn't been an issue up until now.

PC is running Windows 10 Pro. Server is Windows Server 2016 Essentials.

Thanks

John

0 Users found this helpful

John, a couple of initial suggestions here:

First, try setting up a simple Files & Folders backup task to your Server destination with just a single folder for the source.  This will prove that you are able to establish a valid connection.

Next, try reselecting the Destination for any tasks that were migrated from ATI 2018.

Hi Steve

Unfortunately, trying a simple files & folder backup simply proves that I can't connect to the server. A couple of other things I've tried are temporarily disabling antivirus and running ATI as administrator. I also have a server running TrueNAS on the network which I can backup files to. Unfortunately it doesn't have sufficient disk space to act as my main backup.

By the way, I've already removed the ATI 2018 backup, just in case that was causing an issue. I'm rather regretting that now as it didn't help at all!

John

John, have you tried using the IP address for your Windows Server, i.e. \\192.168.0.29\Backup ? You can enter this in the Browse panel for the destination.

Yes, tried that too.

John, how far do you get with setting up a new task?

Do you get to the point of providing credentials for access?

Yes. I found out why the server wasn't appearing under Windows Explorer and I've fixed that. So now when I choose destination and click browse and click 'network' the server is showing. So I click on it and it immediately asks for authentication settings, but nothing I enter is satisfying it.

John, you may need to qualify your user credential with the server domain.

See the following from KB 58004: Acronis True Image 2016: Troubleshooting Issues Related to NAS Credentials

Different forms of entering NAS user name

If your NAS credentials are not accepted when authenticating, you can try using different forms of entering user name:

  1. Just user name, e.g. administrator
  2. NAS machine name and user name: MyNAS\administrator
  3. NAS ip-address and user name: 192.168.1.20\administrator
  4. Domain name and user name: MyDomain\administrator
  5. User name and domain name: administrator@MyDomain

Nope, tried that too. I've also completely uninstalled and reinstalled, with no luck. Very fed up!

John, sorry but am running short on new ideas for this scenario and don't have any Windows server systems to test with...

My next suggestion is to try a different application such as Macrium Reflect 8 Free to see if the issue is only with Acronis or would apply to any other backup application.

Hi Steve

Thanks for your help. I thought I'd install a trial of the new Cyber Protect Home Office, and that does exactly the same. Went back to ATI 2018 and it connects immediately with no issue. So I've sent feedback with a system report and we'll see if anyone at Acronis has a solution. My guess would be something to do with SMB security, except that it connects fine to the TrueNAS server, and I don't believe that has SMB 1 turned on. In fact, I'm reasonably sure that the Windows server has it turned off too, so perhaps I'm barking up the wrong tree.

John

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Contributions: 250
Commentaires: 7092

To post an update to the issue:

As per the information in the related support ticket, the issue has been solved in Acronis Cyber Protect Home Office. It was required to specify the IP-address of the server and the access credentials, after that the target location was available.