Embedded mode not working on specific server, v 2025.1.13.3
Hello
I've seen some older threads on this but I wanted to check whats going on with current version.
I have one specific server where I cant connect using the embedded mode, but external works. With embedded I get the error
ERRCONNECT_CONNECT_TRANSPORT_FAILED (0x0000000D)
Since this seems to be isolated to a specifik server Im guessing I need to check in with the admins of that server, any pointers on what to look for?
All Comments (4)
Hello
Yes there have been a couple of cases like this; it could be server side, it could be an issue in RDM or it could be related to the Mac or network configuration itself,
What version of macOS do you have?
At a first step, I'd recommend generating a session log and send it to us. RDM Mac will sometimes try to make a reconnection after a failure in certain cases and when it does that, it can mask the "real" error. So let's start by validating that the problem is what we think it is.
Instructions for the session log are here. Once you have it, please send it either to me by PM or to service@devolutions.net (mentioning this forum thread).
And let me know if you have some questions or something isn't clear
Kind regards,
Richard Markievicz
Hello
Yes there have been a couple of cases like this; it could be server side, it could be an issue in RDM or it could be related to the Mac or network configuration itself,
What version of macOS do you have?
At a first step, I'd recommend generating a session log and send it to us. RDM Mac will sometimes try to make a reconnection after a failure in certain cases and when it does that, it can mask the "real" error. So let's start by validating that the problem is what we think it is.
Instructions for the session log are here. Once you have it, please send it either to me by PM or to service@devolutions.net (mentioning this forum thread).
And let me know if you have some questions or something isn't clear
Kind regards,
Hey
Thanks!
I saved a session log and had a look myself and noticed it seemed to be some issue with a license file in the .freerdp folder in /Users/user/Documents. I deleted the .freerdp folder and now Im able to connect. Had some onedrive sync issues previously so might have been that messing it up.
Thanks again for the quick response!
All the best
Hello
Ah! Good catch. Thanks for the update. I assume you're connecting over an RD Gateway?
If the Gateway wants to reissue a client access license (CAL), the new CAL is sent to the client where it's cached on disk. If there's an existing CAL, it needs to be overwritten.
This is interesting to me because another user reported exactly the same issue a week or two ago. Ultimately all we're doing is replacing a file, so it's hard to see why that would fail. I gave the user the same workaround you used - delete the old CAL from disk and then connect again, and it worked.
But since this is the second case in just a matter of a couple of weeks (CALs expire over a period of a few months, they're fairly long-lived), I wonder if we have a regression on our side (in the first case I guessed it was just damaged or corrupt file permissions). All that to say - if you notice this happening again, please do post back and let us know since it would indicate that this needs further investigation.
As always, don't hesitate to post back with future questions or comments.
Kind regards,
Richard Markievicz
Yes, its a jump host running Windows Server 2022.
Will sure do!