First, is the ssh daemon actually running on the box? (take a look at
the process list, and nmap the box to make sure that ssh is bound to
port 22).
If it is running, are there any access control mechanisms in place?
IPChains / IPTables, TCP Wrappers, host control mechanism in the sshd
config, etc.
Stan Brown wrote:
I can't seem to get ibound ssh working to a new woody box. Here is what ssh
-v has to say about it:
Script started on Tue Jan 22 09:27:45 2002
$ ssh -v teddy
OpenSSH_2.9 FreeBSD localisations 20011202, SSH protocols 1.5/2.0, OpenSSL
0x0090601f
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Rhosts Authentication disabled, originating port will not be trusted.
debug1: restore_uid
debug1: ssh_connect: getuid 210 geteuid 0 anon 1
debug1: Connecting to teddy.fas.com [205.159.77.231] port 22.
debug1: temporarily_use_uid: 210/210 (e=0)
debug1: restore_uid
debug1: temporarily_use_uid: 210/210 (e=0)
debug1: connect: Connection refused
debug1: restore_uid
debug1: Trying again...
debug1: Connecting to teddy.fas.com [205.159.77.231] port 22.
debug1: temporarily_use_uid: 210/210 (e=0)
debug1: restore_uid
debug1: temporarily_use_uid: 210/210 (e=0)
debug1: connect: Connection refused
debug1: restore_uid
debug1: Trying again...
debug1: Connecting to teddy.fas.com [205.159.77.231] port 22.
debug1: temporarily_use_uid: 210/210 (e=0)
debug1: restore_uid
debug1: temporarily_use_uid: 210/210 (e=0)
debug1: connect: Connection refused
debug1: restore_uid
debug1: Trying again...
debug1: Connecting to teddy.fas.com [205.159.77.231] port 22.
debug1: temporarily_use_uid: 210/210 (e=0)
debug1: restore_uid
debug1: temporarily_use_uid: 210/210 (e=0)
debug1: connect: Connection refused
debug1: restore_uid
Secure connection to teddy.fas.com refused.
$ ^D
Script done on Tue Jan 22 09:27:58 2002
What have I done wrong?
--
ACHERON
[EMAIL PROTECTED]