Netgear ReadyNAS Duo v2 admin interface issues

[pebble guy]

I recently bought a used ReadyNAS duo v2.
After powering the box up, i could not access the admin interface.
I got "connection refused" error. The issue persists across browsers.

I installed the RAIDar utility, and it can detect the box, but pressing the Admin page button returns the samme issue.

I tried resetting the box to factory settings via the procedure described in the hardware manual(reset button, boot menu etc.)
This did not fix the problem either.

After connecting a UART to the internal debug port, everything seems normal. No errors on startup etc.
I have tried flashing new firmware via the RAIDiator Flash recovery, but it causes a magic number mismatch over the UART.
The tool was found on a page mainly reffering to other x86 based readyNAS based models, however the tool works with the ARM firmeare just fine.
Found mentions of a different tool for the ARM boxes, but i am yet to find it anywhere.

Has anyone managed to solve this issue, and how?
 

[Master Disaster]

Start with the basics....

 

Does the NAS have an IP with your DHCP server? Can you ping it? Are you 100% sure its not an issue with your browser?

[pebble guy]

16 minutes ago, Master Disaster said:

Start with the basics....

 

Does the NAS have an IP with your DHCP server? Can you ping it? Are you 100% sure its not an issue with your browser?

Should have mentioned that.
The NAS gets a ip adressed correctly, as shown in the router interface and the NETGEAR RAIDiator detects the nas.
As i get the same error on my phone, i assume it is not an browser issue.
The only option i see thats browser related, would be to fire up my older windows machine and try internet explorer

[Master Disaster]

Just now, pebble guy said:

Should have mentioned that.
The NAS gets a ip adressed correctly, as shown in the router interface and the NETGEAR RAIDiator detects the nas.
As i get the same error on my phone, i assume it is not an browser issue.
The only option i see thats browser related, would be to fire up my older windows machine and try internet explorer

If you're on 10 then use Edge, the only thing its good for is to keep as a sterilised environment for testing

[pebble guy]

1 minute ago, Master Disaster said:

If you're on 10 then use Edge, the only thing its good for is to keep as a sterilised environment for testing

Tried that already.
Just dug out my old laptop, and an older chrome version and IE8 shows same results.
For the record i have disabled all antivirus and firewall with no effect

[pebble guy]

5 minutes ago, Master Disaster said:

If you're on 10 then use Edge, the only thing its good for is to keep as a sterilised environment for testing

Tried that already

[Master Disaster]

2 minutes ago, pebble guy said:

Tried that already

Maybe this might help, obviously replace the IP, user & pass with your own.

https://community.netgear.com/t5/Using-your-ReadyNAS-in-Business/ReadyNas-refusing-to-connect/td-p/1563058

[pebble guy]

5 minutes ago, Master Disaster said:

Maybe this might help, obviously replace the IP, user & pass with your own.

https://community.netgear.com/t5/Using-your-ReadyNAS-in-Business/ReadyNas-refusing-to-connect/td-p/1563058

As the box has never been setup on my network, i dont think this guide applies.
I tried it anyway, but no dice

[DogKnight]

Some random shots in the dark here. 

 

Some NAS devices use https for their web interface. And the certs they use can expire if not updated regularly. 

This can cause some browsers to refuse to connect to them. May be a possible cause. 

If possible you may be able to connect over http (my ReadyNAS 314 can), which may help avoid this issue. 

 

Otherwise if you have any access via the UART port, make sure date and time settings are correct on the device. 

A factory reset would be advised if at all possible so you can at least make sure you're starting without any pre-configured issues.

 

[pebble guy]

Just a little update.

It turned out to be an insufficient PSU. The NAS installs the OS on the disks, and the PSU did not supply enough viltage to power up the disks, explaining the missing Admin interface