stchizen

Thank you for all the help!

O hey! ... with both enabled it worked! (it did not work with both enabled on 4.1.0.0, so it appears a combo of the checking both and the update was the fix)

Do you still want the log?

To be clear, this was due to a recent Windows Update?

I just checked ... went to Remote Desktop Manager -> About. I have 5.2.0.0 with my Enterprise License active. Same problem.

I then deleted the app and re-downloaded 5.2.0.0 enterprise from your site just to be sure. Same problem.

Yep, captured logs and emailed in. I did a log capture with TLS enabled and one without.

Ok, I updated to 5.2.0.0. (interesting that I did "check for updates" earlier when I was on 5.1.0.0 and it said I was up to date.) Either way I was manually able to download 5.2.0.0

No fix.

So I moved on to the article. It had a few things:

•Validate that you have entered the appropriate username, password and domain to establish the connection or select the appropriate Credential Entry

•Validate that no User Specific Settings or Local Machine Specific Settings has been enabled by mistake or with the wrong credential

•If you are using a different username format to connect, select the appropriate one to use in the Advanced - Username Format field

•Enable/Disable the Network Level Authentication (NLA) option in the Connection tab of the RDP session

•Enable/Disable the Transport Layer Security (TLS) option in the Connection tab of the RDP session

I checked, my credentials are correct.

I have no user or machine specific settings mentioned that are applicable.

I am not using a different username format.

I had already tried both enabling and disabling both NLA and TLS in all combination.

Unfortunately none of these have fixed my issue.

I am on 5.1.0.0 on OS X 10.13.4

It works if I use "external" rather than "embedded"

Searching the forums I tried the following:

-Ensure I am using RDP engine 4 (and I tried 5)

-Uncheck the box for TLS

-Checked resolve hostname before attempting to connect

-Changed my connection from using the FQDN to IP

None of the above worked.

I am able to ping the host I'm trying to RDP to fine.

I have Remote Desktop Manger for Windows running in a VM and it connects fine.

O wow, with 3.5.4.2 it is running much better. Curious that when I did "check version" while running 3.5.3.0 it didn't find the new version but it was obviously available on the website.

I will say I have the same problem. I have tried all of the suggestions in this thread and the performance is bad enough that I use the Microsoft RDP client on my mac. I love the product on my windows machine but on the OS X side it's a struggle. Specifically I do quite a bit of work form the command line when i'm RDPed to a machine. I will type into my cmd window in the RDP session and it will draw the characters quite slowly if at all. Sometimes I need to move around my cmd window get it to refresh and show what I have typed.

I am running v. 3.5.3.0 of Remote Desktop Manager

While I can verify the "Server" setting sticks, it's more obnoxious than setting "none" each morning when I launch the application. I'll just do that until there is a fix, thanks for the help.

Ahh, I hadn't closed the application after making the change to the RDP default. I can report the same problem as NHEvs. While making the change solves my problem, when I relaunch the application the change reverts back to "Auto Scale Resolution". I am running 10.0.4.0

Yep, that was it! Thank goodness, that was really obnoxious. I really appreciate the quick response.

After updating to 10.0.4.0 when I connect multiple Embedded (tabbed) RDP sessions I am having disconnects. Every time I swap from RDP session to RDP session it disconnects. It then reconnections the session automatically, but of course all of my application windows within that session have been resized.

Any suggestions?