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.
Doesn't matter at this stage : you're one step too far ahead - the Putty window opens, the error message is displayed, then the Putty window closes. So I can't log-in as either root or admin.
nmap -sV -p 22 192.168.0.1 <---replace with your nas ip.
you should get
PORT STATE SERVICE VERSION 22/tcp open ssh OpenSSH 4.3p2 Debian 9 (protocol 2.0)
if everything working ok
if you get something about tcpwapper. then do a firmware update from front-view and as the NAS reboots keep scaning as above (rescan over and over) till you see
PORT STATE SERVICE VERSION 22/tcp open ssh OpenSSH 4.3p2 Debian 9 (protocol 2.0)
then quickly log in with putty before the NAS fully reboots if you miss it just try doing the frimware update again from frontview till you get it
once you have ssh access see if sshd is missing from /var/run/ if so then
mkdir /var/run/sshd chmod 0755 /var/run/sshd
do a nmap scan before disconnecting to see if the port in open
else you'll need to look at the ssh logs and start googleing.
A great help - very detailed & I was able to follow - but no joy.... I have exactly the result you list above : 22/tcp open ssh OpenSSH 4.3p2 Debian 9 (protocol 2.0) : but I still cannot get in with Putty. Is there any reason that I can get in to my NV+ with Putty & not my Ultra4plus ? And during updates / reboots, Putty either times-out or the "software" error message appears. Is there any other way to get in other than Putty perhaps ? Or any settings on Putty that can be changed to help ? Thanks !
This is a generic error produced by the Windows network code when it kills an established connection for some reason. For example, it might happen if you pull the network cable out of the back of an Ethernet-connected computer, or if Windows has any other similar reason to believe the entire network has become unreachable.
Windows also generates this error if it has given up on the machine at the other end of the connection ever responding to it. If the network between your client and server goes down and your client then tries to send some data, Windows will make several attempts to send the data and will then give up and kill the connection. In particular, this can occur even if you didn't type anything, if you are using SSH-2 and PuTTY attempts a key re-exchange. (See section 4.19.2 for more about key re-exchange.)
(It can also occur if you are using keepalives in your connection. Other people have reported that keepalives fix this error for them. See section 4.13.1 for a discussion of the pros and cons of keepalives.)
We are not aware of any reason why this error might occur that would represent a bug in PuTTY. The problem is between you, your Windows system, your network and the remote system.
so i would look at you network connection, replace/try different cables, switches, computers and also try downloading a Linux live CD to eliminate you OS from any problems.
but if you can conncet too one and not the other see whats different? cables, routers, etc... then try swapping things around.
Thanks again, but I've already tried the swapping etc - no difference. My whole system goes through 1 16-port switch & changing everything, including cables, changes nothing.
Also, I have shares from my Ultra4plus mounted to my desktop PC - they're active & respond instantaneously. Frontview responds immediately from my PC. I can access all my shares from my phone remotely. I can access from another laptop using various methods & my WiFi connection.
My NV+ responds instantly from my PC using Frontview / explorer / Putty.
The only variable left is (something at the) Ultra4plus end : it doesn't like the ssh connection & it's only been like this since the recent updates.
Can I get the older firmware versions from somewhere & roll-back ?
I 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.
Re: ssh stopped working (connection abort) #19586817
Just 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.
