NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

JeffNAS's avatar
JeffNAS
Initiate
Oct 10, 2022

ReadyNAS Duo V1 SMB2 Configuration Journey

Hey everyone,

I have a ReadyNAS Duo V1 that I pulled out of service a year or two ago and wanted to repurpose it for use as storage on my home network.

I have the usual SMB1.0 issues where I cannot map a network drive due to the vulnerability issue and Microsoft disabling it in the Windows version I am using (Windows 10).

I have poured over a ton of information on these forums and have came to the following conclusion -- there are two options:

1. Use the experimental configuration in smb.conf, adding:

min protocol = SMB1 (which is really invalid, so you can use SMB2 if you're not going to go back to SMB1)

max protocol = SMB2

2. Abandon SMB altogether and implement NFS

 

I started down the 1st road and did the following:

1. Updated my firmware to RAIDiator 4.1.16

2. Added EnableRootSSH so I could SSH into the box,

3. Use PuTTY to then use vi to edit /etc/samba/smb.conf and add the max and min values

4. Rebooted the box

5. Tried to add the network share -- I was able to get further than prior to those changes: I was actually asked for a UID and PW but it was not accepted.  Tried to create a new share and the same results

 

My question is, on this firmware -- is this an actual option in this firmware?  Can I install 4.2.31 x86 even though my box is Sparc?  I read in a thread that SMB2 is available, albeit experimental, in 4.2 firmware and not available in 4.1 firmware.  Is that accurate?

Thanks in advance!

 - Jeff 

3 Replies

Replies have been turned off for this discussion
  • StephenB's avatar
    StephenB
    Guru - Experienced User

    You have NAS that is at least 11 years old, so it might be time to invest in a replacement. 

     

    FWIW, my own Duo still works - I use it as a secondary backup for some shares (SMB is not enabled on it, only rsync). I'm not depending on it - just using it because it still works.

     


    JeffNAS wrote:

    Can I install 4.2.31 x86 even though my box is Sparc? 


    No.  x86 firmware won't run at all on a sparc.

     


    JeffNAS wrote:

     

    I have the usual SMB1.0 issues where I cannot map a network drive due to the vulnerability issue and Microsoft disabling it in the Windows version I am using (Windows 10).

     


    You can of course also go into "turn windows features on or off" and enable the SMB 1.0 client.  Opinions vary, but I don't see a big risk doing that on a home network.  A large enterprise network would be a different story.

     

     

    • JeffNAS's avatar
      JeffNAS
      Initiate

      Thanks very much for the reply.


      StephenB wrote:

      You have NAS that is at least 11 years old, so it might be time to invest in a replacement. 

      Yeah, I know it's very old but it seems like a waste to just chuck it as it works.  I am not scared to go the NFS route as I know I can get that working.  It will be accessible to my Apple and Linux products, so I may just go that route instead of fumbling with SMB and wasting time because it's looking more and more like it's more than just a permissions issue or UID and PW issue.  It's just odd that it's closer to accessing the shares (actually asking for a UID and PW) than it was prior... I feel like it's close to working and just need a tweak here or there.  That's kind of why I was posting to see if anyone has gotten farther with that old V1 Duo and SMB2.

       


      StephenB wrote:

      No.  x86 firmware won't run at all on a sparc.


      Yeah, I pretty much knew the answer to my question, but I thought I'd ask anyway đŸ˜

       


      StephenB wrote:

      You can of course also go into "turn windows features on or off" and enable the SMB 1.0 client.  Opinions vary, but I don't see a big risk doing that on a home network.  A large enterprise network would be a different story.


      I have read that (I believe it was one of your posts) in another thread...I've been weighing that one out... I'll have to do a little more research -- I saw that some were saying the initial vulnerability was with the firmware and the SMB 1.0, but I still need to read up more on it.

       

      I appreciate the reply!  Thanks very much for the info.  I'd love to hear if anyone else has gotten farther with the firmware and SMB2.

      Thanks again!

       

NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology! 

Join Us!

ProSupport for Business

Comprehensive support plans for maximum network uptime and business peace of mind.

 

Learn More