× NETGEAR will be terminating ReadyCLOUD service by July 1st, 2023. For more details click here.
Orbi WiFi 7 RBE973
Reply

Re: ssh

thockin
Aspirant

ssh

ReadyNAS ultra4

I am tried of flaky behavior, and I want to look at real logs. I toggled SSH and installed EnableRootSSH. I can establish a connection by SSH, but it does not take the admin password. I am SURE I am not mis-typing it. 🙂

Any clues where to look next?
Message 1 of 7
mdgm-ntgr
NETGEAR Employee Retired

Re: ssh

You have to login as the 'root' user with the 'admin' password. The 'root' user's passwords initially set to be the same as the 'admin' password. Remember the add-on is EnableRootSSH
Message 2 of 7
thockin
Aspirant

Re: ssh

I am attempting to log in as root.

$ ssh root@10.5.69.250
root@10.5.69.250's password:
Permission denied, please try again.
Message 3 of 7
mdgm-ntgr
NETGEAR Employee Retired

Re: ssh

Try installing EnableRootSSH again
Message 4 of 7
thockin
Aspirant

Re: ssh

Did that. No love.
Message 5 of 7
pdelges
Guide

Re: ssh

Did you find a solution?

I have the same problem with a NVX (RAIDiator 4.2.25).
I'm sure I could ssh as root before. Now I get a permission denied error. I tried to install EnableRootSSH several times, and to reboot too. Strangely, I can't "'shutdown and reboot" nor "shutdown and turn off device" from Frontview anymore (I need to press the power button 3 times). It worked the first time I installed EnableRootSSH today, but not anymore.

ssh as admin with the admin password does work, but the connection is closed:


[PAt:~] pdelges% ssh admin@192.168.0.7
admin@192.168.0.7's password:
Last login: Wed Dec 4 11:10:39 2013 from 192.168.0.15 on pts/0
Linux BU-2TbRaid 2.6.37.6.RNx86_32.1.4 #1 Wed Oct 23 11:00:31 PDT 2013 i686 GNU/Linux
Last login: Wed Dec 4 11:20:05 2013 from 192.168.0.15
Connection to 192.168.0.7 closed.
[PAt:~] pdelges% ssh root@192.168.0.7
root@192.168.0.7's password:
Permission denied, please try again.
Message 6 of 7
mdgm-ntgr
NETGEAR Employee Retired

Re: ssh

As I suspected your root line in your /etc/shadow file was messed up.

Should be working now.
Message 7 of 7
Top Contributors
Discussion stats
  • 6 replies
  • 1530 views
  • 0 kudos
  • 3 in conversation
Announcements