[Info-vax] SSH problem after upgrade on remote system

[Dirk Munk]

helbig at asclothestro.multivax.de (Phillip Helbig (undress to reply)) wrote:
> I use ssh and scp from my VMS system to access a remote linux box (which
> I don't manage).  It has worked fine for years.  After an upgrade on
> the remote box, I get from ssh:
>
> warning: Authentication failed.
> Disconnected; key exchange or algorithm negotiation failed (Algorithm
> negotiation failed.).
>
> and from scp:
>
> tcpip$ssh_scp2.exe: warning: ssh2 client failed to authenticate. (or you
> have too old ssh2 installed, check with ssh2 "-V")
> warning: Authentication failed.
> Disconnected; key exchange or algorithm negotiation failed (Algorithm
> negotiation failed.).
>
> tcpip$ssh_scp2.exe: warning: child process (/sys$system/tcpip$ssh_ssh2)
> exited with code 131.
>
>
> %TCPIP-E-SSH_FC_ERROR, error in ssh file transfer operation
>
> If the problem is that the version is too old, can I get a newer one?  I
> also get it on my 8.4 node with (presumably) the latest version of ssh,
> though the version numbers look the same.
>
> Is it possible to enable something on the remote node?
>
There is another thread on a similar problem called "problem conncting 
via ssh to Fedora-linux-server FC22"
This is most likely exactly the same problem, so please read that thread 
for the solution.