![vnc connect to display 0 vnc connect to display 0](https://images.saasworthy.com/vncconnect_1816_screenshot_1544517893_ijxlp.jpg)
I guess that's one of the differences between vino & VNC. As you can see in the attached screen shot, when I connect using "remote desktop" (aka vino & Terminal Service Client) I get the user desktop :0. So, the vnc module for X is somewhat easier to use. In this case, you would have to connect as root, login as a user and the reconnect with X11vnc again as a user. But you can only connect as a user if a user is already logged into the computer.
![vnc connect to display 0 vnc connect to display 0](https://i.stack.imgur.com/pWwks.png)
There is another solution, using "X11vnc". For a file server or helping a local user on his desktop, you want to connect to the visiable display :0 not :1. Instead it creates another display :1 which is not visible. The standard vncserver does not allow connecting to the visible display :0 the display you would see if a monitor was connected to the computer. Logout and restart X (Ctrl-Alt Backspace) Option "PasswordFile" "/root/.vnc/passwd"Ĥ. Then tell the VNC module where the password is stored in nf: If your VNC server is NOT running in a secure environment, you will need to set a VNC password using the vncpasswd program: Add "vnc" to the Module section in /etc/X11/nfģ.a.If your VNC server is running in a secure environment, you can disable authentication with the following configuration:ģ.b. This will provide "/usr/lib/xorg/modules/extensions/libvnc.so" (The vnc.so module for VNC 4.1.2 was changed from vnc.so to libvnc.so.)Ģ.
#Vnc connect to display 0 install
Install the "vnc4server" package (universe). There is a vnc module for X that can be installed which will provide the native :0 X display when connecting remotely with the vncviewer.ġ.