Hi all. I have a ReadyNAS 312 that I bought un-used. It looks like it's on it's original OS, which is V6.1.8. Because of this I cannot access the admin page, as it displays "refused to connect". I've tried this on multiple browsers and multiple Windows OS's (including XP).
I can see the device in RAIDar and on the network but that's as far as it goes, I cannot copy files to it. I've seen a solution whereby you can upgrade the OS using SSH or Putty. However, this requires going into the admin page to enable SSH first......which I cannot do because I cannot access the admin page 😞😞 .
I've tried accessing via WinSCP and it refuses to connect....likely because SSH is not enabled.
I'm stuck!!! Is there anything more I can try? Can I remove the disks and copy files over to the HDD's manually? or access the admin page via another legacy browser?
I'm not sure why I didn't think of this before. A USB recovery to a higher version should work. Getting access to the GUI and doing a normal upgrade is still the better way, especially since I'm not convinced your problem isn't outside the NAS and an OS update won't fix it.
IE in WinXP should do it unless something else on your network is blocking it. Did you try direct connection to the NAS (which would require you set a compatible static IP address on the PC)?
Are you running RAIDar? Does it show the NAS and the correct IP address? Is that address in the subnet of your PC?
Did it come with drives, or are the ones in it yours? If it came with them, somebody may have changed the admin password from the default, so you should do an OS re-install.
Do you have another OS6 ReadyNAS, or access to one? Another way to update is to insert a volume that's on an updated version. The higher version "wins", and your chassis will be updated. Best way to do that would be to remove the drives from the other NAS (with power off) and then create a single-drive volume on one of the drives from the new one or any spare drive you have. Then power down and move the drive to the new one. When you power up, it'll go through an update, then re-boot into the updated OS. Then you can power down, put all the drives back in, and do a Factory Default.
NOTE to anyone else reading this: This is perfectly fine on the Intel-based 312. It would not be OK on an ARM based unit, as there is a mandatory upgrade path.
Hi all. I have a ReadyNAS 312 that I bought un-used. It looks like it's on it's original OS, which is V6.1.8. Because of this I cannot access the admin page, as it displays "refused to connect".
"refused to connect"? Are you also seeing an SSL-Version or Cipher Mismatch error?
Can you post a screenshot of what you see on RAIDar?
Hi. Yep RAIDar shows the correct product and IP. It's on the same subnet. I should have mentioned before that I tried a factory reset and OS install from the device and it made no difference. Password should have been reset to default.
Yeah, 2 X 2TB disks that came with it. I've taken them out and connected via a separate caddy to my PC to confirm they're ok and reading correctly etc.
I tried two 500GB disks I have spare. RAIDar recognises them as new, needing formatting etc but once it's done its thing the same OS is back and the issue remains
I tried two 500GB disks I have spare. RAIDar recognises them as new, needing formatting etc but once it's done its thing the same OS is back and the issue remains
😞
Just to clarify - the OS is installed on the disks, and you will not be able to connect to the web admin ui unless the system has been booted from the disks. That should happen at the end of the install step.
It could be a little quicker to use just one disk, as that eliminates the need for a RAID sync.
Yes, the OS has now installed on the new disks but the original error has returned. The enclosure has just installed V6.1.8 back on the new HDD's. (se pic)
Have you tried connecting a computer directly to the NAS? When you do so, there will be no DHCP server, so the NAS will adopt IP address 192.168.168.168. So you'll have to manually set the computer IP to something in the 192.168.168.* sub-net.
Have you tried connecting a computer directly to the NAS? When you do so, there will be no DHCP server, so the NAS will adopt IP address 192.168.168.168. So you'll have to manually set the computer IP to something in the 192.168.168.* sub-net.
@rhob - RAIDar is reporting 192.168.86.61, so this is NOT a DHCP failover.
I'm not sure why I didn't think of this before. A USB recovery to a higher version should work. Getting access to the GUI and doing a normal upgrade is still the better way, especially since I'm not convinced your problem isn't outside the NAS and an OS update won't fix it.
It took a couple of different USB sticks but I created the bootable USB and updated the OS to V6.8.10. The Admin page now launches, I can log in and manage it and all the network shares are now accessible on my home network. 🙂🙂
