Results 1 to 2 of 2
Hello,
I'm new to these forums, but I was hoping someone could help me out with something. I'm having trouble with a server I run and being able to connect ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
- 06-06-2005 #1Just Joined!
- Join Date
- Jun 2005
- Posts
- 2
SSH Connection problems
Hello,
I'm new to these forums, but I was hoping someone could help me out with something. I'm having trouble with a server I run and being able to connect to it via SSH.
The server is running Fedora Core 3. The client is mostly OS X, but this happens through all machines I have tried to connect.
When the client tries to login (using debug mode):
$ ssh -vl user 172.16.66.x
OpenSSH_3.6.1p1+CAN-2004-0175, SSH protocols 1.5/2.0, OpenSSL 0x0090702f
debug1: Reading configuration data /etc/ssh_config
debug1: Rhosts Authentication disabled, originating port will not be trusted.
debug1: Connecting to 172.16.66.x [172.16.66.x] port 22.
debug1: Connection established.
debug1: identity file /Users/user/.ssh/identity type -1
debug1: identity file /Users/user/.ssh/id_rsa type -1
debug1: identity file /Users/user/.ssh/id_dsa type -1
debug1: Remote protocol version 1.99, remote software version OpenSSH_3.9p1
debug1: match: OpenSSH_3.9p1 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_3.6.1p1+CAN-2004-0175
debug1: An invalid name was supplied
Cannot determine realm for numeric host address
debug1: An invalid name was supplied
A parameter was malformed
Validation error
debug1: An invalid name was supplied
Cannot determine realm for numeric host address
debug1: An invalid name was supplied
A parameter was malformed
Validation error
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: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Host '172.16.66.17' is known and matches the RSA host key.
debug1: Found key in /Users/user/.ssh/known_hosts:11
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
debug1: Next authentication method: publickey
debug1: Trying private key: /Users/user/.ssh/identity
debug1: Trying private key: /Users/user/.ssh/id_rsa
debug1: Trying private key: /Users/user/.ssh/id_dsa
debug1: Next authentication method: password
user@172.16.66.x's password:
Connection closed by 172.16.66.x
debug1: Calling cleanup 0x1c540(0x0)
This problem has been posted a number of places, but I haven't been able to find a solution yet.
SSH has worked in the past few days on this box, but we've suddenly been having this problem. No new software has been installed, although I did upgrade my version of SSH, hoping it would fix the problem. I have also tried using the UseDNS setting in the sshd_config file.
The firewall has been turned off as well.
If anybody can help me out or direct me to a resource where I could find some help, I would greatly appreciate it.
Thank you in advance.
LJ
- 06-06-2005 #2Just Joined!
- Join Date
- Jun 2005
- Posts
- 2
Problem solved... ?
The problem seems to have actually been related to Mac OS X connecting to the server. I basically did the following:
$ cd ~/.ssh
... edited known_hosts to comment out the server ...
$ cp known_hosts known_hosts.bk
And then connected to the server:
$ ssh user@172.16.66.x
It still took a few moments, but eventually I got the prompt and was able to login. And now I don't have trouble connecting. It's pretty strange.


Reply With Quote
