Version: (using KDE KDE 3.0.9) Installed from: Compiled From Sources Compiler: GCC 3.2 OS: Linux KRdc should allow the user to listen on a port for a reverse VNC connection (server connects to client).
Which clients and servers support this?
Virtually all of them-- usually as vncviewer -listen
Any news for this "60 votes" request? This mode is very useful when assisting people, since connection originates from them and so it can pass firewall and other settings on their side. For instance, for Windows people you can use UltraVNC "single click" and prepare a VNC server that connects to your client, if in "listen mode", passing easily through their router/firewall. If only KRdc could support listen mode...
This could be very useful for remote technical support. I often have to help people out when they are working from home. NAT and Firewalls give me real headaches as you can imagine so being able to set up a small config file ahead of time so that when KRDC is fired up there is an option to connect to a predefined server. Just a thought, but how would the listening "server" handle multiple incoming requests? Could we generate a SessionID? which is displayed on the initiators screen and once that number has been phoned/e-mailed through to tech support the SessionID can be picked off a list and connection established. This would make the job of linking incident reports to remote connections so much easier.
I just voted for this bug since it is a very annoying issue for beginners, who may need help. This bug seems quite old know will it have a chance to be implemented ?
Yes, this feature is planned. I will have a look at libVNCclient if it is already implemented there.
Any news on this one? This feature would really make my life easier as I quite often have to help people over the net (through NATs and Firewalls, of course).
Nope, still nothing available. LibVNCclient, which is the base for KRDC does not support that IIRC. Do you know an open source VNC client, which does support that?
@Urs Wolfer: Tightvnc does this. From the (vncviewer man page): -listen Make the viewer listen on port 5500+display for reverse connections from a server. WinVNC supports reverse connections using the "Add New Client" menu option, or the -connect command line option. Xvnc requires the use of the helper program vncconnect.
@Marco: You need special parameters for tightvnc in order to connect to SingleClick clients. Here's a description of how to use tightvnc to listen for ultravnc's single click connections: http://linux-tipps.blogspot.com/2008/08/ultravnc-single-click-and-linux.html
Well this can't be too hard to implement in libvncclient, can it? All source for this piece of functionality is available: http://www.tightvnc.com/download/1.3.10/tightvnc-1.3.10_unixsrc.tar.gz just needs someone picking the task!
FWIW, it looks like the latest version of libvncclient supports listening for reverse connections (finally).
Any news? 170 votes so far. Remmina does this but I would prefer use krdc of course
Isn't this also reuiring reverse connection in krfb? As of my knowledge krfb also does not yet support reverse connections. Typically VNC clients listen on port 5500 to allow a reverse connection. This is very useful if the server is behind NAT (mostly the case for desktop clients). I am personally using UltraVNC based solution very successful to support Windows systems. It offers reverse connection on server side. I am running a "repeater" component on a public internet host with public IP address which is allowing me then to connect from ma viewer to the repeater (typically port 5900) as well as the server connecting to the repeater (typically port 5500) to allow relayed connection even if both parties are behind NAT.
(In reply to rainer.meier from comment #14) > Isn't this also reuiring reverse connection in krfb? The nice thing about standards is that there are multiple implementations. No, it doesn't require krfb to support it, since there are other VNC servers that do.
(In reply to Luke-Jr from comment #15) > The nice thing about standards is that there are multiple implementations. > No, it doesn't require krfb to support it, since there are other VNC servers > that do. Good point. But the number of VNC servers supporting wayland sessions is pretty much limited too.
(In reply to rainer.meier from comment #16) > Good point. But the number of VNC servers supporting wayland sessions is > pretty much limited too. Thankfully, VNC is also not limited to Wayland.
(In reply to Luke-Jr from comment #15) > Thankfully, VNC is also not limited to Wayland. I see your point. So perhaps I have to elaborate that my (yes my personal) use case is to support friends and family with almost zero computer knowledge. They might run a wayland-only desktop and ask for remote support. This is why I was looking for a VNC serverr supporting waland and found krfb to be the promising but without reverse connection it's questionable if this can support this use case if developers don't see a benefit. I might just have to do some more research about alternative options then. What I need is an RFB server allowing reverse connection with either simple GUI or simple command-line which even my grandma would be able to launch. So thanks for your reply. Krfb/krdc might just not be the right tool for the job.