Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have two PCs on the same LAN, both Debian 12 with KDE. I installed Krfb on one and Krdc on the other.
When I try to connect from the client, Krdc to the server Krfb, I get the popup on the server asking for permission to allow the connection. I confirm, and the client comes up again with the popup to enter the password, stating that "authentication failed". I tried Remmina as a client and same issue happen.
The two PCs don't have a firewall set up or any other security running. Running nmap against the server confirms that port 5900, the default for Krfb is listening. It should be a straightforward connection. The internet doesn't have much at all on something like this. Any ideas?
Oh yes, I definitely used the exact password that Krfb generated, many times. Eventually I started experimenting with changing it but still no luck.
It's such a weird thing. Krdc sees the server right away when I start it, Krfb responds right away when I enter the password in Krdc, but then the connection just doesn't happen.
I don't use Debian, and instead use tigervnc. Install that from the repo, something like apt get tigergvnc on both systems. You might also like to install a light windows manager, apt get jwm perhaps.
On one, run vncserver :1
that will prompt for a password that must be at least 6 characters, that has to be entered twice.
Immediately thereafter kill that
vncserver -kill :1
and edit the newly created ~/.vnc folders xstartup to change the last line from twm to jwm (or whatever window manager).
Restart vncserver, but with no security
vncserver :1 -SecurityTypes none
On the same box, connect to that. vnc adds 5900 to whatever Display number you allocated, so 5901 in this case
vncviewer localhost:5901
and it should drop straight into a jwm windows desktop
From the other box I more usually set up a ssh tunnel
ssh -f -N -L 5900:localhost:5901 <ip of server>
and then run
vncviewer localhost
Going through the above might help to identify where the problem lay with your current setup/choice.
Just an update if anyone else has the same problem. I got it to work, partially...
After following the instructions at https://wiki.debian.org/PipeWire I can finally use Krdc to vnc into the Krfb server. The problem is that the display of the remote server is garbled and can't be used.
I then used Remmina as a client and the display works perfectly. The mouse works, but the keyboard doesn't work. It's a KDE bug according to this post: https://bugs.kde.org/show_bug.cgi?id=435338
Until Krfb is fixed, I'm experimenting with x11vnc.
EDIT: I just installed Gnome and removed KDE on the server. Gnome works fine with x11vnc and now I can remote without a single issue.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.