Re: ssh client gets to server, but doesn't connect...?

ListenAddress 192.168.0.2
ListenAddress 192.168.0.4
Yeah, those are the IPs of the two NIC cards I have and LIstenAddress
That probably means one of the NIC's isn't doing anything, but that's another story.

lines WERE turned off initially, and I still got no answer from the
daemon to the client. So I tried enabling those as the latest "try" in
getting this to work. Either way, ListenAddress lines on or off, it
still doesn't work.
Do you know that the SYN is getting to your machine? If so, try stopping sshd and running it manually with -d (check that's the right option) to see what it's doing.
.

Relevant Pages

  • Re: ssh client gets to server, but doesnt connect...?
    ... daemon to the client. ... Either way, ListenAddress lines on or off, it ... I had in mind to try the other card -- swap the IPs and try the ... and this case of the missing ssh daemon is now solved. ...
    (comp.os.linux.networking)
  • Re: ssh doesnt work from inetd but ok as a daemon
    ... > When running from inetd you will not see anything listening on 22 since this is handled by inetd, when running as a daemon it will show up on netstat output. ... >> I have tried the following in sshd_config but it didnt work ... >> ListenAddress 0.0.0.0 ...
    (comp.security.ssh)