nivron

Hi Michael,

Glad we could at least get it working for you, but we'd still like to find the root cause of your issue. Would you mind sending us a screenshot of your RDP settings in File -> Options -> Types -> Remote Desktop ?

Thanks!

Here are screenshotsof the RD settings.

Alright thanks for sending the logs, this should help us clear things out. Could you go in File -> Options -> Types -> Remote Desktop, and set the option "Enable API hooking" to "Disabled". We've had an issue similar to this recently and that was the cause.

Regards

That worked. I can get into local RDP sessions and the SSH tunneled ones now. Odd that I never had that issue on previous versions.

Hi Michael,

For the RDP -> SSH tunnel issue, could you please go in your SSH Tunnel settings, enable logging (tab Logs), retry the connection, and send us the resulting logs file ? We can't exactly replicate your issue at the moment, so this could be of great help.

Once that is done, could you go in File -> Options -> Types -> Terminal and enable the option "Use legacy terminal" at the very bottom. This could solve your issue, and if so would give us a better understanding of the cause.

Regards

I've uploaded the gateway log.

I can confirm "Use legacy terminal" doesn't have the CTRL+] issue.

Also, I hadn't checked the application log before, but I get this every time I try to connect with 3.8 and 3.10. I also hadn't tested just a regular RDP connection, but those don't work either. It's not dependent on the SSH tunnel for the failure.

System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

at MSTSCLib.IMsRdpClient9.Connect()

at AxMSTSCLib.AxMsRdpClient9NotSafeForScripting.Connect()

at Devolutions.RemoteDesktopManager.Frames.Embedded.FreEmbeddedRDP.Connect()

at Devolutions.RemoteDesktopManager.Managers.EmbeddedViewManager.OpenEmbedded(FreEmbeddedView frame, Connection connection, Boolean isConnected, OpenConnectionMode openConnectionMode, Image image, Image imageLarge, String svgName, Nullable`1 imagePaletteType)

at Devolutions.RemoteDesktopManager.Managers.EmbeddedViewManager.Open(Connection connection, FreEmbeddedView frame, Boolean isConnected, OpenConnectionMode openConnectionMode, Boolean undocked, Image image, Image imageLarge, String svgName, Nullable`1 imagePaletteType)

at Devolutions.RemoteDesktopManager.Business.Connectors.EmbeddedConnector.Connect(Connection connection, OpenConnectionMode openConnectionMode)

at Devolutions.RemoteDesktopManager.Managers.ConnectionManager.OpenConnection(Connection connection, OpenConnectionParameter parameter)

at Devolutions.RemoteDesktopManager.Managers.ConnectionManager.OpenConnections(Connection[] connectionList, OpenConnectionParameter parameter)

at Devolutions.RemoteDesktopManager.Managers.ActionManager.OpenConnections(OpenConnectionMode openConnectionMode, IConnectionSource source, Boolean checkOpenedConnection)

at Devolutions.RemoteDesktopManager.Frames.FreDashBoardBase.GalleryActions_ItemClick(Object sender, GalleryItemClickEventArgs e)

at DevExpress.XtraBars.Ribbon.Handler.GalleryControlHandlerBase.OnUnpressItem(DXMouseEventArgs e)

at DevExpress.XtraBars.Ribbon.Handler.GalleryControlHandlerBase.OnUnpress(DXMouseEventArgs e)

at DevExpress.XtraBars.Ribbon.Handler.GalleryControlHandlerBase.OnMouseUp(DXMouseEventArgs e)

at DevExpress.XtraBars.Ribbon.GalleryControl.OnMouseUp(MouseEventArgs e)

at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)

at System.Windows.Forms.Control.WndProc(Message& m)

at DevExpress.XtraEditors.XtraControl.WndProc(Message& m)

at DevExpress.Utils.Controls.ControlBase.BaseWndProc(Message& m)

at DevExpress.XtraEditors.BaseControl.WndProc(Message& msg)

at DevExpress.XtraBars.Ribbon.GalleryControl.WndProc(Message& m)

at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

Hi Michael,

For the RDP -> SSH tunnel issue, could you please go in your SSH Tunnel settings, enable logging (tab Logs), retry the connection, and send us the resulting logs file ? We can't exactly replicate your issue at the moment, so this could be of great help.

Once that is done, could you go in File -> Options -> Types -> Terminal and enable the option "Use legacy terminal" at the very bottom. This could solve your issue, and if so would give us a better understanding of the cause.

Regards

I've uploaded the gateway log.

I can confirm "Use legacy terminal" doesn't have the CTRL+] issue.

Hello,

We have fixed many things in the new beta release and some others fixes are coming next week. Hub Business, Hub Personal and DOD are now supported with this release.

https://cdn.devolutions.net/download/Devolutions.RemoteDesktopManager.Bin.2022.3.10.0.zip

https://cdn.devolutions.net/download/Setup.RemoteDesktopManager.2022.3.10.0.exe

Regards

Good morning,

I have installed the new 2022.3.10.0 version. I can confirm that I still have all of the issues I posted previously (icon for "Free" doesn't get removed from ProgramData, SSH tunnel-->RDP doesn't work, CTRL+] doesn't work, etc.). I had previously submitted my RDM file for analysis. I will also send screenshots of a blank upgrade finish window (the one that has the "Launch RDM now" checkbox, along with a "Connecting to..." screenshot.

I don't know if this problem existed in .8, but when launching one of the RDP sessions that just continually sits in the "Connecting to" state, their tabs don't get focused like a connected session does. I seem to remember even the "Connecting to" part getting focus when launching it.

I have uploaded a file to the support department. I have a "SSH Tunnel" connection that is called by the RDP connection. The "SSH Tunnel" also uses a Gateway because of IP restrictions.

Using the new beta version, I can connect the SSH Tunnel fine manually, and via the RDP connection. When attempting to use the RDP connection in the beta, I get "Connecting to" infinitely as opposed to "Connecting to localhost:XXXXX" like I do in 2022.2.26.0.

First of all, thanks for creating such a great product. I have been enjoying it for a couple of years.

I'm a RDM Free user. I installed the new version manually via browser, as the updater executable would only find the 2022.2.26.0 "free" version. My initial issues below caused me to have to roll back to 2022.2.26.0 version for the time being.

• The installer uninstalled the "free" version as expected to install the new merged version. The shortcut for the free version didn't get removed from the ProgramData folder.

• All of my host/credential entries showed up properly, however I have to re-acknowledge all of the SSH keys upon first connect.

• I have multiple SSH->SSH->RDP connections (connect to our datacenter, then to the client's datacenter, then to the RDP target). Those connections stopped working entirely. It would connect to the gateways properly, but the RDP session would say "Connecting to" instead of "Connecting to localhost:randomport". The connections would not complete and also didn't appear to timeout. There were no error messages.

• Previously working SSH connections stopped understanding CTRL+] (the telnet close connection) command. CTRL-Z and CTRL-C continue to work properly.

Now on the other hand, the app seems a bit snappier and I dig the new look (that I could see before I had to roll back) with the rounded tabs and whatnot.

I'm happy to do some additional testing if you like -- just let me know what you'd like to see. I made no changes at all in any of the hosts or the global settings before I attempted to do the things above, which all worked fine on 2022.2.26.0 vs. 2022.3.8.0.