Users

All Posts (5)

avatar

ptong

RD Gateway - connections not using existing credential entries, but custom is fine

avatar
avatar
avatar
avatar
avatar

Does the domain is typed the same way in the credentials than when you save it directly?

If you mean that we fill in the username field with just the username (rather than DOMAIN\username), yes.

So the domain field in our case is populated with the short form of the domain ie. DOMAIN rather than domain.local or similar.

(I even went so far as to match case - ie. Administrator with a capital "A" - although being Windows it should not matter).

If the tickbox to use the same credentials for RD Gateway as the server is ticked, the prompt asks for both at the same time (as if I had not provided credentials at all).

If we untick the box and set the RD Gateway credentials by selecting a credential entry, the first prompt is for the RD Gateway credentials, which is blank.

RD Gateway - connections not using existing credential entries, but custom is fine

avatar
avatar
avatar
avatar
avatar

This is really strange. Could you tell me what type of linked credential it is? Is it a LastPass or a normal user/password?

The credential is an internal one - one that you create with New - Credential Entry.

RD Gateway - connections not using existing credential entries, but custom is fine

avatar
avatar
avatar
avatar
avatar

Hello Phillip,

Do you have this issue in embedded or external mode?

Hi David,

Interesting you mention this.

Normally we use the connections in embedded mode.

However, if I open one in external mode (right-click - Open with parameters - Open (External)), that works correctly, but also any other connections opened after that in the current RemoteDesktopManager session (embedded or external) work correctly as well (ie. it utilises the credentials), until RemoteDesktopManager is closed.

After (re)opening RemoteDesktopManager, the same behaviour returns.

RD Gateway - connections not using existing credential entries, but custom is fine

avatar
avatar
avatar
avatar
avatar

I did see a few similar mentions of this in the forum, but nothing specific like this.

We have quite a few entries in our database that require the use of a Remote Desktop (RD) Gateway, and as part of that we have a number of saved credential entries (typically on a per-client or per-environment basis).

What we have noticed is that for those connection entries that manually specify the username/password for the RD Gateway credentials (where the password is saved in the database), the connection works as intended (ie. untick "Use my RD Gateway credentials for remote computer", then select "Use Custom Credentials" in the RD Gateway credentials dialogue).

However, if we set the option to use an existing credential entry and select it (in the RD Gateway credentials setting), OR we select the "Use my RD Gateway credentials for remote computer" option (and opt to use a credential entry for the main login), we get prompted to enter the credentials anyway, which is not what we want (ie. we want the credentials to be pre-filled from the database, since not all users should know what the password is).

Seems like the RDP client within RemoteDesktopManager does not want to read the RD Gateway credentials when they are stored as an existing credential entry (as opposed to separately saved per connection in the database) - or is there a setting that needs to be set to make this happen?

Or is this a (long-standing) bug?

Expired connection still locked if option unticked

avatar
avatar
avatar

In doing some testing as part of restructuring how we use Remote Desktop Manager in our workplace, I was testing the "expire" option against a RDP connection (though it is likely to happen for any other connection type with this option).

It is all good and well if a connection expires (one cannot use the connection), but if you untick the "Expire" tickbox, the connection still remains expired (and highlighted orange), and the expired message appears.

Only if you tick the box again (if unticked), change the date to either today or in the future, then untick it will the connection become available for use again (ie. not expired).

1 - 5 of 5 items