Hi,

I am having problems running VNC. I am attempting to run a VNCServer on my linux machine (Running RH7.2), and to access it using a VNCClient on my windows machine (Running WinME). Unfortunately it doesn't work. VNCServer seems to start OK:

[root@Snoopy root]# vncserver

New 'X' desktop is Snoopy:2

Starting applications specified in /root/.vnc/xstartup
Log file is /root/.vnc/Snoopy:2.log

When I attempt to connect from the Windows machine I receive no response in Windows after I have entered the machine to connect to. No password is asked for. It just disappears. The log created on the Linux machine shows the following:

06/01/02 14:12:22 Xvnc version 3.3.3r2+tight1.2.2
06/01/02 14:12:22 Copyright (C) AT&T Laboratories Cambridge.
06/01/02 14:12:22 All Rights Reserved.
06/01/02 14:12:22 See http://www.uk.research.att.com/vnc for information on VNC
06/01/02 14:12:22 Desktop name 'X' (Snoopy:2)
06/01/02 14:12:22 Protocol version supported 3.3
06/01/02 14:12:22 Listening for VNC connections on TCP port xxxx
06/01/02 14:12:22 Listening for HTTP connections on TCP port xxxx
06/01/02 14:12:22 URL http://Snoopy:xxxx

06/01/02 14:26:40 Refused connection from client 192.xxx.xxx.xxx

I've checked for previous postings, and searched Google for help, and I'm still stuck. I don't know what else to check. The message in the logs obviously doesn't provide much information.

I've also tried to connect through a web browser. This also failed. The message returned in IE6 is:

Bad Gateway

The following error occurred

A DNS Lookup error occurred. The host was not found

Is this really a DNS problem? Why did the VNCClient not report this? Which files do I have to check for this? I've checked the hosts file and couldn't see any problem.

Any help gratefully received.

Thanks.

New 'X' desktop is Snoopy:2
that would be screen 2. example: 192.168.1.105:5902

you have to specify the screen your trying to connect to. i.e. 192.168.1.105:5902 ,etc. same thing trying to connect through the browser http://192.168.1.105:5802
I havnt run it in a while but i think the client software uses the :59** and the browser uses :58**

Hi,

I have tried connecting through the client software, and my browser on the ports you mention. No luck unfortunately.

New 'X' desktop is Snoopy:2

Is that output that you posted off your machine? You really named a comp snoopy LOL. Just kidding

Have you tried running the vncserver as a normal user? not root.
And the desktop number may not be the same, you have to use the one that vncserver shows as it starts up. Can you ping your linux machine from your windows machine? Are you trying to connect through a firewall?

Hi,

When I run VNC as a normal user this I still have the same problem as before. However there is different output in the logfile:

