Your credentials did not work - RDM freeze

Hi,
This dialog comes directly from the Microsoft ActiveX. We will try to reproduce it. Are you sure you get this if you use a wrong password?

Regards

Hi,
Thanks for the quick reply. I'm fairly sure that this dialogbox comes from a wrong password, or using domain credentials (from the private vault) on a non domain joined machine.

That's always a bad credential set or failed authentication. The domain/user/password combo is wrong somewhere or can't be authenticated, and from a security perspective it doesn't tell you which part it thinks is wrong (like wrong password or invalid username).

With RDP, it does not care if the machine you are coming from is domain joined or not.. all it cares about is the credentials presented to the server you are connecting to. If your private vault has your local domain credentials trying to access a non-domain (or even a different domain) machine, then it will think about it for a little while, while it tries to detect the correct domain controller for the credentials you sent it. It will keep trying until it times out, and gives you that dialog box. If it is a non-domain machine you are connecting to, and you give it a different domain's credentials, the timeout should be almost instant, because it doesn't know about any other domains. If it belongs to a different untrusted domain, then it may take longer while it searches its global catalog to see what's available.

Now.. the machine you are connecting to could be having its own issues, like not being able to locate a DC/GC, which is usually a DNS or networking problem, and that will cause it to take a long time to time out, unless that machine already has a cached profile for the user, in which case it will try the cached credentials (assuming that hasn't been disabled). If it is not domain joined, then the local security authority (LSASS) could be failing.

If you are going to connect to a non-domain machine, then you'll want a 2nd entry in your private vault, and have it specify the credentials in one of a few different ways (I haven't played with it recently, so I'm not 100% sure which one is going to work).

RDP never assumes anything about the credentials you are sending.. when you are being authenticated before the destination's gina (logon dialog box) {this is the behavior for Vista/2008 and beyond}, then it will start populating your current userid (or the last one you used to connect to that server) and ask you for the password.

David F.

Hi,
I've done some more investigation. The issue only occurs with users using a Wacom Bamboo Fun Pen & Touch tablet. Latest drivers are installed.
When users with a Wacom tablet click on a session with an expired password in the private vault, or a non domain joint server, forcing RDM (or in fact RDP) displaying a credential popup, RDM freezes.
When the user does the very same action with a regular mouse, everything goes fine. We have 10 users with a Wacom tablet, and they all experience the same issue.
I know this is probably not an RDM issue, but any input and help is appriciated.

Do you know if RDM 32 vs 64 bit does the same thing?

Regards

We have tested this, and it occurs both with the 32 and 64 bit versions of RDM.

Any update on this one?
Thanks in advance.
Valid Operations.

We have a new RDP engine coming soon with FreeRDP. You will be able to test it and see if you get the same issue.

Regards

Hi David,
Any idea when we can expect the freeRDP implementation in RDM?

The next beta will have it as an option. I think it's already available but I know that we did some other fixes.

Regards

Hi Devolutions,
Just an update from my side.
The problem appeared to be in the Wacom settings along with some windows settings to use Windows Ink as handwriting.
When Use Windows Ink was disabled, RDM didn't freeze anymore when displaying a credential box.
It did also solve problems with the focus of other applications.
This case can be closed :)