Credentials Dialog Keeps Popping Up

Also the clipboard isn't working on FreeRDP.

Hello Derek,

Thank you for contacting us on that matter!

Which version of RDM and what type of Data Source you are currently using? Is there a reason why you are not using the "Latest" RDP engine instead? Do you encounter any issues with it?

Best regards,

Hello Derek,

Thank you for contacting us on that matter!

Which version of RDM and what type of Data Source you are currently using? Is there a reason why you are not using the "Latest" RDP engine instead? Do you encounter any issues with it?

Best regards,
James Lafleur

RDM version: 2022.3.27.0 64-bit
Data source: RDP (Microsoft Remote Desktop)
Reason: "Latest" produces input lag for my RDP while "FreeRDP Latest" is buttery smooth.

Hello,

Thank you for your swift reply!

Would it be possible for you to provide us screenshots of the configuration of your RDP entry? I would like to see sections that are not using their default values.
Also, do you experience the same input lag if you launch your RDP connection with MSTSC.exe?

Best regards,

Hello,

Thank you for your swift reply!

Would it be possible for you to provide us screenshots of the configuration of your RDP entry? I would like to see sections that are not using their default values.
Also, do you experience the same input lag if you launch your RDP connection with MSTSC.exe?

Best regards,

I've attached screenshots, I just tried out Latest again and even that is asking for credentials now and clipboard isn't working.

Hello,

Would it be possible for you to go under the "Authentication" of your entry and uncheck the "Enable Network level authentication (NLA)" option?
As for the clipboard not working with the "FreeRDP" engine, I have verified it on my end and this is a known limitation of this engine.

Best regards,

Hello,

Would it be possible for you to go under the "Authentication" of your entry and uncheck the "Enable Network level authentication (NLA)" option?
As for the clipboard not working with the "FreeRDP" engine, I have verified it on my end and this is a known limitation of this engine.

Best regards,

It still prompts after being unchecked.

Hello,

Would it be possible for you to open your Windows Credentials Manager, outside of RDM, and see if you have any credentials saved for the hosts you are trying to connect to?
If you do, could you please delete them and try to launch the RDP connection from RDM once again and see if the same issue occurs? If it does, please go under Help -> Submit a support ticket, check both options found in the form and just mention this forum thread in the description of your case.

I will analyze the data that will be provided to us and provide you a link to schedule a remote session to take a closer look at this issue.

Best regards,

Hello,

Would it be possible for you to open your Windows Credentials Manager, outside of RDM, and see if you have any credentials saved for the hosts you are trying to connect to?
If you do, could you please delete them and try to launch the RDP connection from RDM once again and see if the same issue occurs? If it does, please go under Help -> Submit a support ticket, check both options found in the form and just mention this forum thread in the description of your case.

I will analyze the data that will be provided to us and provide you a link to schedule a remote session to take a closer look at this issue.

Best regards,

The credentials dialog keeps popping up when I connect to window 2003 server though FreeRDP(or FreeRDP Latest), I cancel the dialog,it can login. The annoying dialog is unwanted.

FreeRDP is important to me that it is friendly DPI with old system like when I use win11 with 4K resolution and high DPI connect to win2003.

Everything is ok when I connect to window 2008 or greater(win8/10/11/2012/12016/2019/2022) though FreeRDP(or FreeRDP Latest).

Pls fixed the issue, thanks.

Screen dump 
https://i.postimg.cc/rFNgGk0S/Snipaste-2023-01-14-18-14-34.png

Hello,

Thank you for contacting us on that matter!

Out of curiosity, even though you mentioned that you need to use FreeRDP to connect to your old servers, are you able to connect to your Windows Server 2003 using RDM's default RDP engine (RDP (Latest)?

Since this issue only occurs when you connect to your Windows Server 2003, I doubt there is anything in RDM we could change to fix. This is likely a consequence of Windows Server 2003 being deprecated since July 14, 2015.

Best regards,

Hello,

Thank you for contacting us on that matter!

Out of curiosity, even though you mentioned that you need to use FreeRDP to connect to your old servers, are you able to connect to your Windows Server 2003 using RDM's default RDP engine (RDP (Latest)?

Since this issue only occurs when you connect to your Windows Server 2003, I doubt there is anything in RDM we could change to fix. This is likely a consequence of Windows Server 2003 being deprecated since July 14, 2015.

Best regards,

Dear James,

Yes,I can connect to my Windows Server 2003 using RDM's default RDP engine (RDP (Latest),but there an other issue.It's not friendly DPI with old system.I try all Screen sizing mode and Zoom with 125%,150%,I get the blurry text issues,even the mumber string is fragmentary.The other software like mRemoteNG,ASG RemoteDesktop,RDM with FreeRDP has the clarity text,but RDM with FreeRDP has the annoying dialog,so I believe you can fix it.

Btw,RDM's default RDP engine (RDP (Latest) with 100% zoom is too small to me when I use win11 with 4K resolution and high DPI connect to win2003,and Zoom with 125%,150% the text is blurry.So I have to use RDM with FreeRDP.

Screen dump: My win11 machine with 32 Inch 4K resolution monitor and high DPI connect to win2003 Screen dump 

It is recommended to download the original image and 100% zoom to better see the problem clearly.

https://i.postimg.cc/28hWbBc6/2023-01-17-13-58-00-1.png




Best regards,

Hello,

Thank you for your swift reply!

Unfortunately, since this issue only occurs on Windows Server 2003 and these are no longer supported by Windows, we won't be able to implement a fix.

Sorry for the inconvenience.

Best regards,