m.schouren

I am using the parent host feature because I use 1 gateway entry for multiple SSH sessions. The instructions that you link are for a 1:1 setup (1 tunnel for 1 session, where I want a single tunnel entry for multiple actual sessions). This functionality is described in https://forum.devolutions.net/topic23592-multiple-rdp-hosts-via-single-ssh-tunnel.aspx :

In the next RDM beta version, we will have a few enhancements for our SSH portforward type, which is pretty much SSH tunneling. You will be able to put a variable in the "destination" field when adding a portforward (you can put multiple portforwards in one entry). In your case you would put the $PARENT_HOST$ variable.Then, in your RDP sessions, you would edit them and in the VPN/Tunnel/Gateway tab you would set it up to open your portforward session, making sure to check the new "override parent" checkbox. This will make your portforward consider the RDP connection as its parent, even if it is not. This will then resolve the parent variables like $PARENT_HOST$ using your RDP session as a base, thus taking its host.

For RDP connections CTRL-ALT-BREAK should provide some form of fullscreen. It works the same as rightclicking the tab > full screen.

I'm doing a new evaluation of RDM. I want to tunnel SSH connections through an SSH tunnel to have a central break-out point within the network for management connections.

I set RDM up as follows to allow for a single 'gateway' connection to manage multiple remote machines.

Connection entry

• Name: gw-linux (jump host)

• Type: SSH tunnel

• Host: 192.168.0.14

• Port: Default

Outgoing tunnel settings:

• Local address: 127.0.0.1

• Local port: default

• Remote host: $PARENT_HOST$

• Remote port: 22

Next I set up an SSH Shell connection profile:

• Name: targethost

• Type: SSH Shell

• Host: 192.168.0.19

• Port: Default

VPN/SSH/Gateway

• Open: Always connect

• Type: SSH

• Settings > Session > gw-linux (jump host)

• Settings > Session > Use dynamic port: Enabled

• Settings > Other > Override parent ($PARENT_HOST$): Enabled

Now when I try to connect it establishes the tunnel to the jump host:

Connecting to 192.168.0.14 port 22

Local port 127.0.0.1:41621 forwaring to 192.168.0.19:22

Then it attempts to connect to the target machine (which should by accessible through 127.0.0.1:41621):

Connecting to 192.168.0.19 port 41621

Network error: Connection refused

So RDM is connecting to the target host instead of the tunnel. If I configure More > Alternate Host > Prompt for selection and add 127.0.0.1 to the list it works, but this seems a bit of a workaround for a bug.

Can you confirm whether I'm doing it wrong or this is just a bug?

edit: this appears to overlap a bit with the following topic: https://forum.devolutions.net/topic26515-ssh-tunnel-vpn-entry--dynamic-port-usage.aspx

I tested the fixed functionality.

It performs a lot better now. There is still some delay while RDM is talking to PMP but that is in the order of a few seconds instead of 10 minutes+ and not really something that RDM can fix.

Just one thing: the 'Default' filter does not appear to do anything (it does not filter). Since you initially start with looking for a resource it would make sense to have the 'Resource' filter selected by default (or make it a configurable option on the credential entry).

I will, thank you. When do you expect the next release of RDM to be out?

Thanks for the update. Happy to see the issue is being addressed.

Thanks. Should you need any extra information please let me know.

Do you have any update regarding this?

A possible solution would be to initially only request the list of servers. Subsequently when a server is selected the available accounts for it are fetched, allowing you to select a credential entry from PMP.

Please let me know what you think of this.

Thank you. I'd love to hear back from you regarding this.

Hi,

We're currently evaluating the possibility of using of Remote Desktop Manager for our company. One of the requirements is ME Password Manager Pro integration, which is the tool we store our passwords in.

This sort of works, albeit very slow. By the looks of it, RDM does the following when selecting a credential:

- Request a list of servers

- Iterate through that list by doing an additional API call for each entry.

Since each API call takes about 1.5 second, you can image how long this takes to do about 750 API calls. During this entire time the Password Manager Pro server consumes 100% CPU (while trying to fetch the information) and the client machine becomes quite slow as a whole.

Is there a way this can be fixed, by for example providing some caching mechanism so the API doesn't need to be accessed as intensively as it does now, and perhaps some progress indicator to monitor its progress?

Thanks for replying.