Embedded RDP dosent working with Macos, but with external works fine - errconnect_logon_failure 0x00000014

Hi Mark,

What is the format of the username your are sending to the server (username, username@domain, domain\\username)?

Best regards,

Hi Xavier,

the format is:

servername\username

domainname\username

Regards,
Markus

Hi,

FreeRDP (the component we use for embedded RDP session) expects to receive the username and domain separately. While, in the past, we were splitting those ourselves, this splitting was conflicting with the Username Format feature of RDM. That being said, this seems to be a common enough issue that we are considering bringing back the split (at least for the "domain\username" format).

In the mean time, you could probably separate the username and domain into their respective fields, although it might not be possible for all Credential type (I do not know what you use).

Best regards,

Hi Xavier,
Thanks for Replay.

I would be very happy when the old option (RDP) would be available again.

Is that planned in feature very soon?

BR
Markus

Hi markus,

You mean, the split of the username and domain? We are looking into it now. It's doubtful it will be in the next official release (2022.1). But it may very well be in a subsequent patch.

I'll post back in this ticket when it is available.

Best regards,

Hi Xavier,
i have install the new Version like 2021.2.15.0 (Enterprise) Mac Version.

It's strange, but with one mail server I can use the function "embedded" with the other not.

The username and password are the same and come from the exact same container from 1Password.

Username:
Domain\username

Passwort:
the Password

The only difference is that a Windows Server 2008 R2 (embedded works)" on Windows Server 2016 unfortunately does not work. I have already compared the entries.

What can I do?

BR
Markus

As far as I'm aware, it should never worked with domain\username if the domain and username do not get split somehow before the connection. That being said, I might very well be wrong and it could depend on the server version.

Is it still the errconnect_logon_failre (0x00000014).If so, at the moment, you can only do what I suggested and separate your username and domain yourself to ensure RDP receives them in separate fields. We are working on implementing the splitting programmatically, but It shouldn't be available for the next official release. Possibly for a subsequent patch.

Best regards,

Hi Markus

Like Xavier asked - on the Server 2016 machine, is the error the same (errconnect_logon_failure)?

If so, can you check the event log on that machine for a corresponding audit failure? That would be under Event Viewer > Windows Logs > Security - the corresponding event ID is 4625. The body of that event will indicate the reason for the logon failure (and include the username / domain information which should be obvious if something is being passed incorrectly).

Thanks and kind regards,

As far as I'm aware, it should never worked with domain\username if the domain and username do not get split somehow before the connection. That being said, I might very well be wrong and it could depend on the server version.

Is it still the errconnect_logon_failre (0x00000014).If so, at the moment, you can only do what I suggested and separate your username and domain yourself to ensure RDP receives them in separate fields. We are working on implementing the splitting programmatically, but It shouldn't be available for the next official release. Possibly for a subsequent patch.

Best regards,

Yes, it is the same Error 0x00000014. The Only difference is one Machine is Server 2008 and the other 2016.

Regards
Markus

Hi Markus

Did you see my message following Xaviers?

can you check the event log on that machine for a corresponding audit failure? That would be under Event Viewer > Windows Logs > Security - the corresponding event ID is 4625. The body of that event will indicate the reason for the logon failure (and include the username / domain information which should be obvious if something is being passed incorrectly)

Thank you!

Richard

Hi Markus,

Could you try the latest version (2022.1.3.0) and see if it resolves your issue?

Best regards,

Hello Xavier,

wow, with the new Version Update it works fine, now.

Thanks for your support.

Have a new day.

Best regards,
Markus

Hi Markus,

Glad to hear it!

Do not hesitate if you have any other issue/questions.

Best regards,