ssh -v -v -v user@host # This is extremely verbose.
I'd bet though that if you are getting nothing back and can ping the IP Address of the server or the Hostname of the server that ssh may not be properly set up.
Originally Posted by gull04
So where are you running the telnet command from, presumably a command window?
What application are you using for ssh?
Is ssh connection allowed as root on the remote server? (Although that would normally give an access denied message.)
Also there seems to be no key in the known hosts file or no known hosts file.
Oh and one more thing, can you send the output of cat /etc/ssh/ssh_config from the target system.
# This is the ssh client system-wide configuration file. See
# ssh_config(5) for more information. This file provides defaults for
# users, and the values can be changed in per-user configuration files
# or on the command line.
# Configuration data is parsed as follows:
# 1. command line options
# 2. user-specific file
# 3. system-wide file
# Any configuration value is only changed the first time it is set.
# Thus, host-specific definitions should be at the beginning of the
# configuration file, and defaults at the end.
# Site-wide defaults for some commonly used options. For a comprehensive
# list of available options, their meanings and defaults, please see the
# ssh_config(5) man page.
# ForwardAgent no
# ForwardX11 no
# ForwardX11Trusted yes
# RhostsRSAAuthentication no
# RSAAuthentication yes
# PasswordAuthentication yes
# HostbasedAuthentication no
# GSSAPIAuthentication no
# GSSAPIDelegateCredentials no
# GSSAPIKeyExchange no
# GSSAPITrustDNS no
# BatchMode no
# CheckHostIP yes
# AddressFamily any
# ConnectTimeout 0
# StrictHostKeyChecking ask
# IdentityFile ~/.ssh/identity
# IdentityFile ~/.ssh/id_rsa
# IdentityFile ~/.ssh/id_dsa
# Port 22
# Protocol 2,1
# Cipher 3des
# Ciphers aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc
# MACs hmac-md5,hmac-sha1,email@example.com,hmac-ripemd160
# EscapeChar ~
# Tunnel no
# TunnelDevice any:any
# PermitLocalCommand no
# VisualHostKey no
# ProxyCommand ssh -q -W %h:%p gateway.example.com
# RekeyLimit 1G 1h
SendEnv LANG LC_*
Best to debug from server side, the side you wish to connect to, if everything else seems ok.
You can do it by command line starting the ssh server with multiple (up to 3) -d switches, and observe the output on screen.
Or uncomment / change the LogLevel in sshd_config to DEBUG3, restart and look at system logs.
Much more verbose output will follow.
I used this to succesfully debug one switch network brand which was unable to connect to SSH server due to server and client unable to find a common cipher to agree on.
Once i got it to debug mode, a server wrote a nice message, and when a chosen Cipher was added to server everything worked.
After you have identified the problem, turn it off since it will produce a lot of logs and possibly invade peoples privacy.