Hi to everybody...
I tried to find a workaround to my problem in the forums but nothing came up, so I start this topic...
Today I tried to SSH from my PC (Windows) to the SME Server box (SME 7.2, fully updated), but I kept getting the error "Server closed remote connection". Both PCs are on the same LAN-subnet and everything was working OK about a month ago, using either Putty or Secure Shell, but I only noticed this behaviour today.
Here is the latest part of my sshd.log file:
2007-07-05 10:07:26.935365500 Received disconnect from 10.0.1.100: 11: Disconnect requested by Windows SSH Client.
2007-07-05 10:07:38.690226500 Accepted password for root from 10.0.1.100 port 1279 ssh2
2007-07-05 13:10:41.862009500 Failed password for root from 10.0.1.100 port 1715 ssh2
2007-07-05 13:10:49.004034500 Accepted password for root from 10.0.1.100 port 1715 ssh2
2007-07-06 14:22:57.734340500 Server listening on 10.0.1.10 port 22.
2007-07-22 18:00:56.532579500 Server listening on 10.0.1.10 port 22.
2007-08-04 09:13:50.688043500 Server listening on 10.0.1.10 port 22.
2007-08-04 09:20:46.552173500 Server listening on 10.0.1.10 port 22.
2007-08-08 21:11:08.996449500 Server listening on 10.0.1.10 port 22.
2007-08-08 21:58:52.050064500 Accepted password for root from 10.0.1.154 port 1191 ssh2
2007-08-09 10:18:56.934184500 Server listening on 10.0.1.10 port 22.
2007-08-09 10:20:28.085790500 Accepted password for root from 10.0.1.100 port 4139 ssh2
2007-08-09 11:25:46.913140500 Server listening on 10.0.1.10 port 22.
2007-08-09 14:08:14.329426500 Received disconnect from 10.0.1.100: 13: Authentication cancelled by user.
2007-08-09 14:08:25.318152500 Accepted password for admin from 10.0.1.100 port 4296 ssh2
2007-08-09 16:04:58.230577500 Received SIGHUP; restarting.
2007-08-09 16:04:58.230581500 Server listening on 10.0.1.10 port 22.
2007-08-09 16:05:40.262842500 Received SIGHUP; restarting.
2007-08-09 16:05:40.274834500 Server listening on 10.0.1.10 port 22.
2007-08-11 18:07:17.348263500 Accepted password for root from 10.0.1.100 port 3849 ssh2
2007-08-18 11:24:21.455909500 Accepted password for root from 10.0.1.100 port 3667 ssh2
2007-08-31 12:12:30.257682500 Server listening on 10.0.1.10 port 22.
2007-08-31 12:13:19.755832500 Accepted password for root from 10.0.1.100 port 3821 ssh2
2007-09-11 13:15:36.287409500 Server listening on 10.0.1.10 port 22.
2007-09-11 13:18:06.245659500 Received SIGHUP; restarting.
2007-09-11 13:18:06.245663500 Server listening on 10.0.1.10 port 22.
2007-09-11 13:32:10.855525500 Server listening on 10.0.1.10 port 22.
2007-09-11 13:37:45.082644500 Received signal 15; terminating.
2007-09-11 13:37:45.094572500 Server listening on 10.0.1.10 port 22.
2007-09-11 13:44:07.575970500 Received SIGHUP; restarting.
2007-09-11 13:44:07.592975500 Server listening on 0.0.0.0 port 22.
2007-09-11 13:44:46.242966500 Received signal 15; terminating.
2007-09-11 13:46:53.215479500 Server listening on 10.0.1.10 port 22.
2007-09-11 14:06:57.296424500 Received signal 15; terminating.
2007-09-11 14:07:03.242869500 Server listening on 10.0.1.10 port 22.
2007-09-11 14:44:50.764593500 Received signal 15; terminating.
2007-09-11 14:45:08.604646500 Server listening on 10.0.1.10 port 22.
As you can see, SSH started producing errors on August, 9 .....
I found out that the same day, the openssh package was automatically updated by SME, as you can see below:
Aug 09 10:41:12 Updated: e-smith-openssh.noarch 1.12.0-9.el4.sme
Could have something gone wrong with the update??
I have direct access to the SME box, and also normal access to the Server Manager via http...Options on remote networks for SSH are enabled, and have tried both Public and private option, but still the same issue......I was thinking of uninstalling and reinstalling SSH, but I would like your help on this, or any other workaround you feel free to offer...
Thank you in advance,
Mike
1 Replies
1071 Views