This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
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 Radar, but couldn't connect to the admin page or explore the drives (Connection Refused error). (Maybe I uninstalled an app as I've seen tickets here refer to...) Radar reports that it's a healthy system, and the front lcd reports the right storage levels.
In reading through the forums - I saw different options presented. So I tried the boot menu and reinstalling the OS. No dice. Then I saw where I could put a new disk in and try doing the boot menu - factory default. I did this and the NAS comes up perfectly - I can connect, and browse the shares with that new disk. Upon shutting down and reinstalling the original disks however the old issue comes back. Any ideas? Thanks, Justin
Hi Tony, thanks for the response. Admin account has been reset which is fine (on the new single disk). I don't even get to a logon screen as the logon page request has the connection request refused before even loading.
Windows 10 (But it was doing this on Windows 7 before my upgrade as well.) - Justin
Just to clarify- the OS is on the hard disks. So whatever you did with the new single disk doesn't apply when you switch back to the old ones.
If you did the OS reinstall on the old disks, the admin password should have been reset to password there too.
If you didn't do the OS reinstall - is the IP address reported on the LCD screen compatible with your current network? (this is with your original disks running).
In addition to the IP address shown on the display, what browser are you using. "Connection refused" is a bit odd, so I'm wondering exactly what is provinking such a response - I've only seen browser security alerts due to certificate error in the past (not that this is helpfulu!).
Hi Tony - I did do the OS reinstall with the original disks. It won't allow me to get to the admin page to even enter a username and password. The ip address is a valid address for my network. I typically use Chrome, but IE gives a similar error.
Raidar still reports the correct IP address and the unit is healthy (just rechecking since your first post!)?
Do you have command line access via ssh (you would need to have enabled it through the admin interface by loading an add-on)?
I do have an NV+ v2 so hopefully we can make some progress. The basic problem right now is that the web service appears to not be coming up for some reason. A possible reason could be OS partition may be full, and I'm not sure how to get past that but I know a man on here who does (mdgm is one of them ).
Thanks for the replies - to Tony - that is indeed the url that is giving the connection refused error.
To Stephen, windows explorer cannot access the drives either (windows error: cannot access). I do not wish to lose the data on the device and have seen some posts where someone from netgear has been able to remote in and resolve the broken piece.
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.
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.
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...
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.
).
