Quote:
Originally Posted by Mario Blunk
So tightvnc does not allow sharing the SAME desktop ?
|
Under Linux, i dont think so. Under Windows it does only that.
Quote:
Originally Posted by Mario Blunk
Hi, yes the word "localhost" appears strange to me but however, I see the customers linux desktop. Before starting vncviewer I prepare the connection by
ssh -L 5901:192.168.7.3:5901 customers_user_name@customers_router_ip
afterwards I run
vncviewer -shared -encodings Zlib -compresslevel 5 localhost:5901
which does the actual desktop connection to the customers desktop.
|
Well you should have said that you use ssh tunneling. So probably the customer has Linux running.
Under Linux VNC solutions tend to behave by default more like a terminal services (remote desktop) server under Windows - ie providing a new session.
You need a VNC solution that actually shares the active session.
For example Gnome DE has a built in VNC server named vino-server that can be activated easily.
One of the established and working solutions on Linux which is DE-agnostic is x11vnc. This runs really well on anything (there are some permission related tricks in some circumstances, but that depends on the used DE).
I use it and its great. I use it with ssh tunneling too, but i use it in reverse VNC mode - this means that the server does the connection towards the viewer.
My script launches the viewer (i use ssvncviewer, but you can use anything) in listening mode on my end, sets up the port forwardings and launches x11vnc on the target computer with the reverse connection option.