RDP to windows server on a Mac
So, on a Mac and I cannot RDP to unless I enable the legacy engine. If I leave it as default, then I always get the message: ERRCONNECT_CONNECT_TRANSPORT_FAILED (0x0000000D)
and it disconnects.
I should point out that if I connect to console, the modern engine is fine, but i dont want to connect to console and need more than one person to connect anyway....
The legacy engine also seems goofy and unstable, it likes to crash regularly (once or twice a day). I don't get this when connected with the modern engine via console, so I have to think thats part of the reason its being replaced.
I've tried changing the rendering from metal to opengl and core, but that doesnt change this behavior.
Anyone have any ideas?
All Comments (4)
I think we are in contact with each other by email? Regardless, could you provide a session log of an RDP session that fails with the Legacy engine disabled?
Here are the instruction for this: https://docs.devolutions.net/kb/remote-desktop-manager/how-to-articles/macos-rdm/rdm-mac-enable-send-rdp-logs/?q=session+logs?q=session+logs
Best regards,
Xavier Fortin
Hello
Further to what Xavier wrote, can you also confirm what version of RDM Mac you are running? The fact that you can connect to the console session indicates an issue with the RDP licensing module. There was a significant regression in this area recently but it should have been fixed in the most recent versions of RDM Mac (2023.1.11.x, IIRC).
If you're on the latest version and experiencing this issue, the session logs of a failed connection with the modern engine will be important.
Thanks and kind regards
Richard Markievicz
I worked some with Xavier, the newest version does seem to remove my need for legacy mode, which is great. I'm running on 2023.1.11.1 and not having those problems connecting any longer. So far no instability, crossing my fingers :)
Glad to hear it!
Do not hesitate if you find any other issues.
Best regards,
Xavier Fortin