Version: (using KDE KDE 3.3.2) Installed from: Mandrake RPMs OS: Linux KRFB allows only one concurrent connection. So, if one person is connected, a second attempt to connect will be rejected. One might ask, why two people should collaborate on one remote VNC desktop, but sometimes it is very useful. Another case is when someone has a dynamic IP address (whether it's the KRFB server or VNC client): when this IP changes, and KRFB still thinks the client is connected (because network connections were not closed properly and still exist), so it won't allow a second connection - which means people with dynamic IPs often have trouble reconnecting to KRFB. VINO VNC server from Gnome allows multiple connections.
I removed that feature away because its relatively difficult to do with krfb's implementation. Connections are accepted by kded/kinetd, which then starts krfb. It's easy to pass a TCP connection when you start a process (just fork and take it over in the new process), but there is no easy and portable way in Unix to pass a TCP connection to a running process.
*** Bug 143060 has been marked as a duplicate of this bug. ***
This actually *almost* works in current krfb trunk. I can connect multiple times, but the server shuts down when one connection disconnects, forcing all the others to as well. Also, the notification item tooltip, which lists who is currently connected, only displays the most recent connection. The good news is, I reckon it won't take more than a few small adjustments to the code to make this work properly :).
Upping the priority so I remember to fix this one soon.
This should be working in trunk now. I haven't tested it though.
Does not work for me... ever connection disconnect the previous. kde-base/krfb-4.9.3