Forum Discussion

Tutor

May 23, 2017

Solved

No access to shares after disabling SMB1 as recommended by Microsoft

Hi everyone, in view of the latest WannaCry/Crypt attack on 12 May 2017, Microsoft recommended to patch my Windows 10 OS and disable SMB 1.0/CIFS File Sharing Support. Check this link: ht...

File Sharing

kohdee
Aug 23, 2017
On RAIDiator 4.1 and RAIDiator 5.3, they use versions of Samba that do not support SMB2. You will need to use the Windows tricks to re-enable SMB1 support.

On RAIDiator 4.2, it can support SMB2 but you may experience a performance hit that you could find unacceptable.

We can see about creating an unofficial add-on for RAIDiator 4.2 boxes that you can use at your own risk to be use SMB2. These devices were not meant to run SMB2 though. All of the RAIDiator boxes are older than 5 years. It might be time for an upgrade.
If you are really concerned, you can unofficially upgrade most RAIDiator 4.2 boxes to OS 6 at the risk of factory defaulting your NAS and putting your data back onto the volumes. Alternatively, you can upgrade to a newer ReadyNAS and use the old ReadyNAS as a backup (always smart to have multiple backups, which eliminates single point of failure).

Hubris1

Aspirant

Jun 23, 2017

That will translate as upgrade or tough then

StephenB
Guru - Experienced User
Jun 24, 2017
Hubris1 wrote:
That will translate as upgrade or tough then

Again, I have no inside scoop.

The 4.1.x and 5.x systems have SAMBA 3.5, which has experimental SMB2, the OS 4.2 systems have Samba 3.6, which has a more complete SMB2. Simply allowing those to be used is easy enough, but there could be other CVEs and bugs that would need to be backported.

Also, the info on Windows I have is

All Home and Professional editions now have the SMB1 server component uninstalled by default. The SMB1 client remains installed. This means you can connect to devices from Windows 10 using SMB1, but nothing can connect to Windows 10 using SMB1.

Windows 10, we may uninstall SMB1 client if we detect that you are not using it.

All Enterprise and Education editions have SMB1 totally uninstalled by default.

The removal of SMB1 means the removal of the legacy Computer Browser service. The Computer Browser depends exclusively on SMB1 and cannot function without it.

If you are upgrading or need to install the protocol after a clean install, you will still be able to do so

Assuming this is all correct, it's not as stark as "you can't access the old NAS after the next Win10 release" SMB1 still be available, though of course it is a vulnerability.

FWIW, Microsoft is building their own list of products requiring SMB1 - it is here: https://blogs.technet.microsoft.com/filecab/2017/06/01/smb1-product-clearinghouse/ I'm sure there are a lot more.

In my own case, the 4.1 and 4.2 systems I have are purely backup NAS, and losing SMB access is not a big problem - arguably I should turn SMB off altogether on them anyway, and just leave rsync enabled.. I could easily upgrade the 4.2 system to OS 6.