NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
rolski
Oct 04, 2012Aspirant
ssh stopped working (connection abort) #19586817
I have perhaps a similar problem with my ReadyNas Ultra 4 plus. Since recent updates, root SSH access doesn't seem to work when using Putty.
(referring to :- viewtopic.php?f=20&t=65601&hilit=ssh+stopped)
I have an NV+ on my (same) home network, with root-SSH enabled, a fresh download / installation of Putty from putty.org and my NV+ is running "RAIDiator 4.1.10 [1.00a043]".
All works fine.
However, on my Ultra4+, running "RAIDiator 4.2.22", whenever I try to log-on I get "Network error : Software caused connection abort".
I've re-installed the "EnableRootSSH_1.0-x86.bin" add-in, and when that failed I downloaded a fresh copy & tried again, in case of any recent updates.
Admin log-in on frontview works fine.
I've checked my network for any i.p. address clashes & rebooted everything - nothing obvious.
Any ideas ?
(referring to :- viewtopic.php?f=20&t=65601&hilit=ssh+stopped)
I have an NV+ on my (same) home network, with root-SSH enabled, a fresh download / installation of Putty from putty.org and my NV+ is running "RAIDiator 4.1.10 [1.00a043]".
All works fine.
However, on my Ultra4+, running "RAIDiator 4.2.22", whenever I try to log-on I get "Network error : Software caused connection abort".
I've re-installed the "EnableRootSSH_1.0-x86.bin" add-in, and when that failed I downloaded a fresh copy & tried again, in case of any recent updates.
Admin log-in on frontview works fine.
I've checked my network for any i.p. address clashes & rebooted everything - nothing obvious.
Any ideas ?
16 Replies
Replies have been turned off for this discussion
- mdgm-ntgrNETGEAR Employee RetiredI doubt it'd be the firmware though I could be wrong. SSH still works fine for me on 4.2.22. You could try downgrading to e.g. 4.2.21: http://www.readynas.com/RAIDiator_x86_4_2_21_Notes
What version of RAIDiator did you update from? - rolskiAspirantI think I was until very recently on 4.2.19 : I've been away on business for the best part of a year, and although I've had notifications that there were updates available & downloaded, I didn't install them for fear of losing the connection to my NAS !
Returned on the 12th Sept when I performed the first update, then there was another, then another - leading to 4.2.22 - which I actually had to install twice as it didn't seem to install correctly. Perhaps that's a clue....
Am wondering whether to open a ticket as something's clearly wrong - and may be as a result of the recent updates. - mdgm-ntgrNETGEAR Employee RetiredYou could open a case and see what support has to say. Post your case number.
- rolskiAspirantThanks again. As usual, help / advice / assistance on this forum has been very very good & it's much appreciated - even when not successful !
Case 19586817 opened. - KydDynoMyteAspirantTry with firewall disabled?
Is the nas ip static and/or reserved if using DHCP?
Flush DNS and try?
Using ssh keys? - rolskiAspirantJust re-installed 4.2.21 : no difference.
Have also (coincidentally) performed a complete re-install of Windows XP on my desktop PC (which is my main access to my NAS's) - no difference at any stage.
NV+ still functioning perfectly - accessible from several different devices (including remote SSH), Ultra4plus working ok - apart from SSH access. So my conclusion is that "something's broken" which is directly related to SSH on my Ultra4plus.
Any other ideas ?
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!