SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
if your talking about remote desktop connection to a windows xp professional machine, then download rdesktop, which is just like the windows remote desktop connection.
If you want to tunnel your X window through ssh, then "ssh -X -l username subdomain.domain.com
The problem seems to be in your PATH, but I seem to remember that building Xvnc was a separate step from the rest of the install.
Here is the README, if it didn't come with you package:
TightVNC 1.2.9 Source Distribution for Unix platforms
TightVNC is Copyright (C) 2001-2003 Constantin Kaplinsky. All Rights Reserved.
VNC is Copyright (C) 1999 AT&T Laboratories Cambridge. All Rights Reserved.
This software is distributed under the GNU General Public Licence as published
by the Free Software Foundation. See the file LICENCE.TXT for the conditions
under which this software is made available. VNC also contains code from other
sources. See the Acknowledgements section below, and the individual files for
details of the conditions under which they are made available.
There are five programs here:
vncviewer - this is the VNC viewer, or client, program for X.
vncserver - this is a wrapper script which makes starting an X VNC
server (i.e. desktop) more convenient. It is written in
Perl, so to use the script you need that.
vncpasswd - this program allows you to change the password used to
access your X VNC desktops. The vncserver script uses
this program when you first start a VNC server.
vncconnect - this program tells a running instance of Xvnc to connect
to a listening VNC viewer (normally the connection is made
the other way round i.e. the viewer connects to Xvnc).
Xvnc - this is the X VNC server - it is both an X server and a VNC
server. You normally use the vncserver script to start Xvnc.
First you must have a reasonably recent version of X installed (this includes
/usr/openwin on Solaris machines). Also, TightVNC requires JPEG and zlib
libraries installed in the system (e.g. under /usr/local). To build
everything but Xvnc, do:
% make World
This should build first the vncauth library which is used by each of the
programs, then vncviewer, vncpasswd and vncconnect.
Xvnc differs from the other programs in that it is built inside a cut-down
version of the X build tree. This is based around the XFree86 3.3.2 "server
only" distribution, which in turn is based on the X11R6.3 distribution from
the X consortium. To build Xvnc, do:
% cd Xvnc
If you have trouble building Xvnc, see the Xvnc/README file for more details.
If it all builds OK you should copy the programs to some directory which
is in your PATH environment variable, such as /usr/local/bin. Also, it's
handy to install manual pages in a directory where the man utility can find
them. You can use the vncinstall script to do this for you (man path is
% cd ..
% ./vncinstall /usr/local/bin /usr/local/man
If you want to use the Java VNC viewer, you should copy the class files from
the classes directory to some suitable installation directory such as
We recommend that you use the vncserver script to run Xvnc for you. You can
edit the script as appropriate for your site. Things you may need to change
* The location of Perl - if Perl is not installed in /usr/bin you'll need
to edit the "#!/usr/bin/perl" first line of vncserver.
* $vncClasses - this specifies the location of the Java classes for
the VNC viewer applet. The default is /usr/local/vnc/classes.
* Xvnc's font path and color database. If you have an installation of
X which is not in the standard place you may need to add arguments to the
Xvnc command line to set these. These should be appended to the $cmd
variable at the comment "# Add font path and color database...".
Now I can only get vncviewer on other machine to load a new display on my machine.
New 'sKex:1 (tsun)' desktop is sKex:1
Starting applications specified in /home/tsun/.vnc/xstartup
Log file is /home/tsun/.vnc/sKex:1.log
root@test:~$ vncviewer host.dyndns.org:5901
works for me, but not
root@test:~$ vncviewer host.dyndns.org:5900
I want to connect to my CURRENT desktop running on my machine.