This was resolved by editing the /etc/sysconfig/vncservers to include a display. The username in the configuration indicates the user under which vncserver will run. I found it is not recommended to run as the root user (duh!). Once the config is done, connecting from a WinXP client should use :. By default, the viewer will attempt to connect to display :0, which causes many issues. In my case, I used "mydomain.com:1", and it worked fine.
Be aware that the password request is not the password of the user account, but the password set by vncpasswd. It is stored encrypted in ~/.vnc/passwd.
Finally, gnome-settings-daemon seems to have some known issues with RealVNC. Disable/uninstall the package to make things run more smoothly. I was still able to connect OK, but there are many reports of keyboard failures attributed to the daemon.
1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:
|
[root@fedora-backup .vnc]# cat /etc/sysconfig/vncservers
# 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
# .
# Use "-nolisten tcp" to prevent X connections to your VNC server via TCP.
# Use "-nohttpd" to prevent web-based VNC clients connecting.
# Use "-localhost" to prevent remote VNC clients connecting except when
# doing so through a secure tunnel. See the "-via" option in the
# `man vncviewer' manual page.
# VNCSERVERS="2:myusername"
# VNCSERVERARGS[2]="-geometry 800x600 -nolisten tcp -nohttpd -localhost"
VNCSERVERS="1:username"
VNCSERVERARGS[1]="-geometry 1024x768"
|
Open in New Window
Select All
