Results 1 to 5 of 5
Thread: Windows and FC4 VNC
Enjoy an ad free experience by logging in. Not a member yet? Register.
- Join Date
- Nov 2005
Windows and FC4 VNC
Which way are you trying to do this? To start vnc server on windows, install the service, and connect to it from Linux using 'vncviewer [host]:0'.
To turn on the vnc server in FC4, you need to edit the file /etc/sysconfig/vncservers to add a screen for each user you want the vnc server for (you can work more than one), then start the vnc server service ('service vncserver start'). Dont forget to add this service to your current runlevel if you need it starting automatically at bootup. Dont forget to set the password using vncpasswd for each user.
Then from windows, you just need to connect using the viewer, and type [hostname]:[screennum] in the connect box, and type in the correct password.
- Join Date
- Nov 2002
This is what I did on FC4 I am logging as root (I know the security implication)
[root@localhost ~]# rpm -q --info vnc-server
Name : vnc-server Relocations: (not relocatable) Version : 4.1.1 Vendor: Red Hat, Inc. Release : 10 Build Date: Wed 27 Apr 2005 10:44:11 AM GST Install Date: Wed 15 Feb 2006 11:53:50 PM GST Build Host: decompose.build.redhat.com Group : User Interface/X Source RPM: vnc-4.1.1-10.src.rpm Size : 3054396 License: GPL Signature : DSA/SHA1, Fri 20 May 2005 10:28:29 PM GST, Key ID b44269d04f2a6fd2Packager : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla> URL : http://www.realvnc.com Summary : A VNC server. Description : The VNC system allows you to access the same desktop from a wide variety of platforms. This package is a VNC server, allowing others to access the desktop on your machine.
The gedit /etc/sysconfig/vncserver
# The VNCSERVERS variable is a list of display:user pairs. # Uncomment the lines below to start a VNC server on display :2 # as my 'myusername' (adjust this to your own). You will also # need to set a VNC password; run 'man vncpasswd' to see how # to do that. # DO NOT RUN THIS SERVICE if your local area network is # untrusted! For a secure way of using VNC, see # <URL:http://www.uk.research.att.com/vnc/sshvnc.html>. #zillah uncomment VNCSERVERS="2:myusername" VNCSERVERS="2:root" #zillah uncomment VNCSERVERARGS="-geometry 800x600" VNCSERVERARGS="-geometry 800x600"
[root@localhost ~]# vncpasswd root
[root@localhost ~]# vncserver
New 'localhost.localdomain:2 (root)' desktop is localhost.localdomain:2 Starting applications specified in /root/.vnc/xstartup
then start the vnc server service ('service vncserver start').
Then I run as well
[root@localhost ~]# service vncserver start
Starting VNC server: 2:root A VNC server is already running as :2
Then from windows, you just need to connect using the viewer, and type
[hostname]:[screennum] in the connect box, and type in the correct
The error message that I received when I typed in the ip address for the address is below:
VNC Viewer: 220.127.116.11:Error unable to connect to host: The requested address is not valid in its context.(10049)
Ok, in your step marked 'fourth', you dont have to run both 'vncserver' and 'service vncserver start' - the first way just executes the vncserver, the second way starts vncserver as a server process in the background. The second way is the preferred option.
What is happening here is that whenever you try to connect, it seems to be struggling to locate the machine, or it is struggling to connect thorugh some local firewall.
Things to check:
That you're connecting by the right IP address (on the same machine, i.e. the right place to test that it's working, it should be enough to just connect to ':2' without specifying the machine name).
Check your firewall settings on the linux machine - if the machine is rejecting connections on port 5902 (the port for vncserver screen :2), then you wont be able to see the screen.
So, test it on the same machine first (using vncviewer from linux), then check that you can connect to the machine on that port by using the windows vnc client viewer with the right address or hostname for the linux computer.
it should be enough to just connect to ':2' without specifying the machine name
- Join Date
- Nov 2002
Check your firewall settings on the linux machine - if the machine is rejecting connections on port 5902
May be I forgot to tell you that I have done this as well :
I am using FC4. The fix for me was that the default iptables (i think
thats the firewall settings) were preventing incoming VNC connections.
To overcome this in gnome i went to Desktop>System Settings>Server Settings>Services There I stopped iptables - and immediately I was able to connect!