Mr. Know-It-All has the answers to even the really tough questions.
Jerry Rash's VNC presentation at the December SCOUG meeting was really interesting,
but some reason I can not recall all the details on how to set it up.
How about an install cookbook?
OK. How's this?
Download the software
This is part that runs on the system to be controlled.
This is part that runs on the system that will do the controlling.
Install the server
Install the Server on each system that you may want to control remotely.
Create a directory to hold the server.
Unzip the contents of pmvnc-1.02-bin.zip, preserving directories.
install.cmd, the install program.
This will create several desktop objects.
These objects all run the same program, but the parameters differ for each object.
Configure the Server
Click on PM VNC Server object to start the server.
The server must be started before you can use any of the other objects.
The first time you start the server, the Settings notebook will display automatically.
For now, all you need to do is select a password.
Leave the other settings at their default values.
Install the viewer
Install the viewer client on each system that will be used to control another system.
Create a directory to hold the viewer code.
Unzip the contents of pmvnc100.zip to this directory and the client is ready to run.
You might want to create Desktop objects for vncview.exe and vncview_e.txt.
Test the Installations
While you can install both the viewer and the server and the same system,
you can only control a system from another system.
Start the server on the system to be controlled.
Start the viewer on a different system.
Enter the hostname:display parameters.
The hostname will be the value defined by HOSTNAME in config.sys.
The display number will be 0 on eCS/OS2 system.
Leave the options blank for now and click OK.
Select a password when prompted.
If all goes well, the remote host's desktop will appear.
To adjust the connection, disconnect from the remote host or shut down the viewer,
click on the control menu button to access the menu.
To shut down the VNC server, click the PM VNC Server Kill object
Tuning your setup
If you contact the same system often, you can create a Desktop object
which will connect with minimal prompting. See The client readme (vncview_e.txt) for
the command line options accepted by the viewer.
There are lots of tuning options for special situations.
If you have questions, you can ask
directly. You can also get help from the nice folks on the
SCOUG-Help mailing list.
Jerry said that VNC alone is not a secure connection?
What's the solution?
The short answer is you can use ssh or stunnel.
I'm out of time for now, so ask me later and I'll explain the setup details.
Curious or in doubt, you can ask
OS/2 is his specialty and sharing solutions is his passion
Mr. Know-It-All lives in Southern California.
The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA
Copyright 2006 the Southern California OS/2 User Group. ALL RIGHTS
SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group.
OS/2, Workplace Shell, and IBM are registered trademarks of International
Business Machines Corporation.
All other trademarks remain the property of their respective owners.