ssh problem

[Mario Vukelic]

On Tue, 2008-11-18 at 21:57 +0000, R Kimber wrote:
> 
> The last line of the output is
> 
> debug1: Connecting to potter.pol.keele.ac.uk [160.5.46.1] port 22
> 
> and then nothing else after.

This does seem weird, and as if the ssh client was not aware that
something goes wrong. Usually it would then continue with protocol
selection, identification, etc, that is:

ssh -v 192.168.1.100
OpenSSH_5.1p1 Debian-3ubuntu1, OpenSSL 0.9.8g 19 Oct 2007
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Connecting to 192.168.1.100 [192.168.1.100] port 22.
debug1: Connection established.
debug1: identity file /home/mario/.ssh/identity type -1
debug1: identity file /home/mario/.ssh/id_rsa type -1
debug1: identity file /home/mario/.ssh/id_dsa type -1
debug1: Remote protocol version 2.0, remote software version
OpenSSH_5.1p1 Debian-3ubuntu1
debug1: match: OpenSSH_5.1p1 Debian-3ubuntu1 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_5.1p1 Debian-3ubuntu1
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
<snip>

I guess you should verify somehow that the server works before spending
lots of time on a possible problem on your side.