Thank you BlckJck, that worked well. Now I can start vncserver with no errors.

Also, I created a file, /home/terry/.vnc/xstartup , that will give the viewer the X desktop. Here is xstartup:

#!/bin/sh
Xsession &


I have discovered 2 new problems however:

1) According to the vnc doc's on the web, I should be able to login to this machine via a webbrowser on some other machine (using some java witchery), using http://machine:5801. (vncserver's log file says that it is listening on TCP port 5901 and the doc's say to use port#-100.) However, this does not work and no message is listed in the logfile. If I try using machine:5901, the logfile notes the attempt and immediately kicks the client off. Here is the error message:

08/03/03 15:57:28 Got connection from client 192.168.1.7
08/03/03 15:57:28 rfbProcessClientProtocolVersion: not a valid RFB client
08/03/03 15:57:28 Client 192.168.1.7 gone

If I use vncviewer on the other machine, with machine:5901, vnc serves up a tasty helping of desktop.

2) I would like to have vncserver start up as soon as the system comes up. What is the best way to make that happen?
This machine will be in a closet and I would like to be able to have it recover from power failures by itself, as well as giving me the capability of modifiying it remotely.

Thank you
Terry Egan
P.S. Yes, this sw is installed on the hard drive.