I saw a thread on this not too long ago, and just revisited it, but I am still a little confused. I am hoping to access my Linux machine at work and have access to the existing KDE environment as I left it. I telecommute part of the week and often need to access something exactly as I left it. When I run the vncserver command on the remote machine (in this case the one at my office): ~> vncserver :0 I get A VNC server is already running as :0 However, If I try to use the vncviewer from my machine at home: ~> vncviewer 10.xxx.xx.xxx:0 I get vncviewer: ConnectToTcpAddr: connect: Connection refused Unable to connect to VNC server If however I use: ~>vncviewer 10.xxx.xx.xxx:1 I get a viewer window consisting of an xdisplay with a xterm window open. What am I missing? How can I use the environment just like I left it? TIA, Darrell
Darrell Cormier wrote:
I saw a thread on this not too long ago, and just revisited it, but I am still a little confused. I am hoping to access my Linux machine at work and have access to the existing KDE environment as I left it. I telecommute part of the week and often need to access something exactly as I left it. When I run the vncserver command on the remote machine (in this case the one at my office):
~> vncserver :0 I get A VNC server is already running as :0
However, If I try to use the vncviewer from my machine at home:
~> vncviewer 10.xxx.xx.xxx:0 I get vncviewer: ConnectToTcpAddr: connect: Connection refused Unable to connect to VNC server
If however I use: ~>vncviewer 10.xxx.xx.xxx:1
I get a viewer window consisting of an xdisplay with a xterm window open. What am I missing? How can I use the environment just like I left it?
TIA, Darrell
Sorry, I forgot to mention that I am using SuSE 8.2 Pro in both locations. D.C.
The answer is really quite simple, I don´t know which version of KDE are you running but anyway. I can tell as far as my expirence tell me that you are using an old version of VNC so the easiest way to do what you want to do is to upgrade your kde version to 3.1 or 3.1.4 because in that versions inside the Control Center there is the possibility to configure desktop sharing through the gui, Plus the Fact that the VNC version that is in that KDE is master and more stable than the original VNC thzt you Stara through the console. Any doubts ask me again. Saludos Marco Antonio Sánchez Jullian Help Desk Impulse Telecommunications de México 441-1300 x 1042 msanchez@impulse-telecom.com _______________________________________ "The only way around is through." Robert Frost -----Mensaje original----- De: Darrell Cormier [mailto:linuxdev@sptc.net] Enviado el: Jueves, 20 de Noviembre de 2003 01:08 p.m. Para: SuSE-Linux Asunto: Re: [SLE] Desktop Sharing with VNC Darrell Cormier wrote:
I saw a thread on this not too long ago, and just revisited it, but I am still a little confused. I am hoping to access my Linux machine at work and have access to the existing KDE environment as I left it. I telecommute part of the week and often need to access something exactly as I left it. When I run the vncserver command on the remote machine (in this case the one at my office):
~> vncserver :0 I get A VNC server is already running as :0
However, If I try to use the vncviewer from my machine at home:
~> vncviewer 10.xxx.xx.xxx:0 I get vncviewer: ConnectToTcpAddr: connect: Connection refused Unable to connect to VNC server
If however I use: ~>vncviewer 10.xxx.xx.xxx:1
I get a viewer window consisting of an xdisplay with a xterm window open. What am I missing? How can I use the environment just like I left it?
TIA, Darrell
Sorry, I forgot to mention that I am using SuSE 8.2 Pro in both locations. D.C. -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Darrell Cormier wrote:
I saw a thread on this not too long ago, and just revisited it, but I am still a little confused. same here
I get A VNC server is already running as :0 I thought someone had posted the procedure. Were you reading http://lists.suse.com/archive/suse-linux-e/2003-Oct/2823.html and the answers?
After some tinkering I got xf4vnc to work for me on SuSE 8.0 with results here http://lists.suse.com/archive/suse-linux-e/2003-Nov/0471.html Damon Register
Damon Register wrote:
Darrell Cormier wrote:
I saw a thread on this not too long ago, and just revisited it, but I am still a little confused.
<snip>
I thought someone had posted the procedure. Were you reading http://lists.suse.com/archive/suse-linux-e/2003-Oct/2823.html and the answers?
<snip> Damon Register
Thanks, this was the thread I was reading but I missed a few. I have tried several of the possibilities but am still not satisfied. Using the Control Center ---> Internet ----> Tools ----> Desktop Sharing on the office machine and then trying the Remote Desktop Connection on my home machine, I get a connection, but the screen never comes in. I get a black screen with several white blocks randomly placed on the screen in rows. But the actual screen never comes in. I can see about half of the panel at the bottom of the screen, but nothing else. Even to get this far it is painfully slow (I am on a 300+K DSL connection). Anyone have any ideas on what is happening here? D.C.
On Thursday 20 November 2003 4:28 pm, Darrell Cormier wrote:
the panel at the bottom of the screen, but nothing else. Even to get this far it is painfully slow (I am on a 300+K DSL connection). Anyone have any ideas on what is happening here?
I use vnc a LOT and really count on it. I use the tightVNC. I would suggest download tight vnc, compile it and install it. The run vncserver :5 (or whatever) to start a simple vncserver session and make sure you can access that simple configuration from home. I assume you are not really attempting to access the vnc session directly over the internet without forming an ssh session or some other encryption method into play first. Keep in mind vncviewer does have an option for ssh tunneling. Have you verified the vncserver is working on the local LAN? Can you access the vnc session from another box? Greg Engel
Greg Engel wrote:
On Thursday 20 November 2003 4:28 pm, Darrell Cormier wrote:
the panel at the bottom of the screen, but nothing else. Even to get this far it is painfully slow (I am on a 300+K DSL connection). Anyone have any ideas on what is happening here?
I use vnc a LOT and really count on it. I use the tightVNC. I would suggest download tight vnc, compile it and install it.
The run vncserver :5 (or whatever) to start a simple vncserver session and make sure you can access that simple configuration from home.
I assume you are not really attempting to access the vnc session directly over the internet without forming an ssh session or some other encryption method into play first.
Keep in mind vncviewer does have an option for ssh tunneling.
Have you verified the vncserver is working on the local LAN? Can you access the vnc session from another box?
Greg Engel
I finally got this working. I was trying too many different approaches at once and getting nowhere. I finally did the following: 1. (KDE) Control Center ---> Internet & Network ---> Desktop Sharing 2. Checked "Allow uninvited connections" and "Allow uninvited connections to control the desktop" 3. Provided a good password 4. Connected to the remote machine via ssh and forwarding ports: ssh -C -X -L 5905:remote_ip:5900 remote_user@remotehost ## This allows for a secure/encrypted connection and makes the remote ## VNC server look as if it were running on the local machine 5. Start the vncviewer for the localhost port supplied above: vncviewer localhost:5 6. You will then be prompted for the password that was set in step 3. This works wonderfully. I have not tried tightVNC, but I plan to do that in the near future to see if it enhances this experience at all. I had seen in the archives where one person (Damian O'Hara) was able to get this working using rdesktop. I could not get that to work. I would continually get this result: ~>rdesktop -g 1600x1200 -f -p - localhost:5 ERROR: connect: Connection refused I will research it further as well and if I get it working I will post my results. Thanks for all the input, Darrell Cormier
participants (4)
-
Damon Register
-
Darrell Cormier
-
Greg Engel
-
Marco Antonio Sánchez Jullian