SSH Sessions for vmware Appliances FAIL

Hello,

would it be possible to test the connection with 2020.2.18.0?
You can use the portable mode, so you can execute this version directly from the folder, without installation. The zip file can be found here

Regards,
Min

Do you have an update for the Remote Desktop Manager Free Edition that would resolve this issue?

I am using Enterprise Edition 2020.2.19.0 x64 and I am not able to connect to multiple CoreLELEC boxes with the same error message :) No problem with Putty.

Log:
[22.08.2020 21:17:49] Starting SSH, verbose level: 1
[22.08.2020 21:17:49] Setting up connection
[22.08.2020 21:17:49] Connecting as root
[22.08.2020 21:17:50] SSH banner: SSH-2.0-OpenSSH_8.3

[22.08.2020 21:17:50] Successfully authentified server
[22.08.2020 21:17:50] Starting interactive authentication
[22.08.2020 21:17:50] Starting interactive authentication
[22.08.2020 21:17:50] Starting interactive authentication
[22.08.2020 21:17:50] Starting interactive authentication
[22.08.2020 21:17:50] Starting interactive authentication
[22.08.2020 21:17:50] Starting interactive authentication
[22.08.2020 21:17:50] Disconnecting

I tried to disable Default credentials, the connection was interrupted as soon as I entered usernam "root". I would like to try to test it with another user but CoreELEC doesn't allow any change.

I am curious if you use username "root" too.

Ok, it's not related to username root.

I uninstalled 2020.2.19.0 and installed 2020.2.18.0 and I am able to connect to CoreELEC boxes via SSH again! It seems like 2020.2.19.0 brought a breaking change for some SSH connections. Not all because I was able to connect to various Linux servers, DiskStations etc.

Hello,

Thank you for providing us these logs, they have been given to our Engineering Department and a case has been opened with them in order to see what might cause this.
I will be in touch as soon as I will have an update on that matter.

Best regards,

Hi,

Thanks for the logs, but I will need that you send us another set of logs with the verbose level set to 2. This will provide me with more information and there are good chances I can fix this soon.

Regards,

The verbose level can be set in the "Advanced" tab.

Verbose logging set to 2.

[24.08.2020 22:40:08] Starting SSH, verbose level: 2

[24.08.2020 22:40:08] Setting up connection

[24.08.2020 22:40:08] Connecting as root

[24.08.2020 22:40:08] SSH banner: SSH-2.0-OpenSSH_8.3


[24.08.2020 22:40:08] Sending kex init

[24.08.2020 22:40:08] Received kex init

[24.08.2020 22:40:08] Selected algorithms: curve25519-sha256, ssh-ed25519, chacha20-poly1305@openssh.com, chacha20-poly1305@openssh.com, implicit by cipher, implicit by cipher, none, none

[24.08.2020 22:40:08] Sending Ed25519 kex init

[24.08.2020 22:40:08] Received Ed25519 kex reply

[24.08.2020 22:40:08] Successfully authentified server

[24.08.2020 22:40:08] Sending new keys message

[24.08.2020 22:40:08] Sending userauth service request

[24.08.2020 22:40:08] Received new keys message

[24.08.2020 22:40:08] Received extension info message

[24.08.2020 22:40:08] Server accepts public key types: ssh-ed25519,sk-ssh-ed25519@openssh.com,ssh-rsa,rsa-sha2-256,rsa-sha2-512,ssh-dss,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,sk-ecdsa-sha2-nistp256@openssh.com

[24.08.2020 22:40:08] Received service accepted message

[24.08.2020 22:40:08] Sending userauth init request

[24.08.2020 22:40:08] Received userauth failure: publickey,password,keyboard-interactive

[24.08.2020 22:40:08] Starting interactive authentication

[24.08.2020 22:40:08] Sending userauth interactive request

[24.08.2020 22:40:08] Received userauth failure: publickey,password,keyboard-interactive

[24.08.2020 22:40:08] Starting interactive authentication

[24.08.2020 22:40:08] Sending userauth interactive request

