Re: login by ssh fails
This is a generic problem you describe, but I'll try to (at least) give
you some directions on where to look for the source of that problem...
I have here two scenarios, one where the sshd daemon works fine
(scenario 1) and one where sshd doesn't work (scenario 2). I'm sorry if
that sounds a bit huh.. pedantic, that's not my intention; I'm trying to
be as clear as possible. So here we go....
Let's assume that the computer where you connect FROM is called A, and
the one where you connect TO via ssh is called B.
The way I see things, putty is responsible of the error. You did not
mention if Putty sent you any error messages, so I'm assuming a lot of
stuff here. Check out if the connection has been accepted on the server
(PC B) by browsing throught /var/log/auth.log .
Here's an extract of my /var/log/auth.log .. oslo is the server
(192.168.0.100) and helsinki is the PC I connect from (192.168.0.1).
Feb 24 18:42:04 oslo sshd2: connection from "192.168.0.1"
Feb 24 18:42:06 oslo sshd2: Public key
Feb 24 18:42:06 oslo sshd2: Public key authentication for user
Feb 24 18:42:06 oslo sshd2: User devsys, coming from helsinki,
I realise I don't tell you exactly WHAT is the problem, but at least I
help you find what is NOT the problem ... :)
OK now, for Scenario 2, a malfunctionning SSHD...
Another reason why you might not be able to connect could be that the
ssh daemon on the remote computer isn't up (functioning).
There are two ways to setup a sshd: as a daemon, or throught tcpwrapper
(inetd). If sshd is started as a daemon, try (on the remote computer) ps
-fe | grep ssh .. if nothing appears, the daemon is most likely not
If the daemon is started throught inetd, a line like the following
should appear in /etc/inetd.conf :
ssh stream tcp nowait root /usr/bin/tcpd $LOCATION/sshd
(where $LOCATION is of course WHERE the daemon is located).
OK, I might have told you the obvious, otherwise I hope I helped you !
On Mon, 2003-02-24 at 16:49, Willem-Jan Meijer wrote:
> Hello again,
> - AMD athlon 1300 was Pentium 2
> - Soltek mainboard was <unknown>
> - old HDD
> - old ram
> I couldn't boot anymore...3 beeps, 2 beeps, 1 beep and that's it...No
> picture, nothing so that's why I bought a new one. The move went fine except
> one thing
> When I connect a monitor and a keyboard to the server direct I can login.
> But I want to use PuTTY for an SSH remote login. PuTTY setup a connection.
> When I want to give a username, doesn't matter what kind of user, PuTTY
> What's going wrong? Has the old mainboard destroyed some config files?
> I can ping, write to the server by samba, apache, squid al works fine except
> a remote logine.
> Kind regards,
> Willem-Jan Meijer
> <-- Alle inkomende en uitgaande e-mail worden gescand op virussen -->
> <-- All incoming and outgoing e-mail is scanned for virusses -->