I just updated to 2022.2.14 this morning (free edition) and now I can't RDP into any of my servers ("an internal error has occured").
Most of my entries use Linked (Vault), which are the various proxy servers I connect through (on port 4489). If I turn off the linked host, switch to Custom, and put the same host into the Host field, it works and connects. But if I go back to Linked (Vault), it fails. This was working fine on Friday so I suspect it's something with the 2022.2.14 update?
In case this is related, if I try to export the entry to a .rdp file, the "full address" line is missing the host name and just has the 4489 port. But I haven't tried exporting these entries before so not sure if that usually happens if the entry has a linked host instead of a custom entry.
Here's what I see in the debug panel, if this helps:
Double click triggered Double click node:<my entry name> rdpClientAdvancedSettings4.AuthenticationLevel:0 Opening in Console / Admin mode rdpClientAdvancedSettings6.EnableCredSspSupport:True An internal error has occurred. | reason: 4 | extended: exDiscReasonNoInfo RDP - Disconnect:4 / exDiscReasonNoInfo
Could there also be an issue with the custom port (4489)? My networking guys are reporting that they are seeing connections from my machine to the hosts on port 3389 instead of 4489 so the firewall is blocking the traffic. So maybe it's an issue with the non-default port plus the linked vault host?
Again, all of this was working fine last week. I'm going to see if I can downgrade RDM to the previous version.
I removed 2022.2.14 and re-installed 2022.1.27 and I'm able to connect again.
Hello,
A ticket has been created to investigate this issue. We will keep you updated on the progress.
Regards,
Michaël Beaudin
Thank you!
Hi,
We have fixed the issue internally. It should be available starting with version 2022.2.15
Regards,
Jean-Francois Duchesne
Woo hoo! Thank you!
Hi Jeremy,
We had to fixed a bug related to this issue. It should be available starting with version 2022.2.16 instead.
Sorry for the delay.
Regards,
Jean-Francois Duchesne
No worries, appreciate the fix!
I just upgraded to 2022.2.17 and this seems to be working again. Thank you!
Hi,
I'm glad to hear your issue was resolved.
If you have another issue don't hesitate to make a new post. We will be happy to help you.
Regards
Jean-Francois Duchesne