Well, after reboot it logged this Nov 23 11:07:55 mand sshd2[117]: Listener created on port 22. Nov 23 11:07:55 mand sshd2[118]: Daemon is running. Nov 23 11:08:05 mand sendmail[138]: starting daemon (8.9.3): SMTP+queueing@00:30:00 Nov 23 11:08:06 mand sshd[144]: error: bind: Address already in use Nov 23 11:08:06 mand sshd[144]: fatal: Bind to port 22 failed: Transport endpoint is not connected. And when connecting from intranet machine of private IP, it logs this: at the 3rd row it seems to be swithing on to sshd, but I do not know where is sshd in inet.d Nov 23 11:08:35 mand sshd2[118]: connection from "192.168.42.2" Nov 23 11:08:36 mand sshd2[172]: DNS lookup failed for "192.168.42.2". Nov 23 11:08:36 mand sshd[172]: log: Generating 768 bit RSA key. Nov 23 11:08:37 mand sshd[172]: log: RSA key generation complete. Nov 23 11:08:37 mand sshd[172]: log: Connection from 192.168.42.2 port 1224 Nov 23 11:08:37 mand sshd[172]: log: Could not reverse map address 192.168.42.2. Nov 23 11:08:43 mand sshd[172]: log: Password authentication for antal accepted. /-------------------------/ Antal Leisen webmaster@kreorg.hu Kreorg Educational Center Budapest, Hungary
You seem to be starting both sshd2 and sshd at the same time and yet they are both supposed to connect to the same port. Look for the script that is starting sshd and remove it. The compatibility with sshd in sshd2 is done in the sshd_config file where sshd2 is told to pass the requests on to sshd1 do not start sshd1 yourself.
Nov 23 11:08:35 mand sshd2[118]: connection from "192.168.42.2" Nov 23 11:08:36 mand sshd2[172]: DNS lookup failed for "192.168.42.2". Nov 23 11:08:36 mand sshd[172]: log: Generating 768 bit RSA key. Nov 23 11:08:37 mand sshd[172]: log: RSA key generation complete. Nov 23 11:08:37 mand sshd[172]: log: Connection from 192.168.42.2 port 1224 Nov 23 11:08:37 mand sshd[172]: log: Could not reverse map address 192.168.42.2. Nov 23 11:08:43 mand sshd[172]: log: Password authentication for antal accepted. There is nothing wrong with this to avoid the could not reverse map just set up your dns and set up a reverse zone for 42.168.192.in-addr.arpa
participants (2)
-
semat
-
webmaster