CYGWin and sshd. Accepts authentication, but won't connect

Question

Everything I find relating to this is the "ssh-exchange-identification:" error. This doesn't happen for me. I get two lines:

Connection to localhost closed by remote host.
Connection to localhost closed.

ssh -v localhost spits out:

OpenSSH_5.8p1, OpenSSL 0.9.8r 8 Feb 2011
debug1: Reading configuration data /etc/ssh_config
debug1: Connecting to localhost [::1] port 22.
debug1: Connection established.
debug1: identity file /home/tim/.ssh/id_rsa type -1
debug1: identity file /home/tim/.ssh/id_rsa-cert type -1
debug1: identity file /home/tim/.ssh/id_dsa type -1
debug1: identity file /home/tim/.ssh/id_dsa-cert type -1
debug1: identity file /home/tim/.ssh/id_ecdsa type -1
debug1: identity file /home/tim/.ssh/id_ecdsa-cert type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_5.8
debug1: match: OpenSSH_5.8 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_5.8
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-ctr hmac-md5 none
debug1: kex: client->server aes128-ctr hmac-md5 none
debug1: sending SSH2_MSG_KEX_ECDH_INIT
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ECDSA 64:e3:27:90:ef:48:93:21:38:ea:9b:0e:0b:07:b0:2a
debug1: Host 'localhost' is known and matches the ECDSA host key.
debug1: Found key in /home/tim/.ssh/known_hosts:1
debug1: ssh_ecdsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: Roaming not allowed by server
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,password,keyboard-interactive
debug1: Next authentication method: publickey
debug1: Trying private key: /home/tim/.ssh/id_rsa
debug1: Trying private key: /home/tim/.ssh/id_dsa
debug1: Trying private key: /home/tim/.ssh/id_ecdsa
debug1: Next authentication method: keyboard-interactive
debug1: Authentications that can continue: publickey,password,keyboard-interactive
debug1: Next authentication method: password
tim@localhost's password:
debug1: Authentication succeeded (password).
Authenticated to localhost ([::1]:22).
debug1: channel 0: new [client-session]
debug1: Requesting no-more-sessions@openssh.com
debug1: Entering interactive session.
debug1: channel 0: free: client-session, nchannels 1
Connection to localhost closed by remote host.
Connection to localhost closed.
Transferred: sent 2008, received 1376 bytes, in 0.0 seconds
Bytes per second: sent 64774.0, received 44387.0
debug1: Exit status -1

I'm really at wit's end here because I couldn't get Windows' remote shell to even work. I'm so sick of using VNC just to get to a shell. Plus Windows' shell sucks because there is nothing like screen. Thanks

score -1 · Answer 1 · answered Aug 27 '11 at 00:39

-1

Have you looked at PuTTY and/or Tera Term Pro as possible alternatives? They are both "cleaner" implementations as well.

answered Aug 27 '11 at 00:39

user48838

7,393
2
17
14

I wasn't aware those were anything but clients. I use putty, but the problem here is a server, not a client. – timramich Aug 27 '11 at 15:22
Being "cleaner implementations" as well as alternative options, they can assist in sorting out functionality vs. user error situations. – user48838 Aug 27 '11 at 17:16
2

But the client wasn't my issue... – timramich Aug 28 '11 at 04:03
Understood that it was purely a user issue. – user48838 Aug 28 '11 at 06:12

score -1 · Answer 2 · answered Aug 27 '11 at 16:13

-1

Solved. Couldn't log in as my account, had to use sshd as the account.

answered Aug 27 '11 at 16:13

timramich

51
1
3

2

Could you elaborate on using sshd as the account? I never manually set a passwd for it, and I'm afraid that if I do it something else will break. – Nov 09 '11 at 22:41

score -2 · Answer 3 · edited Apr 13 '17 at 12:14

-2

First off, some friendly advice. For your own sanity, stop using VNC for connecting to Windows machines when you need a remote GUI. RDP will always be a better experience and comes with the base OS.

Second, there are numerous SSH Servers for Windows that are a lot less hassle than Cygwin with SSHD. Some are even free. There's a ServerFault thread about it here:

What is a good SSH server to use on Windows?

edited Apr 13 '17 at 12:14

Community

1

answered Jun 17 '12 at 06:21

Ryan Bolger

16,472
3
40
59

At the time I couldn't use RDP because it disables CUDA on nVidia cards. I've since given up on this because I got this cygwin ssh crap to work, but anything executed under it was painfully slow. – timramich Jul 20 '12 at 01:34

CYGWin and sshd. Accepts authentication, but won't connect

3 Answers3