SubConnections are am i missing something ?

Hello,

Sub-connections are not for that purpose, they were meant to easily allow for multiple protocols (RDP, VNC, etc) to be used against the same host (our current recommendation is to stop using them anyway....)

What you want to do can be achieved in two manners:

Our RDM Jump is the most powerful, but it does require that first hop to be made with RDP, so for multiple concurrent access by your colleagues it would require that the jump box be a Terminal Services Server. Lone users do not suffer from that requirement.

SSH Tunnels usually only use a single port to be used by a connection, so they are somewhat limited for advanced scenarios, but for 80% of use cases they do fit perfectly.

Since you mention that you first establish a RDP connection, it means that RDM Jump would be easy to use. If you do not need multiple concurrent access, simply follow the first link I sent and you will find detailed instructions.

Best regards,

Yes!
That did the trick!
thank you very much Maurice :)

Can you elaborate on this statement more?
Why is this your recommendation to stop using sub-connections?
What is your recommended alternative?

Hello,

@H K, some features are not available with subconnections like Batch Edits. Only the General Settings can be modified though the batch edit feature on subconnections.

A recommended alternative is creating a folder and then create all connection type as single entry under that folder. It is possible to use variables and credential inheritance from the parent folder.








Best regards,