OpenSSH 3.9p1 on Linux, and whatever the most current verion on Mac OS X is (I don't have my iBook with me currently, but it is having the same problem) will not connect correctly to an IBM Remote Supervisor Adapter II card. The card runs some type of embedded software and provides an SSH connection to the command-line interface to do nifty things on your IBM xSeries machine like power off/on, tempature monitoring and the like. The RSA will accept the username and password, but then close the connection instead of offering the shell. I will attach a copy of the debug trace. Could this be a client-server version negotiation issue? Thanks. Moshe Hyzon
Created attachment 840 [details] Debug (-v -v -v) dump of failed connection
I forgot to mention that PuTTY under windows (version 0.56) works fine connectiong to the RSAII.
Comment on attachment 840 [details] Debug (-v -v -v) dump of failed connection >debug2: channel 0: open confirm rwindow 65536 rmax 16384 >debug1: channel 0: free: client-session, nchannels 1 >debug3: channel 0: status: The following connections are open: > #0 client-session (t4 r0 i0/0 o0/0 fd 4/5 cfd -1) >debug3: channel 0: close_fds r 4 w 5 e 6 c -1 >Connection to dgsq-asm1 closed by remote host. >Connection to dgsq-asm1 closed. This looks like the server is exitting immediately (crashing, perhaps?) Is there any way to check the server's log or run it in debug mode? A couple of things you can try (but probably won't help): * disable agent forwarding: ("ssh -o ForwardAgent=no yourserver") * disable pty allocation ("ssh -T yourserver") Failing that you may have to ask IBM. >I've compared this to a successful login to another machine and the only difference is the lines >debug2: channel 0: open confirm rwindow 0 rmax 32768 >debug2: channel 0: rcvd adjust 131072 That's just the receive window size and maximum (ssh) packet size, those can be different for different implementations.
(In reply to comment #2) > I forgot to mention that PuTTY under windows (version 0.56) works fine > connectiong to the RSAII. Could you turn on packet debugging in PuTTY, log a connection and attach the log? (your password may be in the log so make sure you delete it it before uploading). It may not help either but comparing it with the OpenSSH log may provide a clue.
Created attachment 843 [details] PuTTY packet log Here is a successful connection via PuTTY
(In reply to comment #3) > This looks like the server is exitting immediately (crashing, perhaps?) Is > there any way to check the server's log or run it in debug mode? > A couple of things you can try (but probably won't help): > * disable agent forwarding: ("ssh -o ForwardAgent=no yourserver") That did it! APparently, the IBM server doesn't like agent forwarding. :-/ Well, I guess it's their problem, then huh?
(In reply to comment #6) > (In reply to comment #3) > > This looks like the server is exitting immediately (crashing, perhaps?) Is > > there any way to check the server's log or run it in debug mode? > > A couple of things you can try (but probably won't help): > > * disable agent forwarding: ("ssh -o ForwardAgent=no yourserver") > That did it! APparently, the IBM server doesn't like agent forwarding. :-/ > Well, I guess it's their problem, then huh? Also, X11Forwarding needs to be off as well.
(In reply to comment #6) > > ("ssh -o ForwardAgent=no yourserver") > > That did it! Wow, that was a long shot. > Apparently, the IBM server doesn't like agent forwarding. :-/ > Well, I guess it's their problem, then huh? Sure looks like that, and without some kind of debugging from the server, IBM is the only one who can verify it.
Change all RESOLVED bug to CLOSED with the exception of the ones fixed post-4.4.