Difference between revisions of "Talk:WebVNC"
Spatialguru (talk | contribs) |
(→Chicken and egg: new section) |
||
(One intermediate revision by one other user not shown) | |||
Line 2: | Line 2: | ||
---------------- | ---------------- | ||
− | + | ||
+ | We should probably show what config files need edited for sharing the desktop WITHOUT logging into HDA. For example, I use a headless HDA install and didn't need the desktop until adding a second hard drive. In this case, I needed VNC installed and running but couldn't do so without connecting a monitor which defeats the purpose of VNC for me...having the 'enable sharing' portion done in config files with text editors would be much better for those of us running headless. [[User:Devnet|- Devnet]] 17:08, 8 May 2010 (UTC) | ||
+ | |||
+ | == Chicken and egg == | ||
+ | |||
+ | I believe that this app requires the user to authorize the remote connection on the desktop ... which means the user has to be logged in (console/monitor) OR VNC ... '''first'''. | ||
+ | |||
+ | That confuses most people, because of the VNC name to the app. Typically VNC and NX require one session (which in the case of NX can be started at the moment the first request comes in), but no authorization. | ||
+ | |||
+ | If we could make it that the authorization would be on by default, it may help! |
Latest revision as of 22:42, 8 May 2010
Leave your comments, questions or ideas here. There is more to come on this package in the future, including allowing users to run multiple VNC sessions (e.g. one for each user) and to specify which to connect to through this client. Also, I hope to implement SSH tunneling as an option.
We should probably show what config files need edited for sharing the desktop WITHOUT logging into HDA. For example, I use a headless HDA install and didn't need the desktop until adding a second hard drive. In this case, I needed VNC installed and running but couldn't do so without connecting a monitor which defeats the purpose of VNC for me...having the 'enable sharing' portion done in config files with text editors would be much better for those of us running headless. - Devnet 17:08, 8 May 2010 (UTC)
Chicken and egg
I believe that this app requires the user to authorize the remote connection on the desktop ... which means the user has to be logged in (console/monitor) OR VNC ... first.
That confuses most people, because of the VNC name to the app. Typically VNC and NX require one session (which in the case of NX can be started at the moment the first request comes in), but no authorization.
If we could make it that the authorization would be on by default, it may help!