What to do if the clipboard does not work for RDP clients

This is not to say that RDP is such a common phenomenon. Nevertheless, in a semi-professional and professional computer environment, it is not at all rare, therefore, for a start, it does not prevent us from clarifying what it is.

Everything is very simple. Microsoft at one time bought a communication program that was later renamed the familiar NetMeeting and took the remote desktop protocol from it, this is the RDP Remote Desktop Protocol.

The protocol today is widely used by client programs for remote work with the server. There are only ten client programs in the top, remmina, which has a graphical interface, is only one of them.

The popularity of remmina is caused by the popularity of Linux - on Ubuntu, this client is installed by default.

Among the possibilities of remote access clients:

  • encryption of transmitted data;
  • audio transmission with the ability to play on a local PC;
  • use mapping - run local programs on the server;
  • use of resources on the server from a local PC.

On Windows, the client works as an executable mstsc.exe (TSC - Terminal Services Client - the official name of this program). Developed client versions for all operating systems.

Among the opportunities of RDP-clients and one that can fail from time to time - the exchange of information through the clipboard.

The first solution

The problem, when the exchange through the buffer between the client and the server is violated, is ubiquitous, with any operating systems on both sides. And the fact that you often have to deal with Linux on the client and Windows on the server is determined simply by the popularity of these systems.

ATTENTION. Please note that the previous version of remmina for Ubuntu had some rather unpleasant internal errors that cannot be fixed by the user with the usual settings. Now they are eliminated, and the new version of remmina is waiting for its fans to download.

This error has one peculiarity - if you currently have several servers connected, it can appear when exchanging with only one, the others use the clipboard without any problems.

The first solution that suggests itself from the very beginning is to terminate the current failed RDP session and start it again. It works at 100%. But the disadvantage of this approach is obvious - you have to close all programs on the server, exit, and then, after restarting, run all programs again.

But there is another solution to the problem, not so cumbersome.

The second solution

Another option is to restart only the program that is responsible for the buffer exchange — this program is behind the rdpclip.exe executable module, it is external to remmina itself and is indicated by a separate line in the task manager.

Thus, to restore the exchange between the RDP client and the server through the clipboard, you need to enter the Task Manager, go to the tab of the running processes, find under your rdpclip.exe account that is responsible for the failed exchange, complete it and start it again, manually .

Completing the rdpclip.exe process

Perhaps it's in the settings

But before dropping processes in the Dispatcher, it doesn’t bother to make sure that the RDP client itself is configured correctly - remmina.

Thus, we go into the client settings and:

  • On the Local Resources tab, in the Local devices and resources group, we select resources that we are going to use in the current remote session — we are interested in the Clipboard resource.

Next you need to check the server settings:

  • On the Client Settings tab of the “RDP-Tcp Connections” parameters in the Redirection switch group there is a mode that prohibits clipboard redirection (simply called the Clipboard). It should be reset, although this is its default state.

In other words, first make sure that your RDP client meets the requirements of the client system (at least according to the version), and then carry out the proposed actions, starting with the settings, by itself.