ReadyNas - RAIDiator 4.1.16 - Win10 issues

[MrMarc]

Hi,

I´ve got a ReadyNas Duo running with the latest firmware RAIDiator 4.16.16. Haven´t have any problem, until  yesterday. I´m unable to access the NAS  on WiFi through Win10 browsing \\NAS och \\192.168... or mapping. "Unable to acces..try do identify". Works fine when i use Boxee or my Android phone

I´ve searched the web and it seems to be a workaround. It seems to have something to do with SMB-versions. "Install SMB Plus on the NAS and then change SMB to SMB1". But how will i´m be able to do that on RAIDiator, when its not possible to install apps? How do i fix this? Must be something Netgear can do to help.

[mdgm-ntgr]

The NV+ (v1) only supports SMB1. It's the default and only version of SMB supported.

[MrMarc]

Thanks

So what should i do then if this doenst work? I can ping the nas without any problems. Probably this started with som windows patch last week

[StephenB]

What happens if you open CMD on the windows system and enter

net use * /delete

net use t: \\nas-ip-address\c /user:admin nas-admin-password

Be careful on the slash direction and spaces (and use the real ip address and admin password of course).

This normally will mount the C data volume as driver letter T.

[mdgm-ntgr]

Have you tried rebooting your NAS and PC?

Can you access the web admin interface?

[MrMarc]

"

---

@StephenB wrote:

What happens if you open CMD on the windows system and enter

net use * /delete

net use t: \\nas-ip-address\c /user:admin nas-admin-password

Be careful on the slash direction and spaces (and use the real ip address and admin password of course).

This normally will mount the C data volume as driver letter T.

---

The Network name cannot be found"

[MrMarc]

---

@mdgm wrote:

Have you tried rebooting your NAS and PC?

Can you access the web admin interface?

---

I´ve tried rebooting both, twice. 

Yes, can access the interface without any problems

[StephenB]

Can you ping the NAS ip address from the PC?

[MrMarc]

---

@StephenB wrote:

Can you ping the NAS ip address from the PC?

---

Yes

[StephenB]

Did you have access after you upgraded to 4.1.16?

Also, were you seeing any unexpected disconnects or other warning signs before you lost access altogether?

[MrMarc]

---

@StephenB wrote:

Did you have access after you upgraded to 4.1.16?

Also, were you seeing any unexpected disconnects or other warning signs before you lost access altogether?

---

Truth is, i updated the firwmare after this error occured because i thought i was whats why it has stopped working, so I haved this problem before

Went trough the Log without any odd warnings

When i browsing other forums, posts from 2015-16 says that this error could occur in win 10 because SMB1 disables in some updates. I´ve tried to run this https://www.technibble.com/forums/threads/microsoft-networking-smb-configuration-in-windows-10.68432... to fix it, but no luck.

[MrMarc]

Figured it out. I enabled SMB1 through Add programs -> Turn on features -> Enable SMB/CIFS 1.0 which had been disabled during some patch update the last week, i guess

Thanks for your responses!

[Iede]

Where did you find these commands? I seem to have the same problem but I couldn't find them in the RIADiator 4.1.16 screens.

[Sandshark]

Turning on SMB1 is done in Windows, not on your NAS.  The latest Windows10 version does disable SMB1 by default, so you have to turn it on if you need access to a legacy NAS.