ReadyNAS Duo (Sparc) needs SMBv2 or higher

Hi
I have the ReadyNAS Duo V1 (Sparc). Since the Microsoft 2017 Fall Creator's Update for Win10, SMBv1 is obsolete and I can't see it anymore on my main Windows PC (although I can on a second, older machine). It needs to support SMBv2 or v3. I read that this can easily be done by adding the line:

server min protocol = SMB3

to the end of /etc/frontview/samba/smb.conf.overrides

(according to https://community.netgear.com/t5/Using-your-ReadyNAS/SMB-1-0-Given-Wanna-Cry/td-p/1283738).

However, I have absolutely no idea how to do this. I installed a 'shell' from here (https://kb.netgear.com/24546/Add-ons-for-RAIDiator-4-1-3-Sparc) but there are no instructions on how to access it, or if I did, how to find, edit and save the above mentioned document. I know nothing about Linux I should add at this point, but I'm game for trying if I had the instructions.

The last point of note is that the last supported version of Radiator is 4.1.16, so I'm not sure if the version of "samba" that comes with it would support the suggested edit of "server min protocol = SMB3" or even SMB2.

Is there a patient knowledgeable person out there who can tell me if I can make my old NAS continue to talk to Windows 10, and how I achieve this seemingly essential small edit? Thank you so much!!!

----------------------------------------------------------------

ReadyNAS Duo V1 (Sparc). Radiator 4.1.16.

ReadyNAS Add-ons for Legacy ReadyNAS

18 Replies

Replies have been turned off for this discussion

StephenB
Guru - Experienced User
Jan 31, 2018
wrote:

Hi
I have the ReadyNAS Duo V1 (Sparc). Since the Microsoft 2017 Fall Creator's Update for Win10, SMBv1 is obsolete and I can't see it anymore on my main Windows PC (although I can on a second, older machine). It needs to support SMBv2 or v3. I read that this can easily be done by adding the line:

Let's start here. If you go into "turn windows features on and off" you should see an option for the SMB1 client. So you can still re-enable that option.

If you see an NFS client in your windows system, you could alternatively install that, and then turn on NFS file sharing on the NAS. That might be a better long-range solution.

Enabling an ancient experimental mode in your duo v1's SAMBA is probably not a good approach.
- mdgm-ntgr
  NETGEAR Employee Retired
  Jan 31, 2018
  The Duo has experimental SMB2 support which is disabled. It's beyond the security support period so I don't anticipate there being any further firmware updates for it at all.
  
  If SMB2/SMB3 support is important to you you may wish to consider getting a new ReadyNAS.
- Frankie3142
  Aspirant
  Jan 31, 2018
  Hi
  Unfortunately no option for turning on NFS is present. I should state that I'm using Windows Home edition (on the 2 PC's on my little 'network') so perhaps NFS is an option on the Pro or some other edition of Windows. Anyone aware of any 3rd party software I can get that might fix the issue and introduce NFS?
  
  Meanwhile I have an interesting update. My older PC (call it PC1) has the so called Fall update of Windows 10 too, and yet it can still see, read and write to the ReadyNAS Duo as perfectly as ever. PC2 meanwhile (the newer hardware), cannot do anything - the NAS has become totally invisible inaccessible from there. Some people have found that creating a network connection using the IP address of the NAS gets around the problem, but that's not working for me. Having one PC see the NAS isn't quite the fix it first appears to be. Imagine my backup routine for PC2 now: backup PC2 to PC1 (assuming thee's enough space on the older machine. Then move the backup off PC1's disk to the NAS. That's looking like a 24 hour operation now.
  
  Upgrading the NAS isn't quite an option either (I'm on a severely limited budget). I feel angry and let down by Netgear for not providing better support.
  
  I appreciate your remarks (and those of others) on how the old experimental Samba mode isn't to be celebrated, but I may be looking at any port in a storm at this point. I'd still like someone to tell me how to access the shell I installed. Besides, if I could figure out how to access the shell I could do the text edit to the config referenced elsewhere in these forums and linked to in my original post I think. It would be an experiment itself. If it didn't work I could always back out of it and stick with the bizarre 'daisy chain' method of accessing it via PC1 as I seem condemned to do now anyway.
  
  Thank you.
  - Sandshark
    Sensei - Experienced User
    Jan 31, 2018
    Assuming the "shell" you installed is "Enable Root SSH Access", you need to install Putty on your PC. Use the default settings in Putty for an SSH connection and type in the NAS IP address. When the CLI opens, log in as "root" using the admin password.
    
    But from there, you'll still need to know how to navigate the Linux file system and use VI to edit the file. Google can be your friend there. And, BTW, you will have to set the min protocol to SMBV2, as your NAS has no SMBV3 support. Given that SMBV2 is only experimental in your version of Samba, issues are possible.
    
    But is enabling SMBV1 not an option in your Windows version?
    
    Also, for NFS, open an elevated command line on the Windows machine and execute
    dism /online /get-features | more
    and see if these are listed:
    
    Feature Name : ServicesForNFS-ClientOnly
    State : Disabled
    Feature Name : ClientForNFS-Infrastructure
    State : Disabled
    Feature Name : NFS-Administration
    State : Disabled
    
    If they are, you can use
    dism /online /Enable-Feature:NFS-Administration
    and repeat for all the above features to turn on NFS even though it's not listed in the enable features GUI. I don't have a Home version install to check on.