"Windows isn't a virus, viruses do something."
All articles
Last comments
In mate, when I try to add background image in my selection, the new images are always lost when I reopen the mate backgroung setting.
But if you don't register, you can't access to playlist features
What is your system version?
«    October 2016    »
» » Remote desktop via VNC from Windows to Linux Mint

Remote desktop via VNC from Windows to Linux Mint

Remote desktop via VNC from Windows to Linux MintRemote desktop via VNC from Windows to Linux Mint
Almost all the articles that are in the Internet says about configuring VNC how about connecting to a new session. It does not suit me. I need to connect to my home PC that runs under Linux, and gives the torrents and all that. I don't need to create a new session, but need to get proper access to the current session.

Sorry for the spelling and phonetic errors in the text.
Owner and main writer of MintGuide.org is not a native English speaker.

First of all I will say is that this method allows to gain remote access not only from Windows but also from any Operating system, to work with your Linux Mint from everywhere.
At least kill me, but I never got to connect to my computer Linux Mint using a standard VNC server "Vino". Given access but to connect failed. In addition nowhere could I find information about this.
In this regard, i will describe installation of third-party x11vnc server.
More importantly, access can be obtained when only works GMD i.e. the user is not logged in. Once it becomes clear that vino (part of Gnome) not suitable for this. The aid comes x11vnc. It pulls vnc4server but it's logical.
So the task:
to provide access to the machine via VNC even if the user is not logged in. To use only one session.

1. Remove vino (to avoid problems with the occupation of the port and the like)
sudo apt-get -y remove vino
2. Install x11vnc
sudo apt-get -y install x11vnc

3. Make the password to access VNC. Here we must be very careful here's why.

By default, VNC doesn't use shh tunnel therefore information

is not encrypted, because if the machine you are very important

and critical need of googling on the subject forward VNC and its ports through an SSH tunnel.

