Remmina Remote Desktop
Giordano Thibault
I'm using Remmina for connecting to a Windows 7 machine over RDP. One problem is that instead of the wallpaper of remote desktop it displays a black backround. In the RDP preferences the "Wallpaper" flag is set for all quality types of connections (from 'poor' to 'best' ) and wallpaper is not displayed with any connection type. ( Also I tried to set various color types - high color, true color, etc.) What can cause the problem? On Debian it worked OK.
Remmina is a remote desktop client written in GTK+, aiming to be useful for system administrators and travellers, who need to work with lots of remote computers in front of either large monitors or tiny netbooks. Remmina supports multiple network protocols in an integrated and consistent user interface. Currently RDP, VNC, NX, XDMCP and SSH are supported.
Just wanted to record experience here. Have used remmina 1.1.2 for years and had remote sound w/no configuration or special setup. suddenly stopped working from ubuntu clients (windows mstsc clients could still get sound fine). also whenever you'd adjust the sound via ubuntu, it would hang a bit. no updates to os/client.
The answer, for any that come after, is that you have to go to the advanced options and enable sound before connecting to the computer. The advanced options are disabled after the connection is established
Regarding the sound quality: I had to remote into a Win10 machine and I notice the sound is echoey, VERY distorted, and "metallic" sounding using Local audio. I just need a basic notification noise for a task I run occasionally.
You could set the audio output mode to Remote if you wish to use the speakers from the device you are remoting into, but you won't be able to hear them through your Local speakers or headphones. (This might be a good option if you're just trying to play music from a different room and the remote machine's speakers are very good.)
As I am getting ready to implement my home server using Fedora 39 WS, I have run into an issue trying to use Remmina for a desktop session. I have ssh without issue and use it, including Cockpit in a web browser from Linux Mint (main client).
But as this is a headless server and will be located far from other machines (for now it is nearby and I have an HDMI connected) I need to be able to get a desktop session for anything I need to do outside of terminal.
I have followed instructions for getting the gnome-desktop-remote setup as well as all the other settings I could find, but if I try to get into preferences within the Remmina app on Fedora, it just closes.
In terminal, I get the following errors when trying to start the service (indicating I may need a service file?) and in Cockpit it says the xrdp daemon failed to start.
Screenshot from 2024-02-14 08-44-171139419 68.2 KB
I wondered if it was a Wayland issue, but I installed the kde desktop as part of setting up rdp. BUT, do you think I have to actually switch from Wayland desktop to KDE in order for it to work? I thought they had resolved the issues with Wayland.
Certainly! Remmina is a versatile remote desktop client that allows you to connect to other machines over the network. To use Remmina to connect to a Fedora computer using Wayland, follow these steps:
That is why I had asked do I need to switch the desktop to KDE in order to use rdp. I can log in of course. I am currently using the server for this discussion since I have to keep referencing things on it (i.e., screenshots, terminal output etc). But I have never rebooted or logged out since I followed the instructions to install KDE in order to get Remmina working
So far, not sure. Maybe I need to understand all these types of rdp connections. Yet the xrdp daemon seems to be working now. And I confirmed that in Cockpit on LM as it is no longer giving the error message xrdp daemon not running.
I have installed 3 other apps since logging into Gnome Xfce Fedora on server. Thincast did not work. Krdc did not work despite having KDE installed. Finally, no machine worked instantly. Now I will test it using Wayland and see if it fails; if it does, we know that Wayland is the issue.
This is not FOSS and I recall using it years ago on Windows. But since it works, I now have a solution for when it is needed to remote into the headless server sitting downstairs next to my router so it can be connected via ethernet.
Remmina is a remote desktop client written in GTK+, aiming to be useful forsystem administrators and travellers, who need to work with lots of remotecomputers in front of either large monitors or tiny netbooks.
I have been trying to get Remmina working with Endeavor and not having any success. According to what I have found online, you need to setup shares to make it work. However shares is not installed with Endeavor. Has anyone had any luck getting Remmina working with Endeavor and explain how you did it.
I have installed Remmina on both desktop and laptop. Not sure what you mean what kine of server am I running on my desktop. I do have the freerdp server installed. I am not sure but maybe I need to install a VPN Connection. Just not sure as all I can find about Remmina is either for Windows or is just plain outdated or gibberish. I only wish to know the proper way to setup a internet connection for remote access between computers using Remmina.
Since this is my first post to the forum, I should thank the BL implementors. I have enjoyed using BL on some of my older and lesser laptops. Because it is basically Debian (the distribution I am most familiar with), installing it on all my personal Linux systems is the direction I am moving.
It would be very convenient for me to have remote access to the desktop of a BunsenLabs (lithium) system installed in the basement of the building where I live. (That system is a four-core i5, 32GB ram, SSD -- plenty of resources and performance.) Logging in via the greeter (if that is the correct term) and getting the usual openbox desktop would be ideal. That system has more than one ethernet interface, and it is positioned to have direct connections to devices that are not on the main network, which sometimes need configuration by web browser or can stand to be monitored with wireshark.
An ideal response to this posting would be "Your google-fu is weak. You need to read ...", identifying a web-accessible article describing how someone else recently made remote access to the lightdm/openbox combination work. While I am willing to put some effort into problem-solving this, eventually running down and up two flights could be faster.
editing lightdm.conf and restarting lightdm. Years ago, I made this sort of thing work by editing gdm.conf on a Debian system; at the time that config file had many fewer lines and there were only one or two things to change.
describes remmina as a remote desktop (in the general sense, not RDP-specific) _client_. If I needed remote access to the Windows system desktop on the second floor from the BL system in the basement, it might be just the thing. And that might be helpful in some small fraction of the use cases, though none come to mind at the moment. But really I need it in the other direction, and I think I should focus on solving that issue.
As suggested VNC is a viable solution: vncserver on server hosts,
vncviewer on clients. There are many linux implementations, BL also
uses it and has installers ready. You don't get to the 'main' desktop
but to a dedicated virtual one, but that's enough for my needs on
servers I manage.
Restarted lightdm. Ran vncserver. Connect from windows. Get familiar BL greeting. Log in. Desktop is missing status and shortcut key displays normally seen on right side of screen. Right-click does not open a menu. vncserver says:
Remmina is a free and open source remote desktop client for POSIX-based computer operating systems. It supports the Remote Desktop Protocol (RDP), VNC, NX, XDMCP, SPICE, X2Go and SSH protocols and uses FreeRDP as foundation.[4][5]
Remmina is in the package repositories for Debian versions 6 (Squeeze) and later and for Ubuntu versions since 10.04 (Lucid Lynx).[6][7] As of 11.04 (Natty Narwhal), it replaced tsclient as Ubuntu's default remote desktop client.[8][9] The FreeBSD ports/package collection also contains it as a separate port and additional protocol-specific plugin ports.[10]
A remote desktop, according to Wikipedia, is "a software or operating system feature that allows a personal computer's desktop environment to be run remotely on one system (usually a PC, but the concept applies equally to a server), while being displayed on a separate client device."
In other words, a remote desktop is used to access an environment running on another computer. For example, the ManageIQ/Integration tests repository's pull request (PR) testing system exposes a Virtual Network Computing (VNC) connection port so I can remotely view my PRs being tested in real time. Remote desktops are also used to help customers solve computer problems: with the customer's permission, you can establish a VNC or Remote Desktop Protocol (RDP) connection to see or interactively access the computer to troubleshoot or repair the problem.
These connections are made using remote desktop connection software, and there are many options available. I use Remmina because I like its minimal, easy-to-use user interface (UI). It's written in GTK+ and is open source under the GNU GPL license.
Remmina offers several types of connections, including RDP, which is used to connect to Windows-based computers, and VNC, which is used to connect to Linux machines. As you can see in the top-left corner above, Remmina's default setting is RDP.
4a15465005