Just updated my RDM for Mac and am now unable to connect to Windows computers. Attempts to connect and then quits as if the resource isn't there but have confirmed it is there.
Rolled back to the previous version (2025.2.12.6) and am now able to connect.
Hello
Can you enable session logging as described here, reproduce the issue and then send me the log file by PM?
Based on the version that you rolled back to, I guess this is related to TLS. Is the problem when connecting to older Windows Server versions (e.g. Windows 2008 or 2012)?
Thanks and kind regards,
Richard Markievicz
Hello,
This occured on my daily driver so I will try to get time and setup a second system/VM to reproduce and submit the log. These were Windows Server 2019.
Thank you,
Rob
Hello Rob
Thanks for the log files, I was wrong this is not TLS related. Actually the error is LOGON_FAILURE which is normally caused by bad credentials. However what's really weird, is that it seems we are getting empty credentials inside the RDP session (i.e. passed in from RDM).
Is that expected on your side? If you have the RDP session without any credentials configured, you should get a popup asking for them. If you proceed with empty credentials - well, in that case if the server doesn't require NLA I'd expect us to arrive at the WinLogon screen. Historically RDM would try to negotiate an older security protocol if NLA failed but I don't see that happening here, which might show up as a regression on your side.
Can you tell me the expectation / how it worked before? Are you specifying credentials in RDM, or are you expecting to enter your credentials inside Windows? Do you see the popup asking for credentials?
Thanks and kind regards,
Richard Markievicz
I sometimes have saved credentials and other times I have it prompt me. I thought maybe something was up with my saved credentials so when I first got the error, I removed my credentials to get it to prompt but it was the same result. Just closes the connection.
Hello
I'm pretty sure there's a regression with the credential prompt in this version. But I can't recreate an issue with saved credentials. Would you mind restoring the saved credentials and produce another session log that I can look at?
Thanks and kind regards,
Richard Markievicz
Hello
An update has been released that should address this (2025.3.8.5). Let us know if you still have a problem after updating.
Thanks and kind regards,
Richard Markievicz
Looks good! Confirmed update is working on both a VM and my daily. Thank you!!!!