[24.08.2020 22:40:08] Received userauth failure: publickey,password,keyboard-interactive

[24.08.2020 22:40:08] Starting interactive authentication

[24.08.2020 22:40:08] Sending userauth interactive request

[24.08.2020 22:40:08] Received userauth failure: publickey,password,keyboard-interactive

[24.08.2020 22:40:08] Starting interactive authentication

[24.08.2020 22:40:08] Sending userauth interactive request

[24.08.2020 22:40:08] Received userauth failure: publickey,password,keyboard-interactive

[24.08.2020 22:40:08] Starting interactive authentication

[24.08.2020 22:40:08] Sending userauth interactive request

[24.08.2020 22:40:08] Received userauth failure: publickey,password,keyboard-interactive

[24.08.2020 22:40:08] Starting interactive authentication

[24.08.2020 22:40:08] Sending userauth interactive request

[24.08.2020 22:40:08] Received disconnection message, code: 2

[24.08.2020 22:40:08] Too many authentication failures

[24.08.2020 22:40:08] Disconnection in progress

[24.08.2020 22:40:08] Disconnecting

BR,

Radek

Hi,

I have seen this kind of problem a few times now, and a fix has been made and will be available in the next version. This bug is the result of a recent improvement for 2FA authentication and I am sorry for the inconvinience.
A fix is possible on the server side, if you have access to the sshd_config file. Check for the KbdInteractiveAuthentication parameter and make sure its value is set to no. If it's not there, then add the line:
KbdInteractiveAuthentication no
It should not have any effect on other clients because it will only stop the server from offering an authentication method it will refuse anyway. This setup "error" seems to be common in many default config files, probably because all SSH clients have the ability to recognize this situation and continue otherwise, as will RDM in its next version.

Regards

I have tested the new version (2020.2.20) but it has the same issue. Does the fix come in the next version?
Kind regards Micha

I confirm, the fix did not make it into 2020.2.20. It will be available in the next version.

Regards

Hello,

We have a RDM Beta online if you would like to give it a try.
https://remotedesktopmanager.com/home/download#Beta

Please note that there's a database upgrade involve if you are running a shared database
https://help.remotedesktopmanager.com/database_upgrade.html

Best regards,

Hi Jeff,

thanks a lot. I've tested the Beta and there it works!

Best regards
Michael

Hi,
could you please release a 2020.2.XX-Release with this fix integrated?

We don't run Beta's in production but would really need that fix!

Unfortunately it's not that simple. We will release the final version of RDM 2020.3 on October 20th.

Regards

Hi David,

thank you for your update.

So we will have to downgrade to 2020.2.18.0 and wait for 2020.3-release

Hi!

Is there a beta with this fix of the free edition?

Best Regards,

Nicolás.

Hello Nicolás,

The Free edition Version 2020.3.6.0 is available on our web site here: https://remotedesktopmanager.com/home/downloadfree

Best regards,

I was able to bypass the issue using the deprecated version of SSH rebex. The problem is I have a lot of connection that I have to mirror for it. I will be waiting for the update which suppose to be out 10/20/2020 which is already passed.

thanks

PS. I got the beta and works fine there as well

Accessing vmware linux appliances with SSH Sessions I get the following error
An unexpected error occurred. Error Code: FAIL
(-1) Non specific error: this is generally the result of data corruption

Version 2020.2.19.0 64-Bit

I can use Putty just fine to access these devices with no issues
I can also access non-vmware appliances with no issues, like ESXi hosts and do not have this issue.

I'm using 2020.3.14.0 and some sessions fail with Error unspecified -1.
I can work around using the Legacy mode.

I have this problem too, but with my all cisco (> 180) devices.

Hello,

You can refer to this Help topic for that error : https://kb.devolutions.net/rdm_error_code_fail_1_non_speciffic_error.html

Best Regards,

Hello,

You can refer to this Help topic for that error : https://kb.devolutions.net/rdm_error_code_fail_1_non_speciffic_error.html

Best Regards,

Thanks, that did it.