Skip to main content

Backup to Synology NAS no longer possible

Thread solved

Hello,

Until now I managed to backup partitions of my local Win-Computer to my NAS without any problems.

In order to avoid the restriction of file sizes to 2 GB I entered my target via the search-option using the IP-address of my NAS. Thereafter, I had to select "network" and my NAS appeared. This doesn't happen any more.
I have to make use of  FTP. There my NAS shows up and I am asked to enter the NAS access data and port 22.
My registration is considered as invalid.

I hope my English was understandable.
Can anyone give my the reason for this? I shoult possibly add that this was my 1st backup with Win10 after having updated to 1903.

 

 

1 Users found this helpful

Horst, the most likely reason for this issue is that SMB 1.0 was being used and this has been disabled by Microsoft because is deemed too insecure (was at the heart of the Wannacry ransomware issues a while back!).

You should check both on your Windows computer and on the Synology NAS for what versions of SMB each support.  You should be using either SMB 2.0 or 3.0 for security.

See webpage: How to check SMB version on Windows 10/8/7

or webpage: How to detect, enable and disable SMBv1, SMBv2, and SMBv3 in Windows and Windows Server

plus webpage: SMBv1 is not installed by default in Windows 10 Fall Creators Update and Windows Server, version 1709 and later versions

See example of SMB settings from my own Synology NAS.

Hello Steve,

I hope I don't post twice since my original post has gone away.

Thanks for your very fast reply.

I forgot to mention that I had found out that SMB might be the problem.
Therefore, I reactivated SMBv1 as I didn't and still don't see the SMBv2-protocol in the Windows Apps settings.
The only thing which I could have done and which I did nows was to activate "SMB direct" which had been deactivated. I guess that that's not the solution.

In the link you sent me I didn't find a hint on how to activate SMB2.
Did I overlook something?

Could you give me another tip of how to?
Thanks in advance.

 

 

Horst, I have used a Powershell script to automate disabling SMB 1 and enabling SMB 2 as shown below:

SMB1_Disable.ps1

Clear-Host
if ((Get-SmbServerConfiguration).EnableSMB1Protocol) {
write-host "SMB1 enabled"
Set-SmbServerConfiguration -EnableSMB1Protocol $false -Force
Disable-WindowsOptionalFeature -Online -FeatureName SMB1Protocol -Remove
sc.exe config lanmanworkstation depend= bowser/mrxsmb20/nsi
sc.exe config mrxsmb10 start= disabled
sc.exe config mrxsmb20 start= auto
Write-Host "SMB1 now disabled & removed"}
Else {Write-Host "SMB1 is already disabled"}

if (!((Get-SmbServerConfiguration).EnableSMB2Protocol)) {
write-host "SMB2 not enabled"
Set-SmbServerConfiguration -EnableSMB2Protocol $true -Force
write-host "SMB2 now enabled"}

sc.exe config lanmanworkstation depend= bowser/mrxsmb20/nsi
sc.exe config mrxsmb10 start= disabled
sc.exe config mrxsmb20 start= auto
sc.exe config fdPHost start= auto
sc.exe config FDResPub start= auto

Use as follows from an Administrator Powershell or Command window:

powershell -ExecutionPolicy RemoteSigned -file SMB1_disable.ps1

Hi Steve,

Oh, your script looks overwhelming to me. I have some computer knowledge but I'm far far away from being an expert.
I will try to get along with it and will replay tomorrow.

I had overlooked your Synology settings and did so in mine.
After making my adjustments on Windows level and rebooting, my NAS is again part of my Windows Network.
However, even my desktop computer isn't part of network any more when preparing the output in Acronis TI's backup. There is nothing any more unter Network.

Horst, do you have Bonjour enabled (as gets installed with ATI) as this is used on both Windows & the Synology NAS for network discovery functions?

Hallo Steve,

Your recommendation shown in your screenshot dealing with "enable WS-Discovery" was great.

I had already enabled bonjour service but WS-Discovery had been disabled.
I had never touched this setting. I assume that my problem went along with the Win10 1903-Update.

After enabling WS-discovery, my backup to NAS works perfect.

I thank you so much for your never-ending assistance (and I feel much relaxed not to have to include your script :-)

 

Horst, glad to read that this issue is resolved now, thank you for your feedback.