NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
davidr1
Jan 14, 2013Luminary
Installing ssh addon - caused big problems
Hi Ultra 2 - ssh added and working for years Pro 2 (new) - just added ssh Both have different admin passwords I have been using ssh on my Ultra 2 for a long time without problems. Yesterday I i...
mdgm-ntgr
Jan 14, 2013NETGEAR Employee Retired
davidr wrote:
May I ask, to learn, why you suggested key generation for the pro - isn't that automatic with installing EnableRootSSH?
You must have had another device at some point using the same I.P. as the Pro 2 which you connected to via SSH. As the key for the Pro 2 was different to that device your computer suspected that there might be someone doing some hacking and gave this message as a precaution. Since the Pro 2 is on your LAN and you put it there you could remove the key for the old device that used the Pro 2's I.P. from your list of known_hosts. Then there would no longer be any conflict.
davidr wrote:
And what you think corrupted the ssh access to the Ultra? Didn't the log entries point to a corrupt file? (Which I would have thought would be on the nas - not on the PC?
Not sure what caused the problem there.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!