After upgrading to v. 13 some SSH sessions are not working

Do you use a Rebex SSH session?

Regards

Hi David,

yes I'm using Rebex

Thanks

Could you try to convert it to our default SSH client instead of Rebex? You can copy the session before.

Regards

Hello David,

With the default client is working fine, but we need to solve also with Rebex for two reason:

1) with the default client some function key are not working fine

2) we cannot easily convert sub connections

and 3)... if it was working before update I expect that will work again. Convert and tests hundreds of sessions need time

Do you have plan for fix this issue in next release?

Thanks

Fabio Grasso

We just have updated the Rebex component for the next minor update. I hope this. I will publish this version later today.

Regards

Hello,

I have similar problem with the update to 4.0.2.0

I see an error messages saying "Negociations failed. The connection was closed by the server."

It works fine with SSH-Shell, but it's difficult for me to change all my rebex sessions to built-in.

Best regards

@Fabien,

If you are using the Enterprise Edition of RDM, it's possible to convert easily your Rebex session into our native SSH Shell.

To do so, select your sessions and go in Edit -> Batch Edit -> Batch Actions and select Convert Putty/Rebex session to SSH/Telnet/PortForward session

I recommend trying with 1 or 2 session(s) to begin to make sure that the changes are applied properly.

Best regards,

You can also download the zip from RDM enterprise et replace all the Rebex dll for a test.

Regards

We just have updated the Rebex component for the next minor update. I hope this. I will publish this version later today.

Regards

When should this be released? Hundreds of SSH connections we have suddenly stopped working in 13.0.3.0 and converting them loses all kinds of settings.

Hello,

Here's the Rebex DLLs we use in the latest (and internal) version of RDM. Could you unzip them and see if this fixes your issue?

Regards,

No luck. Same error.

Hi, we are somewhat having the same problem.

This happened quite recently on existing, normally working, ssh rebex sessions.

Changing to native ssh resolves the issue, but thats not durable.

We are on version, 13.0.3.0, thanks.

Martin

Same to me, the zip file provided doesn't fix the issue with Rebex session, I'm also on 13.0.3.0.