It would have been better if you included the whole session log. For
example, did the command try to connect to the correct IP address for
linuxb? Etc.
Next, try invoking sshd on the other system with debugging turned on:
/usr/sbin/sshd -d -e
Note that this will cause sshd to not put itself into the background, and
will only process one connection before terminating. You can increase the
level of debugging by specifying a second or third -d option.
Mark Post
-----Original Message-----
From: Wolfe, Gordon W [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 25, 2003 5:58 PM
To: [EMAIL PROTECTED]
Subject: Re: ssh again
I do ssh -v linuxb and get (last few lines)
1803: Enabling compatibility mode for protocol 2.0
1803: debug1: Local version string SSH-2.0-OpenSSH_3.4p1
1803: debug1: SSH2_MSG_KEXINIT sent
1803: debug1: SSH2_MSG_KEXINIT received
1803: debug1: kex: server->client aes128-cbc hmac-md5 none
1803: debug1: kex: client->server aes128-cbc hmac-md5 none
1803: debug1: SSH2_MSG_KEX_DH_GEX_REQUEST sent
1803: debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
1803: Connection closed by UNKNOWN
1803: debug1: Calling cleanup 0x42289c(0x0)
Any of this mean anything to anyone? It sure doesn't to me.
Use the Best! Linux for Servers
Macintosh for Graphics
Palm for Mobility
Windows for Solitaire.
Gordon W. Wolfe, Ph.D. VM & Linux Systems Support
Enterprise Servers, The Boeing Company (425)865-5940
> ----------
> From: Post, Mark K
> Reply To: Linux on 390 Port
> Sent: Tuesday, November 25, 2003 2:37 PM
> To: [EMAIL PROTECTED]
> Subject: Re: ssh again
>
> Gordon,
>
> I would turn on some debugging here. Instead of "ssh linuxb" do "ssh -v
> linuxb" or even "ssh -v -v linuxb" and see where things are going wrong.
>
>
> Mark Post
>
> -----Original Message-----
> From: Wolfe, Gordon W [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, November 25, 2003 5:26 PM
> To: [EMAIL PROTECTED]
> Subject: ssh again
>
>
> This problem has been driving me crazy (in the words or Marty Feldman,
"Too
> late!") all week.
>
> I have two SLES8 Linux servers running under z/VM 4.3, LINUXA and LINUXB.
I
> cannot do a SSH connection from LINUXA to LINUXB.
>
> linuxa:~ # ssh linuxb
> 1714: Connection closed by UNKNOWN
>
> 1. There is nothing in the /var/log/message file about this.
> 2. Both are running SLES8.
> 3. Both are set up to use ssh protocol 2.
> 4. Both servers have the other server set up correctly in /etc/hosts
> and /etc/hosts.allow
> 5. This used to work!
> 6. I can successfully "telnet linuxb" and "ftp linuxb", so
> communications are working.
> 7. I can successfully "ssh linuxc" where linuxc is functionally
> identical to linuxb.
> 8. All the rpc PIDs and sshd appear to be working.
> 9. known_hosts and authorized_keys2 appear to be set up properly.
>
> What the heck does "Connection closed by UNKNOWN" mean? Where am I going
> wrong?
>
> Use the Best! Linux for Servers
> Macintosh for Graphics
> Palm for Mobility
> Windows for Solitaire.
> Gordon W. Wolfe, Ph.D. VM & Linux Systems Support
> Enterprise Servers, The Boeing Company (425)865-5940
>
>
