jkehlet

You are right. I just tested it strange, but it is what it is.

Thank you - you can close the ticket.

Sorry for my belated reply - have been traveling. When I go there, I can set it, but why can I not choose "Default" here in the expectation that it goes to "External"? Or will it then always be external no matter what is set on the individual session?

I got a new MacBook and as I reinstalled it with RDM, all my RDP connections open up in Undocked (RDM's own UI/client) instead of External (Microsoft Remote Desktop).

I could have sworn that I found some central setting that would redirect all Undocked > External a while back. Am I dreaming about that or is there a setting that will redirect all Undocked to External RDP sessions?

Add me to the list - essentially, this is the only way of connecting through an Azure RDS gateway to a WVD.

I'm using RDM on a Mac, but the Microsoft RDP client works exactly the same way. First time, it pops up a browser window asking you to authenticate. I would imagine it's one of these parameters from the signscope parameter:

signscope:s:Full Address,Alternate Full Address,EnableCredSspSupport,GatewayHostname,GatewayUsageMethod,GatewayProfileUsageMethod,GatewayCredentialsSource,PromptCredentialOnce,RemoteApplicationProgram,RemoteApplicationMode,RemoteDesktopName,Authentication Level,AudioMode,RedirectPrinters,RedirectCOMPorts,RedirectSmartCards,RedirectClipboard,DevicesToRedirect,DrivesToRedirect,LoadBalanceInfo

Here's a screen shot of my RDP file with addresses blurred for privacy:

You are right - it has been a while. Mostly because it's been working very well for me so far. Now, admittedly, I'm using it as a launch-pad to Microsoft Remote Desktop Connection as I never got happy with the native RDP engine.

Thanks for the note, please close this out. :-)

I search the forums for this, but couldn't find a bug report, so I'm daring to write this bug report... :-)

When clicking the Close button on macOS, an application is supposed to hide/minimize, not exit/quit completely. Can we please get RDM for macOS fixed so that this is following the macOS guidelines?

In case you are in doubt, I added a screen shot of the Close button as shown below.

/Jesper

Can confirm: I hit Command+, to open Preferences, then close the window -- that act refreshes the connection browser. But editing a connection's properties, then closing out, doesn't refresh the viewer.

I didn't try the connection properties, only the Preferences. I'm glad you can confirm.

Xavier, I found something curious today: I got a black connection browser window, but then I went into Preferences to change something, click OK, and the connection browser now viewed properly.

So something in your Preferences exit-routine is apparently redrawing the connection browser window properly.

Thoughts?

Thank you!

Can you please get rid of the thousand separator in the RDP port number? I know it's numerically OK to have it there, but there is an inconsistency between when you are viewing it and when you are editing it.

And TCP/UDP port numbers are never written with a thousand separator anywhere else - so it would be prudent to not have it in RDM.

/Jesper

Sometimes (about a third of the times or so,) I get a black connection browser. You can have a look at the attached file, although it shows it as transparent in that screen shot.

It started with Mojave when I upgraded.

Now that we are at the open tickets, I checked this one, and v6 has resolved this, too. So you may close this one out, too!

Thanks, Xavier!

Yes, I have not had any problems so far, so I'd say this one has been put to bed! :-)

Also, please download the video so I can remove it from my Dropbox again. The file was too large to attach here (13.4MB)

Have a look at this: https://www.dropbox.com/s/tpl6h7jh3je4ayj/ConnectVideo.mov?dl=0

It is what happens with a number of servers that I try to connect to. It logs on, loses connection, retries etc. Then I get a black screen so I have to retry.

It's so bad that I essentially have to use Microsoft Remote Desktop - RDM won't connect.

/Jesper

Yes!!! :-) I'm glad you were able to reproduce. It's frustrating, so whenever you have a chance is good.

Performance is better now that I'm down to "OpenGL" but obviously looking forward to Metal being fixed.

Sent you the connection separately. I'll mess with the Legacy/Modern settings along with Metal/OpenGL etc. to check performance.

Attached are the pictures you are asking for. The Preferences are only changing from Legacy to Modern, but otherwise stays the same for my connections.

If you want, I can get you a connection to a TEST image that reproduces it?

I can confirm that the Modern Engine is horribly slow performance-wise. I could see it paint the screen, if it painted at all. I had to switch back to Legacy to actually get work done.

So far I haven't seen it with logging turned on - but doesn't the logs eventually grow very large?

Finally, to answer your question: The RDP view doesn't really respond. If I leave the black session for a minute or so, RDM automatically closes the window/destroys it. So it's almost like the handshake doesn't properly happen. There is no items etc., and when I checked the RDP session stuff from a different login/Microsoft RDP Client, I could see that it never opened up the session at all. I hope that helps.

OK, we need to revisit this - it's annoying and we need to troubleshoot. One thing I've noticed is that it doesn't have a user yet, when it happens. If you look at the attached image from one of our servers, I'm logged on (jkehlet) and trying to logon as 'cgadmin'

It doesn't even show on the user list, so the black screen must be a bad handshake in the protocol initiation or something. After a while, RDM just disconnects, almost as if it says "waited long enough for an answer."

What can I do to provide troubleshooting documentation? I would really like to fix this - I'm pulling all my hair out...

Yes. If you have access to a Visual Studio environment, it's actually contained in the standard win32 header files, specifically in ntstatus.h

Here's another link for reference: http://errorco.de/win32/ntstatus-h

https://blogs.technet.microsoft.com/askpfeplat/2013/01/28/quick-reference-troubleshooting-netlogon-error-codes

Oh, yeah, that one. I know it's the right error message (somebody put the wrong DNS address in there, so it couldn't reach the DC,) but let me produce a log to verify. Hang tight...

Where do I find that? I looked at the connection log, but nothing in there...

I had a situation where a Windows Server that I logged onto could not find the domain controller. The error message from RDM was "Failed to connect to the host (-1073741730)."

The error message in hex is 0xC000005E, and when you search that, you get a NETLOGON error message.

When you search the -1073741730, you get nothing.

Thoughts?