x11vnc -storepasswd
The password is stored in the /home/YOUR USER NAME/.vnc/passwd (where YOUR username is the user name under which you executed the command). It is important to execute this command is not under sudo otherwise there would be problems with access rights for login. 
4. The startup service x11vnc. It is very important (to me) that the service was already available at boot X i.e. the user is not logged into the system, but access to the machine already has. To do this, need to have access at the level of GDM.
In some systems use a different welcome screen, not gdm3 therefore this directory is not. For example: Linux Mint 17/16/15/14/13 (MATE) uses MDM. Edit the file /etc/mdm/Init/Default (don't forget to run it as root or sudo otherwise not save the changes):
for mate 
sudo pluma /etc/mdm/Init/Default
sudo gedit /etc/mdm/Init/Default
Add to the end of the file before exit 0 the following line:
/usr/bin/x11vnc -dontdisconnect -notruecolor -noxfixes -shared -forever -rfbport 5900 -bg -o /var/log/x11vnc.log -rfbauth /home/YOUR USER NAME/.vnc/passwd

Remote desktop via VNC from Windows to Linux MintRemote desktop via VNC from Windows to Linux Mint

From the key parameters should pay attention to the following:
-dontdisconnect - do not disconnect when idle time, which is important if turned sessions window
-forever is a very important parameter. Without it x11vnc after the session is closed off and more you will not go until ssh again not run it, that is not convenient.
-rfbport - specify on which port will work our VNC (I pointed 5900)
More detailed settings, you can look in the manual x11vnc:
man x11vnc
5. Additionally are dropping (disconnecting from vnc) when you login in to your account on the computer screen via VNC. I did that because on my home computer to multiple accounts. The solution suggested by our reader BENAHLQUIST. It works.
Open the config mdm
for mate 
sudo pluma /etc/mdm/mdm.conf
for cinnamon
sudo gedit /etc/mdm/mdm.conf
Under the [daemon] section, add this line:

Remote desktop via VNC from Windows to Linux MintRemote desktop via VNC from Windows to Linux Mint

Next, save all files and restart the machine.
Then run any VNC client on a foreign computer, such as TightVNC or UltraVNC. Enter your computer's IP and port.

Remote desktop via VNC from Windows to Linux Mint

Remote desktop via VNC from Windows to Linux Mint

If your computer is behind a NAT forward ports in your router. Enjoy!

Remote desktop via VNC from Windows to Linux MintRemote desktop via VNC from Windows to Linux Mint

Good Luck!!!
Usefulness of the article
This article helped you?
Yes - 1 (50%)
No - 1 (50%)
Not fully - 0 (0%)
Total votes: 2
Edited by Shekin - 3-10-2016, 20:18
Reason: fixed some inaccuracies

Related articles


  1. Paul
    The line

    /usr/bin/x11vnc -dontdisconnect -notruecolor -nofixes -shared -forever -rfbport 5900 -bg -o /var/log/x11vnc.log -rfbauth /home/YOUR USER NAME/.vnc/passwd

    should read

    /usr/bin/x11vnc -dontdisconnect -notruecolor -noxfixes -shared -forever -rfbport 5900 -bg -o /var/log/x11vnc.log -rfbauth /home/YOUR USER NAME/.vnc/passwd

    and without this x11vnc won't start and a remote connection isn't possible.

    In short "-nofixes" causes an error. It should be "-noxfixes".

    Vino and x11vnc can coexist if vino is left on the default port of 5900 and x11vnc uses 5901 (edit the line above accordingly and use with VNC client and router as needed).

    Oops. I forgot to insert the "x" in the 2nd copy of the line!

    I suggest that the article be edited and comments about "nofixes" deleted.
    1. Shekin
      x64 Linux Mint 18 cinnamon
  2. Azizur Rahman
    First of All Thanks for sharing your knowldge

    I have some error after this tutorial ,when i conntect from windows 7 Tightvnc the it show
    "no connection could be made because the target machine actively refused it"

    Kindly Help me
  3. Uwe
    Did work for me - better solution than vino, because no login is requested before connection. However - the "-nofixes" option did waste a lot of my time; because it's not a valid option.
  4. Ghozi Nashrullah Habibi
    Big thanks to you brooo!!
    It's really worked for me!!
  5. Tray
    Thank you! This worked for me. Your awesome. This of course was the last thing I tried to make it work and it finally worked as expected! The only thing I did notice is that after I was done I had to remove firefox and then reinstall using the Software Manager, otherwise firefox never launched when I clicked on it. Might be related to removing Vino, but firefox works fine after a reinstall.
  6. willichan
    Finally! After trying all the different solutions, including several that broke the desktop, this solution worked!

    The only gotcha I encountered was with the login screen. With the password file stored under my profile, I had to be logged in as myself on the Mint station first before the password would be accepted on the remote station.

    By logging in as root, and generating the password file in /root/.vnc/passwd (and, of course, updating that path in the /etc/mdm/Init/Default file) I can then access the login screen remotely when no user is logged into the Mint station.
  7. Alex
    Vino advertises security type 18 which apparently is TLS and according to a user on a mailing list this is widely unsupported by most Windows VNC viewers.

    An easy way to solve this is by disabling the encryption alltogether by doing:

    gsettings set org.gnome.Vino require-encryption false
    1. Uwe
      Should have seen this earlier :-)
      But however - this solution works better, because no login is neccessary before connecting...
  8. benahlquist
    Thanks for the super helpful tutorial!

    I did have something you could add however; as your steps result in a problem with the VNC connection dropping when a user logs in.

    For Cinnamon (I'm using this - confirmed working)

    sudo gedit /etc/mdm/mdm.conf

    (For GDM, I believe this would be /etc/gdm/gdm.conf)

    Under the [daemon] section, add this line:

  9. merlinpatt
    Thank you! This worked for me. If anyone's looking to do this not on their home network, be sure to forward the port on your router
  • bowtiesmilelaughingblushsmileyrelaxedsmirk
Login via