NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RN102 v6.1.8 - cant access SSH
Hello folks, I have a RN 102, now upgraded to 6.1.8. I used to access it via SSH and rsync files from another RN102 to it. Suddenly I cannot access it via SSH anymore. Web interface is ok. I ...
Yep that's why I asked, normal SSH doesn't emit anything but their support special things can contact a server (as mentioned by mdgm), thus creating a connection that can be used to get in (once outbound nat is created, inbound is allowed since it's seen as a reply by your router).
If you got in via console as root, you should be able to get into your NAS via SSH quite soon. check SSH config, users shells, restart the service, check the firewall if needed. I think if all that is fine, you should get SSH back.
If not, I tend to check my backups and factory reset, those NAS are too scripted to my taste and sometimes it's cleaner to reset than to follow the trail to some hidden config file modified by a script that is itself hidden deep into the system. Not an heroic way to go, but works 100% of the time. Of course, I tend to avoid having a problem in the first place so...
PS : for your user, did you use it in the NAS interface for anything ? If so, the NAS may have rewritten it to use it as an FTP/CIFS/AFP user while you updated your settings. If you changed your user password in the interface, same thing. As far as I know, all users created via the web interface have a shell set to /bin/false to prevent them from using SSH or do nasty things and the scripts used by Netgear mays rewrite entirely each thing instead of modifying the existing. That would explain your problem. I know for example that my modified config of apache is erased at each update. Maybe users are checked in the same way and standardized if they are not compliant with what the script expects.
If you got in via console as root, you should be able to get into your NAS via SSH quite soon. check SSH config, users shells, restart the service, check the firewall if needed. I think if all that is fine, you should get SSH back.
If not, I tend to check my backups and factory reset, those NAS are too scripted to my taste and sometimes it's cleaner to reset than to follow the trail to some hidden config file modified by a script that is itself hidden deep into the system. Not an heroic way to go, but works 100% of the time. Of course, I tend to avoid having a problem in the first place so...
PS : for your user, did you use it in the NAS interface for anything ? If so, the NAS may have rewritten it to use it as an FTP/CIFS/AFP user while you updated your settings. If you changed your user password in the interface, same thing. As far as I know, all users created via the web interface have a shell set to /bin/false to prevent them from using SSH or do nasty things and the scripts used by Netgear mays rewrite entirely each thing instead of modifying the existing. That would explain your problem. I know for example that my modified config of apache is erased at each update. Maybe users are checked in the same way and standardized if they are not compliant with what the script expects.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
