I had posted last week about trying to get VNC working. I was never successful nor were multiple admins. But we realized that all the hosts we tried on were VMs. We followed the same procedure ( http://wiki.centos.org/HowTos/VNC-Server) on a machine with physical HW and it worked with no problem. But on the VM I can connect, but I don't get any window displayed. Here is what is in the log: Sat Oct 19 18:39:55 2013 vncext: VNC extension running! vncext: Listening for VNC connections on all interface(s), port 5902 vncext: created VNC server for screen 0 GNOME_KEYRING_SOCKET=/tmp/keyring-Y6Tg3c/socket SSH_AUTH_SOCK=/tmp/keyring-Y6Tg3c/socket.ssh GNOME_KEYRING_PID=19728 Failed to play sound: File or data not found ** (nm-applet:19775): WARNING **: <WARN> request_name(): Could not acquire the NetworkManagerUserSettings service. Error: (9) Connection ":1.552" is not allowed to own the service "org.freedesktop.NetworkManagerUserSettings" due to security policies in the configuration file 19/10/2013 06:39:59 PM Autoprobing TCP port in (all) network interface 19/10/2013 06:39:59 PM Listening IPv{4,6}://*:5900 19/10/2013 06:39:59 PM Autoprobing selected port 5900 19/10/2013 06:39:59 PM Advertising authentication type: 'VNC Authentication' (2) 19/10/2013 06:39:59 PM Advertising security type: 'VNC Authentication' (2) (polkit-gnome-authentication-agent-1:19796): GLib-GObject-WARNING **: cannot regster existing type `_PolkitError' (polkit-gnome-authentication-agent-1:19796): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed Initializing nautilus-gdu extension Initializing nautilus-open-terminal extension ** (gnome-panel:19761): CRITICAL **: panel_applet_frame_change_background: assertion `PANEL_IS_WIDGET (GTK_WIDGET (frame)->parent)' failed (polkit-gnome-authentication-agent-1:19796): polkit-gnome-1-WARNING **: No icon for themed icon with name 'preferences-system-network-proxy' Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2c00003 (Authentica) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2c00003 (Authentica) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. 19/10/2013 06:40:48 PM [IPv6] Got connection from client ::ffff:10.250.151.75 19/10/2013 06:40:48 PM other clients: 19/10/2013 06:40:49 PM Client Protocol Version 3.7 19/10/2013 06:40:49 PM Advertising security type 2 19/10/2013 06:40:49 PM Client returned security type 2 Anyone have any clues as to what could be wrong and why it works on a physical host and not on a VM?