[TriLUG] ssh DOA, but machine pings fast
William Sutton
william at trilug.org
Thu Feb 12 11:08:00 EST 2004
Well it appears the remote sshd is running. For giggles I turned sshd off
on my laptop:
kenobi:~$ ping corran
PING corran.shaldannon.net (192.168.1.2) 56(84) bytes of data.
64 bytes from corran.shaldannon.net (192.168.1.2): icmp_seq=1 ttl=64
time=0.705 ms
64 bytes from corran.shaldannon.net (192.168.1.2): icmp_seq=2 ttl=64
time=0.253 ms
64 bytes from corran.shaldannon.net (192.168.1.2): icmp_seq=3 ttl=64
time=0.252 ms
--- corran.shaldannon.net ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1998ms
rtt min/avg/max/mdev = 0.252/0.403/0.705/0.213 ms
kenobi:~$ ssh -v corran
OpenSSH_3.5p1, SSH protocols 1.5/2.0, OpenSSL 0x0090701f
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Rhosts Authentication disabled, originating port will not be
trusted.
debug1: ssh_connect: needpriv 0
debug1: Connecting to corran [192.168.1.2] port 22.
debug1: connect to address 192.168.1.2 port 22: Connection refused
ssh: connect to host corran port 22: Connection refused
So I turned it back on and tried again:
kenobi:~$ ssh -v corran
OpenSSH_3.5p1, SSH protocols 1.5/2.0, OpenSSL 0x0090701f
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Rhosts Authentication disabled, originating port will not be
trusted.
debug1: ssh_connect: needpriv 0
debug1: Connecting to corran [192.168.1.2] port 22.
debug1: Connection established.
debug1: identity file /home/william/.ssh/identity type -1
debug1: identity file /home/william/.ssh/id_rsa type -1
debug1: identity file /home/william/.ssh/id_dsa type 2
debug1: Remote protocol version 1.99, remote software version
OpenSSH_3.5p1
debug1: match: OpenSSH_3.5p1 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_3.5p1
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-cbc hmac-md5 none
debug1: kex: client->server aes128-cbc hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: dh_gen_key: priv key bits set: 128/256
debug1: bits set: 1630/3191
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Host 'corran' is known and matches the RSA host key.
debug1: Found key in /home/william/.ssh/known_hosts:8
debug1: bits set: 1593/3191
debug1: ssh_rsa_verify: signature correct
debug1: kex_derive_keys
debug1: newkeys: mode 1
debug1: SSH2_MSG_NEWKEYS sent
debug1: waiting for SSH2_MSG_NEWKEYS
debug1: newkeys: mode 0
debug1: SSH2_MSG_NEWKEYS received
debug1: done: ssh_kex2.
debug1: send SSH2_MSG_SERVICE_REQUEST
debug1: service_accept: ssh-userauth
debug1: got SSH2_MSG_SERVICE_ACCEPT
debug1: authentications that can continue:
publickey,password,keyboard-interactive
debug1: next auth method to try is publickey
debug1: try privkey: /home/william/.ssh/identity
debug1: try privkey: /home/william/.ssh/id_rsa
debug1: try pubkey: /home/william/.ssh/id_dsa
debug1: authentications that can continue:
publickey,password,keyboard-interactive
debug1: next auth method to try is keyboard-interactive
debug1: authentications that can continue:
publickey,password,keyboard-interactive
debug1: next auth method to try is password
william at corran's password:
The differences don't mean a lot to me besides the version differences and
the fact that I have a .ssh/id_dsa value of 2 and you have one of -1.
Anybody else see anything?
On Thu, 12 Feb 2004, Turnpike Man wrote:
> just as I posted, more came through: (and doh! so much for hiding hostname)
>
> seee below
>
> --- Turnpike Man <turnpike420 at yahoo.com> wrote:
> > I have a server which seems to have bit the bullet. I can ping fast:
> >
> > PING 192.168.75.100 (192.168.75.100) 56(84) bytes of data.
> > 64 bytes from 192.168.75.100: icmp_seq=0 ttl=64 time=0.323 ms
> > 64 bytes from 192.168.75.100: icmp_seq=1 ttl=64 time=0.279 ms
> > 64 bytes from 192.168.75.100: icmp_seq=2 ttl=64 time=0.264 ms
> > 64 bytes from 192.168.75.100: icmp_seq=3 ttl=64 time=0.284 ms
> >
> > However, when I try to ssh, much of nothing, so I tried with -v option:
> >
> > ssh -v <hostname> #hid my hostname
> > OpenSSH_3.6.1p2, SSH protocols 1.5/2.0, OpenSSL 0x0090701f
> > debug1: Reading configuration data /etc/ssh/ssh_config
> > debug1: Applying options for *
> > debug1: Rhosts Authentication disabled, originating port will not be trusted.
> > debug1: Connecting to bertha [192.168.75.100] port 22.
> > debug1: Connection established.
> > debug1: identity file /home/dmcdowell/.ssh/identity type -1
> > debug1: identity file /home/dmcdowell/.ssh/id_rsa type -1
> > debug1: identity file /home/dmcdowell/.ssh/id_dsa type -1
> debug1: Remote protocol version 1.99, remote software version OpenSSH_3.5p1
> debug1: match: OpenSSH_3.5p1 pat OpenSSH*
> debug1: Enabling compatibility mode for protocol 2.0
> debug1: Local version string SSH-2.0-OpenSSH_3.6.1p2
> debug1: SSH2_MSG_KEXINIT sent
>
> and she just sits there again
> >
> > and she just sits there like a knot on a log... I don't have console access
> > at
> > this time, only remote.
> >
> > Ideas?
> >
> > thanks,
> > David M.
> > *keeping it real and on topic*
> >
> > __________________________________
> > Do you Yahoo!?
> > Yahoo! Finance: Get your refund fast by filing online.
> > http://taxes.yahoo.com/filing.html
> > --
> > TriLUG mailing list : http://www.trilug.org/mailman/listinfo/trilug
> > TriLUG Organizational FAQ : http://trilug.org/faq/
> > TriLUG Member Services FAQ : http://members.trilug.org/services_faq/
> > TriLUG PGP Keyring : http://trilug.org/~chrish/trilug.asc
>
>
> __________________________________
> Do you Yahoo!?
> Yahoo! Finance: Get your refund fast by filing online.
> http://taxes.yahoo.com/filing.html
>
More information about the TriLUG
mailing list