Thanks. What I ended up doing was to put the command into ~/.profile. As far as wm, I'm starting fvwm2, and on the client side "vncviewer -fullscreen suse1:1. Surprisingly, everything works on the client, even the pager and xscreensaver, although some of the 3D graphics hacks really make that network hub light up. This is pretty slick. The client is my laptop. I've got it set up so that it's a fully functioning laptop as a standalone, but when it's hooked to my home network VNC makes it a thin client. This was a fun Saturday. On Sat, 2004-03-13 at 23:37, Gordon Cichon wrote:
Tim Hanson wrote:
I'm trying to figure out if vnc requires additional steps, or what I'm forgetting about installing vncserver and vcviewer. When running vncviewer from the client, i.e., vncviewer 192.168.xx.xx to a computer on my home network, I get "connection refused." I set up a password on the server with vncpasswd. Should I have done that on the client instead?
Is there a config file which allows or denys connections?
When running under Linux, you have to start a VNC server explicitly. (In Windows, you get a default server on your Desktop.) You may use a command line like this:
vncserver :1 -name tim -depth 16 -geometry 1280x1024
If you like to get a fancy windows manager, you may like to provide a file ~/.vnc/xstartup containing commands like this:
#!/bin/sh
xrdb $HOME/.Xresources /usr/bin/startkde
Cheers, Gordon. --