[opensuse] vncserver access via putty but not from remote desktop sharing
Hi list, I put this onto a new threat, since I bunged up the previous mail's threat... I am trying to use KDE desktop sharing. However I am unable to login into the remote desktop via http (time out error) or via remote desktop connection (Kwallet asks for a password but does not accept the invitation password). I have enabled Firewall access to ports etc. So what I would need is a how-to to that explains from scratch what other things need to be enabled to run desktop sharing. Also I cannot find the log file for the vnc server (none under /var/log/) - where would that be located and under what name. Oddly I can start vnc manually and tunnel into it via putty/tighvnc. The logfile than is in my home directory. Thanx Herry -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 31 May 2007 18:28, Alexander.Herr@csiro.au wrote:
I am trying to use KDE desktop sharing. However I am unable to login into the remote desktop via http Some additional details [ how you are going to use this in your setup ] would be great... because there are several good ways to do this.
I share several of my systems [ and multiple desktops ] across my network using vncserver, and tightvnc tunnels over ssh, to allow many users access to several (a few) servers via shared desktops. I can provide a point-by-point howto, but the big picture for now is this: First each server machine runs headless. From remote a user can start a vncserver (from their userid home dir) which starts a virtual frame buffer---and starts KDE. [ some of my users start gnome, but that's another story ] Then the user issues a remote background command over an ssh tunnel that starts vncviewer [ running on the server machine ] and then pipes the vncserver back over the X11 ssh session... including password requests etc all compressed and encrypted. This works *very* well for local area nets with adequate speeds, eliminates the need to open a vnc port on the server, and keeps the whole shabang secure. If the desktop needs to be *shared* then the vncserver is started with the option to share. I have used this technique for net-meetings and for collaboration... doesn't work well across the WAN... but for local setups its fine. You can do a similar thing using the vncviewer from the client machine and logging into an open vnc server port on the host... but if you do this its a better idea to change the default server port number to something else---- otherwise, its not a good idea. Directly logging in to a remote desktop isn't such a good idea... also, its not a real good idea to log directly into an open vnc port... or another way to put this is that it is not a good idea to keep a vnc server port open. With the first technique the only port open is ssh. Shipping vnc over ssh is more secure, if not much faster----even compressed. Is this what you have in mind, or something else? -- Kind regards, M Harris <>< -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 31 May 2007 19:01, M Harris wrote:
I am trying to use KDE desktop sharing. However I am unable to login into the remote desktop via http
Some additional details [ how you are going to use this in your setup ] would be great... because there are several good ways to do this. Does this go back to your question earlier about running GLX over ssh?
-- Kind regards, M Harris <>< -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
M Harris wrote:
On Thursday 31 May 2007 18:28, Alexander.Herr@csiro.au wrote:
I am trying to use KDE desktop sharing. However I am unable to login into the remote desktop via http Some additional details [ how you are going to use this in your setup ] would be great... because there are several good ways to do this.
I share several of my systems [ and multiple desktops ] across my network using vncserver, and tightvnc tunnels over ssh, to allow many users access to several (a few) servers via shared desktops.
I can provide a point-by-point howto, but the big picture for now is this:
First each server machine runs headless. From remote a user can start a vncserver (from their userid home dir) which starts a virtual frame buffer---and starts KDE. [ some of my users start gnome, but that's another story ] Then the user issues a remote background command over an ssh tunnel that starts vncviewer [ running on the server machine ] and then pipes the vncserver back over the X11 ssh session... including password requests etc all compressed and encrypted. This works *very* well for local area nets with adequate speeds, eliminates the need to open a vnc port on the server, and keeps the whole shabang secure. If the desktop needs to be *shared* then the vncserver is started with the option to share. I have used this technique for net-meetings and for collaboration... doesn't work well across the WAN... but for local setups its fine. You can do a similar thing using the vncviewer from the client machine and logging into an open vnc server port on the host... but if you do this its a better idea to change the default server port number to something else---- otherwise, its not a good idea.
Directly logging in to a remote desktop isn't such a good idea... also, its not a real good idea to log directly into an open vnc port... or another way to put this is that it is not a good idea to keep a vnc server port open. With the first technique the only port open is ssh. Shipping vnc over ssh is more secure, if not much faster----even compressed.
Is this what you have in mind, or something else?
You might want to consider vncviewer -via hostname hostname:1. This will create a ssh connection to hostname with the same user id you are running from. -- Joseph Loo jloo@acm.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 31 May 2007 19:42, Joseph Loo wrote:
You might want to consider vncviewer -via hostname hostname:1. This will create a ssh connection to hostname with the same user id you are running from. Joseph Loo, thank you very much.
... this is just another example in my life where a paradigm shift was desperately needed! Thanks again! I have been creating my own tunnel and running the vncviewer (serverside) basically piping the X11 protocol back to the client... for so long that I just never really considered doing it any other way... and tightvnc has a *way* better way. So, I snooped out the -via option and the VNC_VIA_CMD environment variable (didn't know they existed until tonight--- again, thank you. So, with the clever trick you just taught me: vncviewer -via hostname hostname:1 (first password prompt is the tunnel [ssh] password) (second password prompt is the vnc server password on hostname) ----the viewer (clientside) establishes the ssh tunnel automatically and then pipes the VNC *protocol* over the tunnel, instead of X11. This is *much* faster of course---again, thank you! The last piece I have to snoop out here is the VNC_ENV_CMD environment variable. Using my old scripts some environment is setup (client side, server side) before and after the tunnel is established and then the vncviewer is called. My client side stuff can be done easily enough before I start the viewer with -via , and I think I can modify the VNC_ENV_CMD variable to accomplish the same thing I was doing with a script serverside... and if so, then whalla Mr Loo--- you have improved my connection efficiency and speed--- again, thank you thank you! -- Kind regards, M Harris <>< -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (3)
-
Alexander.Herr＠csiro.au -
Joseph Loo -
M Harris