CTRL+C doesn't work. Shortcut refreshes connection

Hi,

This sound like an issue I haven't heard of in quite a while were RDP sessions were disconnecting (and then reconnecting) when doing clipboard interaction.

What is your version of RDM?

What is the configured RDP engine of your session? This settings can be set globally in the Preferences (Session Type -> RDP -> General -> RDP Engine) and can be overriden on a per session basis in their configurations (RDP (Microsoft Remote Desktop -> General -> RDP Engine).

Best regards,

What is your version of RDM?
2019.1.9.0
What is the configured RDP engine of your session? This settings can be set globally in the Preferences (Session Type -> RDP -> General -> RDP Engine) and can be overriden on a per session basis in their configurations (RDP (Microsoft Remote Desktop -> General -> RDP Engine).
It is Modern. (in Dutch Moderne)

I just switched the setting to "Verouderd" and reconnected and it looks like the problem is solved.

Hi,

This surprises me, I would actually have expected the opposite. What's the OS version of the servers you are connecting to?

Best regards,

Windows Server 2012 R2.

I have the same issue. Can't copy anything at the moment.

OS version of the servers I'm connecting to is Windows Server 2012 R2
Remote-Machine MacBook with Catalina 10.15.2
I'm using the free version release 2019.2.2.0

The solution above doesn't work for me.
Any help appreciated.

Best regards,

Thomas

Solved.
A reconnect wasn't enough. I had to disconnect, shutdown and reconnect the remote session
Now it works.

Hi,

I was about to suggest something of the sort. I'm glad you could resolve your issue.

Best regards,

This is an issue for me on a fairly regular basis as well. It seems to happen 2 or 3 times a week. It's an issue for me with both Windows Server 2012 R2 and Server 2016. I've only ever been able to solve it by logging off the remote machine, not just disconnecting.

It happened just a few minutes ago so I decided to do some Googling. I came across this article where they suggest restarting rdpclip.exe on the remote machine. But since I found that after I had already logged off and back on, I haven't actually had the opportunity to test to see if that will solve the issue when I run into. I guess I won't know till it happens again.

If that does solve it (it's a workaround, not a solution), I guess that would mean it's an issue with Windows and not RDM. If that's the case, I wonder if something could be implemented in RDM to detect that behavior and automatically issue the command.


MacOS Catalina 10.15.1
Remote Desktop Manager Free 2019.2.2.0
RDP Engine: Modern

Hi,

This is interesting. Please, do tell us of the result when it occurs again. It is something that we have struggled to reproduce.

As for detecting the behavior, I do not know if this will be possible in an unobtrusive way, as, in the pespective of FreeRDP, the session seems to be "working as expected". This would need some investigation.

Best regards,