Page 1 of 1

Strange VNC/Webvnc behavior

Posted: Tue Jul 27, 2010 8:10 am
by trebor
I have my HDA set up to receive connections via webvnc and vnc via chicken of the VNC.

I first set up webvnc by editing vncserver as instructed by adding:

VNCSERVERS="1:robert"
VNCSERVERARGS[1]="-geometry 1024x768 -depth 16"

I turned on desktop sharing with the following options: top two "sharing" options are "on", the "Ask for confirmation" option is off, and the password option is checked with a password entered in the blank. I got this working fine and all was good.

Next I wanted to set up my HDA to also utlize vnc using a vnc client such as Chicken of the VNC.

As instructed I installed vnc-server via "yum -y install vnc-server". I entered the same password that I had entered in desktop sharing for webvnc (not sure if this is relevant or not).

I turned on the server: vncserver
and made it so that it starts at boot: chkconfig vncserver on

If I remember correctly, I had to make some additional modifications to get the window size I wanted and to get it to start properly at boot.

OK, here is the weird part. Chicken of the VNC on my laptop connects fine on 5901 using login at "robert".

To test webvnc I first restarted the HDA. I log into HDA on the box running HDA---login in name is "robert".

I go to a desktop on my network and try webvnc---it looks like it is trying to connect but nothing is happening---it is just sitting there tyring to connect. I go back to the box running HDA and there are no error windows or anything. I go to my laptop on my network that has Chicken of the VNC on it and connect to my HDA---the desktop appears as expected, but there is a window open stating ""Enter password for default keyring to unlock"---NOTE: this does not typically pop up when I use Chicken of the VNC---only if I am trying to connect from another computer using webvnc. When I close the keyring window on my laptop Chicken of the VNC session, the webvnc session on my desktop that previously looked like it was trying to connect finally connects. Now the desktop webvnc is connected to and controling my Chicken of the VNC session on my laptop---my box running HDA is not being controlled by webvnc like I would expect. I cannot get webvnc to connect to or control the session on my HDA box---webvnc will only connect and control a session open via another computer using Chicken of the VNC.

I would just scrap using webvnc; however, I have computers that I want to connect to my HDA from that do not have Chicken of the VNC on it or any other VNC client (work computers). I have other computers that have Chicken of the VNC on that I would prefer to use rather than webvnc. I would like webvnc to connect to and control my HDA box session separate from and regardless of whether I have a Chicken of the VNC session open. What would be a recommended way to accomplish this?

If I had to guess at what is causing the problem... it seems to me that the session on my HDA box must be using display "0", my desktop trying to connect to HDA using webvnc is trying to connect to display "1" for some reason and cannot connect until display "1" is up and running via Chicken of the VNC. Not sure if this is right and if it is, not sure of the best way to accomplish what I would like.

Thanks in advance for any tips!
-Robert