ReadyNAS NV+ v2 - connection refused

3 disks, and I'm 97% sure it is Raid 5.  - J.

Did you try pinging the NAS IP address from the windows machine?  You need to run CMD to do that (enter "CMD" in the win10 search bar, and it will come as an installed program).

If you aren't familiar with CMD:  It will appear as a black window, and you enter commands from the keyboard in it.  The command you want is simply ping 192.168.0.29

If that works, (likely it will), then try entering

net use * /delete

net use t: \\192.168.0.29\data /user:admin nas-admin-password

Use the real NAS admin password of course, and be careful on the slash direction and the spaces.  You might get a confirmation prompt on the first command (and if you don't, you'll see a message saying there were no sessions to delete).

These two commands attempt to mount your NAS data volume as drive letter t.  If they are successful, the next step is to back up the data on the NAS.

Hi Stephen - thanks for the reply.  Indeed, ping returns successfully, but the net use request ends up with a system 53 error.

System error 53 has occurred.

The network path was not found.

Just to recap, if you browse the network in Windows explorer, do you see the nas in the list of devices?

Raidar can see the unit, and it reports status is ok?

Hi Tony - windows explorer cannot see the drives.  Raidar can see the unit, and yes, reports everything is ok.

---

JHock wrote:

Hi Stephen - thanks for the reply.  Indeed, ping returns successfully, but the net use request ends up with a system 53 error.

System error 53 has occurred.

The network path was not found.

---

You executed both commands, and specified the admin account?  Can you also try 

net view \\192.168.0.29

That should show you the share list.

Did this ever work with your windows 10 system?

Net view gives the same error 53.    In thinking about it, I believe I was still on Windows 7 when last I used the system.

Do you have another PC or mobile device you can try, just in case there is some strange firewall block?

What's the IP address of your PC?

I have another windows 10 pc which I can try later today, but if I remember right when I tried that in the past it didn't work either.  Just tried from my mobile phone, no dice.

PC's ip is 192.168.0.2

Thanks, Justin

Some Windows versions are beginning to deprecate SMB1.  Unfortunately that's required to access your older NAS.

I think the next step is to enable the SMB1 client on the PC and see if that helps.  To do that, you run CMD as administrator, and then enter

sc.exe config lanmanworkstation depend= bowser/mrxsmb10/mrxsmb20/nsi 
sc.exe config mrxsmb10 start= auto

Restart the computer, and try the net view test again.

Also, if the PC is using WiFi, make sure the connection classification is private.

Hi Stephen - so I enabled SMB1 as requested, restarted.

Same System error 53 as before.  

(I am able to fully access my system if I put the new 1-disk setup in... so would that indicate that the issue is on the NAS side, not the pc side?)

I am hard wired between the devices.

Thanks, Justin

You could power down, remove the disks (label by slot) and do a factory install on a scratch disk.  If there's no problem with the fresh install, then that does suggest that the problem is with the NAS disks.

You might also check that the windows workgroup (not the same as homegroup) are the same on the NAS and the PC.

Hi Stephen - yes, I already did the fresh install on a scratch disk which works fine...  however that doesn't explain what happened to the original disks or why a raid 5 redundant system has a lock-out failure like this... if that's what a NAS will do, there's zero value in me having one.

Where does one check the workgroup on the NAS device?   It did work at one point in time and my pc hasn't changed from workgroup...

---

JHock wrote:

however that doesn't explain what happened to the original disks or why a raid 5 redundant system has a lock-out failure like this... if that's what a NAS will do, there's zero value in me having one.

 

---

I agree it doesn't explain what happened.  On SMB it is a bit more complicated than usual right now, because Microsoft is changing SMB in the PCs.  

FWIW, I haven't seen this particular combination of symptoms before ("connection refused" for the web admin UI, plus the SMB challenges).  My own systems have never had the SMB problem.  But I don't own any v2 NAS.

---

JHock wrote:

 

Where does one check the workgroup on the NAS device?   It did work at one point in time and my pc hasn't changed from workgroup...

---

It depends on the NAS.  See pages 69-70 here: http://www.downloads.netgear.com/files/GDC/READYNAS%20ARM-PLATFORM%20(DUO%20V2,%20NV+%20V2)/RAIDiator%205.3%20SW%20Manual_5Sep12.pdf

Thanks mdgm - we should change your name to rock star!

Thanks Tony and Stephen for your assistance as well! - Justin

No problem, that's what a great community is for ;)!

I'm guessing that you had some PM messages going on in the background. Care to elaborate how you accessed the seamingly dead system?