07/01/02 18:32:57 Xvnc version 3.3.3r2+tight1.2.2
07/01/02 18:32:57 Copyright (C) AT&T Laboratories Cambridge.
07/01/02 18:32:57 All Rights Reserved.
07/01/02 18:32:57 See http://www.uk.research.att.com/vnc for information on VNC 07/01/02 18:32:57 Desktop name 'X' (Snoopy:2)
07/01/02 18:32:57 Protocol version supported 3.3
07/01/02 18:32:57 Listening for VNC connections on TCP port 5902
07/01/02 18:32:57 Listening for HTTP connections on TCP port 5802
07/01/02 18:32:57 URL http://Snoopy:5802
XIM DEBUG: xset: bad font path element (#37), possible causes are:
Directory does not exist or has wrong permissions
Directory missing fonts.dir
Incorrect font server address or syntax
Xlib: extension "RENDER" missing on display ":2.0".
DCOPServer up and running.
Xlib: extension "RENDER" missing on display ":2.0".
Xlib: extension "RENDER" missing on display ":2.0".
Xlib: extension "RENDER" missing on display ":2.0".
Server has no DPMS extension
Xlib: extension "RENDER" missing on display ":2.0".
Xlib: extension "RENDER" missing on display ":2.0".
Xlib: extension "RENDER" missing on display ":2.0".
There are already artsd objects registered, looking if they are active...
Xlib: extension "RENDER" missing on display ":2.0".

Error: Can't add object reference (probably artsd is already running).
If you are sure it is not already running, remove the relevant files:

/tmp/mcop-user/Arts_SoundServerV2
/tmp/mcop-user/Arts_SoundServer
/tmp/mcop-user/Arts_SimpleSoundServer
/tmp/mcop-user/Arts_PlayObjectFactory
/tmp/mcop-user/Arts_AudioManager


07/01/02 18:33:16 Refused connection from client 192.xxx.xxx.xxx
Xlib: extension "RENDER" missing on display ":2.0".
Xlib: extension "RENDER" missing on display ":2.0".
Xlib: extension "RENDER" missing on display ":2.0".
Xlib: extension "RENDER" missing on display ":2.0".

I have no idea what this means. Any Suggestions?

I am able to ping both machines from each other. I have a firewall active on the Windows machine (it is used as my internet gateway). This has been configured not to interfere with my Lan. Since the error message in the logs indicates that the connection is being refused by the Linux box, I don't think that there is a problem with the firewall. Unless there is one on RH7.2 that is automatically configured on installation.



I have been using the correct desktop numbers.

What runlevel do you boot up to 3 or 5? Try this: change to runlevel 3, by typeing as root "/sbin/init 3" That should shutdown Xwindows and put you back at a command prompt. log back in as a normal user and start your vncserver. Still getting those errors? Some of them looked to be sound related errors: arstd.

Hi,

Top man! VNC is now working! However, I still have a few problems/issues.

The logfile contains a lot of errors:

07/01/02 22:49:49 Xvnc version 3.3.3r2
07/01/02 22:49:49 Copyright (C) AT&T Laboratories Cambridge.
07/01/02 22:49:49 All Rights Reserved.
07/01/02 22:49:49 See http://www.uk.research.att.com/vnc for information on VNC 07/01/02 22:49:49 Desktop name 'X' (Snoopy:1)
07/01/02 22:49:49 Protocol version supported 3.3
07/01/02 22:49:49 Listening for VNC connections on TCP port 5901
07/01/02 22:49:49 Listening for HTTP connections on TCP port 5801
07/01/02 22:49:49 URL http://Snoopy:5801
XIM DEBUG: xset: bad font path element (#37), possible causes are:
Directory does not exist or has wrong permissions
Directory missing fonts.dir
Incorrect font server address or syntax
Xlib: extension "RENDER" missing on display ":1.0".
DCOPServer up and running.
Xlib: extension "RENDER" missing on display ":1.0".
Xlib: extension "RENDER" missing on display ":1.0".
Xlib: extension "RENDER" missing on display ":1.0".
Server has no DPMS extension
Xlib: extension "RENDER" missing on display ":1.0".
There are already artsd objects registered, looking if they are active...
Xlib: extension "RENDER" missing on display ":1.0".
Xlib: extension "RENDER" missing on display ":1.0".

Error: Can't add object reference (probably artsd is already running).
If you are sure it is not already running, remove the relevant files:

/tmp/mcop-user/Arts_SoundServerV2
/tmp/mcop-user/Arts_SoundServer
/tmp/mcop-user/Arts_SimpleSoundServer
/tmp/mcop-user/Arts_PlayObjectFactory
/tmp/mcop-user/Arts_AudioManager

Xlib: extension "RENDER" missing on display ":1.0".
Xlib: extension "RENDER" missing on display ":1.0".
Xlib: extension "RENDER" missing on display ":1.0".
Xlib: extension "RENDER" missing on display ":1.0".
Xlib: extension "RENDER" missing on display ":1.0".

07/01/02 22:50:29 Got connection from client 192.xxx.xxx.xxx
07/01/02 22:50:29 Protocol version 3.5
07/01/02 22:50:29 Ignoring minor version mismatch
07/01/02 22:50:34 Pixel format for client 192.xxx.xxx.xxx:
07/01/02 22:50:34 8 bpp, depth 8
07/01/02 22:50:34 true colour: max r 7 g 7 b 3, shift r 0 g 3 b 6
07/01/02 22:50:34 no translation needed
07/01/02 22:50:34 Using hextile encoding for client 192.xxx.xxx.xxx
07/01/02 22:50:34 rfbProcessClientNormalMessage: ignoring unknown encoding type
8
07/01/02 22:50:34 rfbProcessClientNormalMessage: ignoring unknown encoding type
7
07/01/02 22:50:34 rfbProcessClientNormalMessage: ignoring unknown encoding type
6
07/01/02 22:50:34 rfbProcessClientNormalMessage: ignoring unknown encoding type
-240
07/01/02 22:50:34 rfbProcessClientNormalMessage: ignoring unknown encoding type
-239
07/01/02 22:50:34 rfbProcessClientNormalMessage: ignoring unknown encoding type
-224

I have no idea if these are OK or not.

Also, VNC seems to be pretty slow. I know it can be used over an internet connection, so I would have thought it would be quicker over a LAN. This isn't severe. There's maybe a 0.5 second lag when moving the mouse.

The last thing is that VNC stops working after I reboot, exactly the same as before. I presume that I have to make changes to my configuration for runlevel 3. How/where do I do this?

Thanks for your help.

Did it start working after you started it from runlevel 3?
You can change it so you boot up into runlevel 3 by editing /etc/inittab there is a line near top top that says id:5:initdefault change the 5 to a 3, and reboot. It will boot to a command propmt. you can start your vncserver like ./vncserver

VNC does run a little slow. How fast is you linux box? And it might run faster in full screen mode. And remember: when you connect to your linux box with the vncviewer and are done DO NOT LOGOFF, just close the vncviewer. Your vncserver will stay running.

How do you connect to your linux box to start the vncserver?
might have some more helpfull info if you say ssh.

The errors: The user you use for the vncserver, have you ever logged into xwindows with that user? If so did you have any errors when you did? Some of them look like informational stuff. the artsd should go away in runlevel 3. If you are going to be logging in with vnc only then you dont need sound anyway and you can use ntsysv to stop the artsd autostart.

Thanks for all your help on this. I had no idea about runlevels, and will find out more about them now.

Your Welcome, So you got it running? Thats good. I still use it on my win2kserver, cause i dont have an extra monitor, I dont use it on my linux machines anymore, I use ssh.

Glad I could help..

It seems as though this thread is a little old, but, I am currently getting the exact same log file results that the initial poster was.

Basically, I am running a Red Hat 9 system and trying to install the vnc server that came with the distro discs, which happens to be version 3.3.3r2+tight1.2.2. Network connectivity seems to be fine, as I can ftp and ssh to the server in question. Plus, I have been able to setup a Fedora Core 3 system with a later version of vnc server and connect with no problem. So, I know that the VNCViewer that is installed on the Windows XP system I am using to connect is fine as well.

Now when the RH9 system boots, there are some rules in the IPTABLES, but, I flush the iptables before trying to connect. Here is my exact log file:

24/03/06 13:20:52 Xvnc version 3.3.3r2+tight1.2.2
24/03/06 13:20:52 Copyright (C) AT&T Laboratories Cambridge.
24/03/06 13:20:52 All Rights Reserved.
24/03/06 13:20:52 See <URL Here> for information on VNC
24/03/06 13:20:52 Desktop name 'X' (localhost.localdomain:1)
24/03/06 13:20:52 Protocol version supported 3.3
24/03/06 13:20:52 Listening for VNC connections on TCP port 5901
24/03/06 13:20:52 Listening for HTTP connections on TCP port 5801
24/03/06 13:20:52 URL <URL for web traffic here>
SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/24397
Option given which is no longer supported in this version of gnome-terminal; you might want to create a profile with the desired setting, and use the new --window-with-profile option

24/03/06 13:21:12 Refused connection from client 192.168.0.2

That Option line in there... could that be the issue?

I also tried shutting down and running it with an init 3... no luck, exact same problem.

Is there anything else (besides iptables) that could be restricting access on certain ports? When I try telnetting to ports on the linux computer, services like FTP (which is active on the box) respond, all other ports seem to be refused. XP tells me that the destination system refused the connection.

I thought I would follow this up with the solution that I finally found. A number of people (in a number of posts) on the internet suggested checking iptables to see if that port was open. Perhaps this is obvious to some of the more savvy system administrators out there, but, my problem was in the hosts.allow and hosts.deny files. My hosts.allow file was extremely restrictive. During the process of trying to solve this, I did try removing all rules from the hosts.deny file which was basically ALL:ALL. I commented that out and restarted. It did not fix the problem. It wasn't until I amended the hosts allow file to add all ports from LAN computers (ALL:192.168.0.) that VNCServer started to accept traffic from all systems.