How do I enable (experimental) SMB2 support on my ReadyNAS DUO?

[saxguy1]

ok understood, thanks. Before I try your checks, can you release either of the two emails before the short one I posted ? I have good info in there I'd like some eyes on.

[saxguy1]

here are those results:

myNAS:/etc/samba# ls -ls
total 80
48 -rw------- 1 root root 49152 Jun 4 2018 secrets.tdb
16 -rw------- 1 admin admin 1224 Oct 8 11:46 smb.conf
16 -rw------- 1 root root 311 Oct 7 16:55 smbpasswd

myNAS:/etc/samba# cat /etc/samba/smb.conf | grep -i protocol
max protocol = SMB2
min protocol = SMB1

only thing is I have the min/max reversed (had asked about that in my (2) quarantined posts)

[StephenB]

I've released the other two posts from quarantine also.

I don't know if the order matters on the two commands, but you could try reversing it.

Though I think you'll need to restore the original file first, and reboot the NAS to regain windows access.

[saxguy1]

I try and edit the smb.conf file, reload it it vi and I see it's reversed but when I reboot, it's backwards again.

I'm saving my edits to the orginal smb.conf with

:w! smb.conf<Return>

...while in myNAS:/etc/samba#

what am I doing wrong for saving a file in BASH?

[saxguy1]

also, see that smb.conf doesn't like the min protocol line

myNAS:~# smbstatus
WARNING: Ignoring invalid value 'SMB1' for parameter 'min protocol'
WARNING: Ignoring invalid value 'SMB1' for parameter 'min protocol'

Samba version 3.5.22
PID     Username      Group         Machine
-------------------------------------------------------------------

Service      pid     machine       Connected at
-------------------------------------------------------
IPC$         3635    Win10         Fri Oct  9 23:45:33 2020

[saxguy1]

I am able to connect using my Mac (Mojave) client over NFS, AFP and SMB

10.0.0.XXX:/c/D_drive on /private/nfs (nfs)

[StephenB]

---

@saxguy1 wrote:

also, see that smb.conf doesn't like the min protocol line

myNAS:~# smbstatus
WARNING: Ignoring invalid value 'SMB1' for parameter 'min protocol'
WARNING: Ignoring invalid value 'SMB1' for parameter 'min protocol'

Samba version 3.5.22
PID     Username      Group         Machine
-------------------------------------------------------------------

Service      pid     machine       Connected at
-------------------------------------------------------
IPC$         3635    Win10         Fri Oct  9 23:45:33 2020

---

SMB1 isn't a legal value (see https://www.samba.org/samba/docs/current/man-html/smb.conf.5.html#SERVERMAXPROTOCOL )  You could use NT1, but if you want to allow SMB1 for now, it's simpler just to leave the min protocol line out.

[saxguy1]

ok thanks for all the help Stephen, appreciate it.

I did a factory reset and everything is fine now over Windows 10. I have the loud fan noise but will find and install EnableFanMinRPMOverride_0.1 (which worked for me back in the day).

If I decide to buy a new ReadyNAS, will my current hard drives work in it?

[StephenB]

---

@saxguy1 wrote:

If I decide to buy a new ReadyNAS, will my current hard drives work in it?

---

You won't be able to migrate your drives, as the newer NAS use a different file system.

[saxguy1]

Sorry, that's not what I meant. I would wipe these drives first. My question is do the newer Netgear NAS' support these HHDs' SATA  interface? Can they pop in the new enclosures for a (new) backup ? Or all NAS from Netgear SSD, i.e.?

[StephenB]

---

@saxguy1 wrote:

Sorry, that's not what I meant. I would wipe these drives first. My question is do the newer Netgear NAS' support these HHDs' SATA  interface? 

---

The drives themselves are compatible with current ReadyNAS.