Ok, this is a weird one.
I have used lots of different SSH programs to connect to my Linux server cluster. The cluster is set up on a 10.10.1.x set of IP's. Every other program I've used lets me ssh from my bastion host to any other server on the network with no problems.
BUT, when I use AbsoluteTelnet 8.14, I immediately get something like this.
sql2 02:10:12 ~ # ssh 10.10.1.21
Received disconnect from 10.10.1.21: 2: Too many authentication failures for root
It doesn't allow me to enter the password to go with the SSH connection. I've tried just about every switch I can think of - it always immediately stops the connection.
The only thing I can think of is that there's an extra invisible character being sent when I press the enter key. But I tried the CR and CR/LF settings under the Options area, and that didn't affect anything.
Brian - any ideas? I really hope you can make this work -- your program is great so far.
Thanks!
Lars
Try the 'keyboard interactive' authentication type under Options->Properties->Connection->SSH2->Authentication. This is the default for some other SSH clients.
Are you *sure* that root access is enabled on this server?
Brian
I'm positive I have root access for this server - I log in like this on other SSH clients with no problem.
So it's strange - I did as you suggested and turned on the keyboard-interactive authentication, and now I get "Authentication Failed. Try again." when I try to log in to the server.
So with keyboard-interactive authentication, I can't get into my server to begin with. And without it, I can get to my bastion host, but I can't SSH to any other servers in my cluster.
It seems like when I try use the command line on my server to ssh to another server in the cluster, AbsoluteTelnet is taking over that command somehow and not letting the bastion host make that connection...? (not sure, I'm just guessing?) I don't understand why SSH'ing from my bastion host to another server in a cluster would be any different on any SSH client.
I've done this with the Mac Terminal program, Putty, and couple other SSH programs, so I know it *should* work, but I don't know why your program is acting differently.
This is what I get from my host-to-host SSH attempt (keyboard-interactive authentication has to be set to off when I connect to my bastion host to get in):
OpenSSH_4.7p1, OpenSSL 0.9.8g 19 Oct 2007
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Connecting to 10.10.1.21 [10.10.1.21] port 22.
debug1: Connection established.
debug1: permanently_set_uid: 0/0
debug1: identity file /root/.ssh/identity type -1
debug1: identity file /root/.ssh/id_rsa type -1
debug1: identity file /root/.ssh/id_dsa type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_4.7
debug1: match: OpenSSH_4.7 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_4.7
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(1024<1024<8192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Host '10.10.1.21' is known and matches the RSA host key.
debug1: Found key in /root/.ssh/known_hosts:1
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
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: Offering public key: from file
debug1: Authentications that can continue: publickey,password,keyboard-interactive
debug1: Trying private key: /root/.ssh/identity
debug1: Trying private key: /root/.ssh/id_rsa
debug1: Trying private key: /root/.ssh/id_dsa
debug1: Next authentication method: keyboard-interactive
Received disconnect from 10.10.1.21: 2: Too many authentication failures for root
Are you using RSA authentication to login to bastion?
Brian
Did you get my last question?
I assume we gave up, then?
B
