Can no longer connect to one specific host since updating to feisty

[Manni]

Since I upgraded my system to feisty, I can no longer issue any tcp/ip connections to one specific host on my network. The machine offers ssh and irc services. I can no longer use any of these.

Connection attempts to both services will just result in a forever hanging connection that never seems to time-out.

The ssh connection will hang when my machine tries to exchange keys. Here's the last part of the output of a ssh -vvv:

debug1: Remote protocol version 2.0, remote software version OpenSSH_4.2-chrootssh
debug1: match: OpenSSH_4.2-chrootssh pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_4.3p2 Debian-8ubuntu1
debug2: fd 3 setting O_NONBLOCK
debug1: SSH2_MSG_KEXINIT sent

I have no idea how to further debug this issue, sorry.

[Manni (ubuntu-lxxi)]

Any TCP/IP gurus out there that might help me debug this problem?

[Jean-Baptiste Lallement (jibel)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

[Colin Watson (cjwatson)]

Status Invalid is not the way to ask for more information. Set to Incomplete.

[Colin Watson (cjwatson)]

If IRC is failing too, this doesn't sound like an openssh issue, but rather something deeper, so I'll punt this in the direction of the kernel ...

[Jean-Baptiste Lallement (jibel)]

Sorry for the wrong status.

Manni, is it still an issue ?

Thanks in advance .

[Manni (ubuntu-lxxi)]

Yes, it is. But I now tend to think of it as a bug of the host I can no longer connect to. The admins of this machine tell me that it is a very old and unpatched Solaris machine that also isn't able to talk to Vista's TCP/IP stack.

[Manni (ubuntu-lxxi)]

Since this doesn't seem to be a Ubuntu problem, I'm setting this bug to 'Invalid'.

[Jean-Baptiste Lallement (jibel)]

Thanks for the update. If you're really willing to track what's happening between the 2 hosts you can use tcpdump or wireshark and try to see where and why establishing a tcp session fails. Just my 2c.