NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
avicenne13
Feb 12, 2014Aspirant
SSH problem on Ultra 2
Hi Using the latest firmware on ReadyNAS Ultra 2. Enabled root SSH after OS reinstall. I get the following error: ssh root@192.168.1.88 Connection closed by 192.168.1.88 Checked logs (boot...
avicenne13
Feb 18, 2014Aspirant
Problem solved. Let me write the steps that I did for future reference:
- the problem -- ssh lockdown due to too open RSA key, permissions messed up by the user
- the solution: *****do it at your own risk*****
1. put the ReadyNAS into tech support mode
2. telnet over port 23
3. log in with root username and password (google this password, it is easy to find)
4. mount the regular boot partition of the device as follows
echo DEVICE partitions > /etc/mdadm.conf
mdadm --examine --scan >> /etc/mdadm.conf
mdadm --assemble --scan
mount /dev/md0 /mnt
5. go to /etc/ssh/
6. rename the key files ssh_host_dsa_key and ssh_host_dsa_key.pub to another name for backup purposes using mv command
7. reboot the device
8. if you are using terminal, you should sudo the ssh or delete the keys on your computer prior to connection attempt
you should be good to go..
thanks to mdgm for the inspiration, some steps are copied from: http://onlyblueatwork.wordpress.com/201 ... -recovery/
- the problem -- ssh lockdown due to too open RSA key, permissions messed up by the user
- the solution: *****do it at your own risk*****
1. put the ReadyNAS into tech support mode
2. telnet over port 23
3. log in with root username and password (google this password, it is easy to find)
4. mount the regular boot partition of the device as follows
echo DEVICE partitions > /etc/mdadm.conf
mdadm --examine --scan >> /etc/mdadm.conf
mdadm --assemble --scan
mount /dev/md0 /mnt
5. go to /etc/ssh/
6. rename the key files ssh_host_dsa_key and ssh_host_dsa_key.pub to another name for backup purposes using mv command
7. reboot the device
8. if you are using terminal, you should sudo the ssh or delete the keys on your computer prior to connection attempt
you should be good to go..
thanks to mdgm for the inspiration, some steps are copied from: http://onlyblueatwork.wordpress.com/201 ... -recovery/
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!