Samba 4.1.17 for ReadyNAS Duo v1 (sparc)

If you have to "mess with" smb.conf and put things in it that the OS normally doesn't, then you could run into issues whever you do something that causes the NAS to re-write that.  So, just keep an eye out that your changes stay changed.

I tried this one on ReadyNAS NV+ and unfortunatelly without achieving desired result. Windows still says that the device uses insecure SMB protocol.
Is there any way how to troubleshoot?

Please disregard this message. It Works!!! Kudos to you!

Wow amazing Work! Thanks bc732 

Would you like to share the binary.deb or the configure scripts on github.com / ReadyNASDuoSparc  ? 

There are still readynas duo v1 users out there, amazing!

After some bit trial and error (had to learn editing files in Vi lol) I also made it work and finally could close SMB v1.0 support on my Win10 machine. Many thanks to the OP on this thread! After upgrading my x-raided Sparc to 1Gb RAM + 2Tb everything seems to be working smoothly (sorry, Netgear, things have been overly expensive these times!).

A remark I think it's worth is that I couldn't connect to my shares without enabling guest logins in Gpedit.msc (which is kinda unsafe but wouldnt't make such a difference in my home network). This is disabled by default on W10 (as in previous versions I was able to connect normally even with SMBv3). I tried to connect with the same user that I created through the frontview panel in the NAS but without success, so it tries to connect with my MS account and fallback to the guest one, so it connects as long as I disable this security check. If any experienced Windows user did make it work, I would appreciate how it was done!

I realize this is an old thread, but I recently fired up my old ReadyNAS NV and NV+ to locate some old data that I somehow never transferred to my newer NAS platform.  Of course I discovered that I could not access the shares anymore due to the SMB version deprecation with Windows 11 (and 10) unless one enabled the antiquated SBMv1 with some potential security risk.

This obviously led me here but my Linux skills were quite minimal, so I knew I was in for some challenging times ahead.  Here were my struggles so hopefully others can be assisted through the process (I used an Ubuntu 22.04 Linux container within Windows 11 to complete this task.):

Challenge 1: Realizing that Chrome and Edge blocked access TLS 1.0/1.1 so I needed to use Firefox and enable TLS 1.0 in the flags to gain access to the Frontview Admin interface.

Challenge 2: After installing the SSH and Apt add-ins and failing to access the ReadyNAS units due to algorithm errors.  The first error complained about lacking a certain diffe-hellman-sha1...etc. so I added this following statement to the ssh config via this command:

sudo nano /etc/ssh/ssh_config

At the bottom I added:

KexAlgorithms diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1

Then it complained about a sha1-rsa issue so I added another line below that in the ssh config:

HostKeyAlgorithms +ssh-rsa,ssh-dss

Challenge 3: Getting that darned .deb file onto the SSH root.  That took me awhile to figure out, but here was the syntax that worked for me:

scp /home/user/Downloads/samba_4.1.17-1_sparc.deb root@ip address:/root

After all that the rest was simple - just follow bc732's awesome steps and you're golden.  I did need to re-create my users as he mentioned but I was able to access the shares!  My NV machine has 256MB RAM while my NV+ machine has 1GB RAM and the transfer rate improvements were 2-5MB/s write and 5-10MB/s read with the extra RAM.  Not major but probably worth it, since overall the NV unit and Frontview interface are more responsive with the extra memory.  Thanks again for the info, bc732, and the helpful discussion with the other folk here.