Re: Question about TightVNC: how can the remote and the local share the same screen?
From: Rod Smith (rodsmith_at_nessus.rodsbooks.com)
Date: 07/17/04
- Next message: Scott Lurndal: "Re: Stupid question: why "find" command does not work?"
- Previous message: Bats: "Re: KDE and GNOME, which one is better?"
- In reply to: gino: "Question about TightVNC: how can the remote and the local share the same screen?"
- Next in thread: Kill Bill: "Re: Question about TightVNC: how can the remote and the local share the same screen?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sat, 17 Jul 2004 18:40:30 -0000
In article <cd972s$6na$1@news.stanford.edu>,
"gino" <mizhael@yahoo.com> writes:
>
> Ok, I downloaded and installed TightVNC, and now it assigned me a display
> number which is
>
> xxx.xxx.xxx.xxx : 1
>
> and my home PC connected to that Linux box without any problem, but it opens
> a new window session, which was not the one I left at the workplace
> yesterday when I left.
>
> I want to continue to work on the stuff I have not finished yesterday at my
> workplace,
>
> how do I do that? (That's the purpose of my using VNC)... How do my remote
> session and local Linux workplace share the same screen?
The standard VNC (RealVNC and TightVNC) servers for Linux won't do this.
AFAIK, the only way to do this in Linux is to use KDE's desktop sharing
tool. I *THINK* this will work even if you don't use the full KDE, but
you'll need to launch the KDE Control Center (type "kcontrol" in an xterm
if you're not running KDE). Select the "Internet & Network -> Desktop
Sharing" item, then either send yourself an "invitation" (a short-term
password to use the system) or configure "uninvited connections." The
last I checked, though, KDE popped up a confirmation dialog box before
allowing a connection. If it still does this and doesn't provide a
workaround, you won't be able to enable remote control unless somebody is
using the system locally.
Chances are you're better off just closing your applications when you
leave work, connecting using a standard VNC server, and restarting the
applications remotely. That'll cost you a minute or two, but at least
it'll work reasonably well without undue hassle to configure.
-- Rod Smith, rodsmith@rodsbooks.com http://www.rodsbooks.com Author of books on Linux, FreeBSD, and networking
- Next message: Scott Lurndal: "Re: Stupid question: why "find" command does not work?"
- Previous message: Bats: "Re: KDE and GNOME, which one is better?"
- In reply to: gino: "Question about TightVNC: how can the remote and the local share the same screen?"
- Next in thread: Kill Bill: "Re: Question about TightVNC: how can the remote and the local share the same screen?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
