How to connect to RND2150 from Windows 11

To be workable with these legacy systems, SMB 1.0/CIFS has to be enabled.

Of course, the NAS must be configured for the same IP subnet like your router and the PC. Enable the NAS DHCP in case, or configure an appropriate free IP address, correct subnet default gateway (the router LAN IP), and point the NAS for this DNS server address, too.

---

NZ wrote:

If the IP address is a different subnet how can it connect?
My router uses 192.168.1.x the Netgear is on 192.168.0.x so I don't think it can work?

---

The simplest thing to do is change the router to 192.168.0.x (at least temporarily).

 

In addition to enabling SMB 1.0, you will also need to enable TLS 1.0 in your browser in order to access frontview.  Browsers are now disabling TLS 1.0 by default.

 

Options are

• use Edge in IE mode (google that if you don't know how to do that)
• install Firefox and set it's min TLS security to allow TLS 1.0. Enter about:config in the browser window.  Then search for security.tls.version.min, and temporarily set it to 1.

After you gain access to Frontview, you can reset the NAS network configuration to use DHCP.  Most routers will then let you reserve an IP address for the NAS.  That is better than using a static address like you are now.

 

I also suggest updating your firmware to the final 4.1.16 (which has one security fix you are missing).  If you need to manually install it, you can find it here: https://kb.netgear.com/000038792/RAIDiator-Version-4-1-16-Sparc  Remember to extract the binary from the zip file before installing it.

 

Finally, if you are comfortable with ssh you can change a configuration file to let you access frontview using normal http (not https).  Then you won't need to click through security warnings, and use TLS 1.0 to reach it.  Instructions are in the first posts here: 

• https://community.netgear.com/t5/New-ReadyNAS-Users-General/Workaround-for-ERR-SSL-VERSION-OR-CIPHER-MISMATCH-problem-for/td-p/2198243