Skip to main content

Unable to connect to server

Thread needs solution
Beginner
Posts: 2
Comments: 7

I have an odd problem that has only recently seem to materialise.

I'm running Acronis TI2016 on a number of PCs and I back them up to a shared folder on a Win10 PC I use as my server. The backups run fine and each PC can log onto the server to perform their backup.

The problem is if I use the restore program when I boot from a restore USB. I get an Unable to Connect Check credentials error every time. The credentials are OK - they work for the backup software - but no matter what I do the restore program will not connect.

I have searched for a solution and could find none so far. Is there some network setting in the server PC I need to change? I'm running Win10 Pro version 21H1 on the server.

Thanks.

0 Users found this helpful
Legend
Posts: 105
Comments: 25746

Glen, take a look at KB 58004: Acronis True Image 2016: Troubleshooting Issues Related to NAS Credentials - which should be of help here.

See also KB 57992: Acronis True Image: NAS Is Not Detected - and look at the section near the bottom of the document dealing with connections from rescue media.

See also: Acronis True Image 2016: Troubleshooting Issues with NAS Devices

Beginner
Posts: 2
Comments: 7

Thanks for your response, Steve. I have had a look at those articles and they don't seem to resolve my issue - unless I missed something...

I can connect to my server through TI2016 without issue, it is only when using the rescue media that things go wrong. The strange thing is I have been able to connect without issue in the past but I don't know what may have changed. I certainly haven't changed anything.

I even tried to restore via the Recover PC option in the Windows Interface. That allowed me to access the server (using the same credentials that I tried in the rescue media) and select the backup file I wanted. When the PC rebooted itself into rescue mode (not from the rescue USB drive) the connection that had worked in the graphical interface now failed.

So, I can connect from the windows application, but not from any recovery system.

 

Thanks again for any assistance.

Legend
Posts: 105
Comments: 25746

Glen, there is a world of difference between connections established within the Windows OS environment and connections being made in the rescue media environment.

Regardless of starting a recovery from within Windows by ATI - no connection information is carried over from Windows to the rescue environment - the latter is a Linux kernel environment to compound the issue.

What type of rescue media are you using when you boot the PC from this? 
Is this the Linux media or have you taken the extra steps to create the Windows PE version of the media?

Are you able to see and connect to the server system from the rescue media (apart from the credentials issue)?  Can you ping the server to demonstrate you have a valid connection?

See KB 56610: Acronis True Image 2016: Creating Bootable Media - for details of the options for creating WinPE media.

Note: the MVP Custom PE Builder script tool is a better tool to use to create WinPE rescue media as this can use the PE files found in your Windows Recovery Environment to save having to download and install the Windows ADK & PE Kits (circa 6GB size).

See forum topic Instructions to use WiFi with MVP PEBuilder Tool for details of adding in the required wireless drivers for PE media if you are not using a wired network connection.

Beginner
Posts: 2
Comments: 7

Hi Steve, I am running the Linux media for the rescue media and I can ping the server, both by name and IP address from the Linux system when booted from the rescue media. I am on a wired ethernet connection.

The server is visible, it just rejects the credentials.

Legend
Posts: 105
Comments: 25746

Glen, I tried a quick test using the Linux media via a VMware VM but could never get as far as the credentials prompt as it just hung!  Testing with the WinPE rescue media worked first time of asking though I had to use the \\192.168.0.71 IP address for the remote Win10 PC as the VM is using a different IP subnet otherwise.

Beginner
Posts: 2
Comments: 7

Steve, I created a winPE restore USB and it connects fine. Not sure why the Linux one stopped working, but I'm back up now. Thanks for your help.

Legend
Posts: 105
Comments: 25746

Glen, that is good news! Thanks for the feedback.