I. Overview:
First, let's take a look at the software currently used for remote desktop and the protocols used.
The Remote Desktop Connection component communicates with each other based on the Remote Desktop Protocol (RDP. Remote Desktop Protocol (RDP) is a multi-channel Protocol that allows users (clients or local computers ") connect the computer that provides the Microsoft Terminal Service (the server or remote computer "). Most Windows systems have the software required by the client. Other operating systems also have these client software, such as Linux, FreeBSD, and Mac OS X. For the server computer, listen to the data sent to the TCP3389 port.
VNC (Virtual Network Computing) is a super thin customer system based on the RFB (Remote Frame Buffer) protocol, designed and developed by Cambridge's AT&T lab. The default vnc ports are main: 5900 (C/S) and http: 5800 (B/S. VNC (Virtual Network Computer) is short for Virtual Network Computer. VNC is an excellent remote control tool software developed by the famous AT&T European research laboratory. Many well-known remote desktop software cities are modified and packaged based on the vnc software, such as Teamviewer, XT800, and KDT.
Through the above description, we already know that we are using the RDP-based viewer on the window. To use the remote desktop of the window, we need to run an rdp-based server on Ubuntu. The problem is to install an rdp-based server on Ubuntu. The XRDP server can provide such services. So you only need to install an xrdp.
II. Installation process
1. Install xrdp and vnc4server
Sudo apt-get install xrdp
Sudo apt-get install vnc4server ubuntu14.10 seems to be installed automatically
Tightvncserver is not installed in ubuntu14.04, if it is connected to ubuntu12.04. Yes
Sudo apt-get install tightvncserver
2. Install xfce4 desktop
Sudo apt-get install xubuntu-desktop
Echo xfce4-session <~ /. Xsession
Sudo service xrdp restart
3. Connection configuration
After all the above are installed, go to "preference-remote desktop" (or go to the/usr/share/applications/directory and click "Remote Desktop") and set it to allow remote desktop, allow control, and so on.
4. window connection operations
Open "Remote Desktop Connection" and fill in the Ubuntu IP address you want to connect to in the "computer" column. In Ubuntu, you can use "ifconfig" to obtain the overview of the local network connection, including the IP address.
Enter the correct IP address and press enter to display a logon box.
Method 1: Select vnc-any or console, enter the IP address, and the port remains unchanged (5900). The password you set can be remotely connected to ubuntu.
If you are prompted that the permission is insufficient, perform the following operations:
1. Install dconf-editor
Sudo apt-get install dconf-editor
2. Use Dconf-editor to adjust and access the following configuration path:
Org> gnome> desktop> remote-access
3. Deselect the requlre-encryption attribute.
Method 2: Select "sesman-Xvnc" and enter your Ubuntu user name and password. There is a cross in the middle. The cause is being investigated!
Because multiple unity and GNOME desktop managers exist in ubuntu12.04 at the same time, you need to specify one at startup. Otherwise, even after the remote login verification is successful, it is only a background and nothing else
Sudo gedit/etc/xrdp/startwm. sh
Insert a row before./etc/X11/Xsession
Echo "gnome-session -- session = ubuntu-2d">. xsession
Save the file and restart xrdp.
Sudo/etc/init. d/xrdp restart
5. Keyboard chaos
This remote connection to Ubuntu found that the tab key on the keyboard was faulty, and many key combinations were also faulty. The source of this problem is a combination of shortcut keys in xface. Open the administrative keyboard shortcut (Setting Editor-> xface4-keyboard-shortcuts) on Ubuntu and find a combination shortcut for super + tab to cancel the corresponding functionality.
Note:
1. If the remote connection fails, run sudo reboot on the terminal to restart the system.
2. As for why xface is used, because in Ubuntu 14.04, xface can only be connected. If it is another window manager, it will fail. According to Google's results, the encryption method does not match. Use Dconf-editor to adjust the solution and access the following configuration path: org> gnome> desktop> remote-access, deselect the requlre-encryption attribute.