On Wednesday 10 September 2003 3:17 pm, Cleary_Mike@emc.com wrote:
Thanks, and yes, I usually pass it a display number. For example:
jethro:/tmp/.X11-unix # vncserver :0 VNC server is already running as :0
Do a ps -edf and see if Xvnc is indeed running for :0. If not you need to rm -fr /tmp/.X11-unix/X0 to unlock so you can start it again.
jethro:/tmp/.X11-unix # vncserver :1 New 'X' desktop is jethro:1 Starting applications specified in /root/.vnc/xstartup Log file is /root/.vnc/jethro:1.log
I still can't connect to display :0. I can connect to display :1, but because of what's in xstartup, I get a twm screen w/ one xterm open in it.
Keep in mind, if your firewall is configured to only pass the port for session 0, you may not be able to connect from home to :1.
That's not what I want. The way it used to work was once I connected (from home) I would see my screen just like it is on my desktop at work. I was passing vncviewer just the IP address, so it defaulted to display :0.
Lastly, remember when you launch vncviewer it goes as the user you are at the time. If you are logged in as root the seesion will be roots session, not yours. If you are logged in as you when you start vncserver :0, then look at $HOME/.vnc/xstartup I think it is. That is where you set the windows manager. Also note that kde has a nice GUI interface to setup desktop sharing and there is also x0rfbserver if you specifically want to share the desktop as it is at work instead of making a seperate x session. Greg Engel