Connecting to RHL from Windows?
JAldrich "at" covista.com
Fri Apr 28 17:39:01 2006
By default, in the X-Windows world, you can't use the VNCSERVER script to
remote :0, i.e. port 5900. There are add-ins (including ones from RealVNC, I
believe it's vnc.so) which will allow that, but by default, VNC sessions
start at :1. As for the grey screen, you need to run the "vncserver" script
which in turn calls the "xstartup" script in ~/.vnc which looks like this:
# Red Hat Linux VNC session startup script
(Except that it does not normally contain the "unset.." line.) That *should*
start the VNC session *with* the Window Manager of your choice.
> -----Original Message-----
> From: vnc-list-admin "at" realvnc.com [mailto:vnc-list-admin "at" realvnc.com]On
> Behalf Of Damian Connolly
> Sent: Friday, April 28, 2006 10:57 AM
> To: vnc-list "at" realvnc.com
> Subject: Connecting to RHL from Windows?
> Hi All,
> We are experiencing a few difficulties connecting to VNC on a
> RHL box from
> Windows (including web-based connection). Basically, at
> server :5900 the
> server does not respond to any connection. If we create a new
> session by
> using the command vncserver :2, we are asked to authenticate
> when connection to server:2), but the screen shown is just a terminal
> screen. We were hoping to be able to access the full GUI as
> we can with
> other Linux servers (including a fedora box) as we can access
> what VNC
> gives us via telnet. Where are we going wrong?
> p.s., if we start the server by using vncserver it shifts to the next
> available port (1,2,3,4,etc...) and if we try vncserver :5900
> we get a
> message "VNC server is already running as :5900"
> Any help would be much appreciated!
> This e-mail has been scanned for all viruses by Star. The
> service is powered by MessageLabs. For more information on a proactive
> anti-virus service working around the clock, around the globe, visit:
> VNC-List mailing list
> VNC-List "at" realvnc.com
> To remove yourself from the list visit: