Forum Discussion

Aspirant

Jul 30, 2017

Solved

ReadyNAS NV+ v2 - connection refused

I have a ReadyNAS NV+ v2 (firmware 5.3.12) that I used a while back to offload family photos and other data. It seems that I did some sort of firmware upgrade and then I could see the system via Rada...

Installation & Upgrade

mdgm-ntgr
Aug 10, 2017
The services configuration file was corrupt which would explain why services weren't starting.

StephenB

Guru - Experienced User

Aug 08, 2017

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

mdgm-ntgr

NETGEAR Employee Retired

Aug 10, 2017

The services configuration file was corrupt which would explain why services weren't starting.

JHock
Aspirant
Aug 10, 2017
Thanks mdgm - we should change your name to rock star!
JHock
Aspirant
Aug 10, 2017
Thanks Tony and Stephen for your assistance as well! - Justin
aks
Virtuoso
Aug 10, 2017
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?
JHock
Aspirant
Aug 10, 2017
Hi Tony - yes, I pm'd mdgm. He posted a couple of posts up, but the services configuration file was corrupt which would explain why services weren't starting. Through the tech support boot, he could log on and replace the config file with the default one. My drives are now visible (admin still isn't working l, but I'll backup the data and rebuild it)