Jump to content

Recommended Posts

Posted

I unearthed an old QNAP TS-420U and, since we have no on-site backup device (we are doing offsite, but nothing local) I've been trying to rig this up as a backup device.

 

Now, I want the QNAP to pull backups, rather than having the file server push them. That way, should any nasties get onto the network, there's a lesser (though still non-zero) chance of the backups getting, for example, encrypted by ransomware (as long as we notice and turn it off), but I just can't get the QNAP to access the shares.

 

However, try as I might I just can't get it to operate over anything other than SMB1

 

The file server has the SMB1.0/CIFS File Sharing Support feature added, though SMB1 is disabled via the registry keys.

Running Get-SmbServerConfiguration on the file-server returns (amongst other things)

EnableSMB1Protocol              : False
EnableSMB2Protocol              : True

 

If I SSH onto the QNAP and run the smb2status command, it returns:

[~] # smb2status

smbd (samba daemon) Version 4.4.16
smbd (samba daemon) is running.
max protocol SMB 3 enabled.

 

The account credentials I feed the QNAP box are domain admin credentials (as it's the same account that does full-vm Veeam backups) and yet it just will. not. work.

If I change the IP address to point at the old file server, success. Only difference? Windows Server version, and running Get-SmbServerConfiguration on the old one returns EnableSMB1Protocol : True

 

I was under the impression that server initiating the connection would always to try and negotiate the highest SMB flavour first, then drop down if the other end couldn't support it? So it should be using SMB3.

But every test I run results in failure..

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...