Shulou(Shulou.com)06/02 Report--

Nagging do not like not to touch: work has been done for such a long time, installed machines are not graphical interface, today's sudden development needs a graphical interface, this is also very simple, when installing the system can be installed, but Nima also needs to be able to connect remotely under windows, this is even forget, unexpectedly said to use mstsc connection, vnc is not quickly solved, omitted here N more words, must think I scolded in mind Ah, you have to scold no matter what you ask, but I am still very happy, because I like challenging things if I haven't done them. Although it's not a big project, this is how the technology grows. There is no good growth in what I do every day. No more nonsense, let's do it.

The Windows system uses mstsc to remotely connect the graphical interface of redhat6.5.

1. Implementation method:

Step 1: download the source code package and install some dependent software to download the xrdp source code package

Wget http://downloads.sourceforge.net/project/xrdp/xrdp/0.6.0/xrdp-v0.6.0.tar.gz

Make sure that the system already has dependent packages gcc, pam-devel, openssl-devel,libtool, especially that vncserver must be installed, and yum can be installed online directly. (as the case may be)

Step 2: install the xrdp unzip installation package:

Tar-xzvf xrdp-v0.6.0.tar.gz

Go to the installation package directory to compile and install: cdxrdp-v0.6.0

. / bootstrap

. / configure

Make

Make install (root running)

Note: if the installation is wrong, install the corresponding dependency package according to the error message.

Step 3: configure xrdp

Modify the configuration file / etc/xrdp/xrdp.ini, and modify the value of port in the parameter [globals]. Here, the port port can be set at will. I did not set or use the original 3389 for this step. The configuration file of xrdp is attached below. I think it's better to have a look, because my English is not good.

The key part of xrdp.ini is global.

[globals]

Bitmap_cache=yes bitmap cache

Bitmap_compression=yes bitmap compression

Port=3389 listening port

Crypt_level=low encryption (low is 40 bits, high is 128bits, medium is dual 40 bits)

Channel_code=1 doesn't know what it is.

Sesman.ini

[Globals]

ListenAddress=127.0.0.1 listens for ip address (default is OK)

ListenPort=3350 listening port (default)

EnableUserWindowManager=1 1 is enabled and allows users to customize their own startup scripts

UserWindowManager=startwm.sh

DefaultWindowManager=startwm.sh

[Security]

AllowRootLogin=1 allows root to log in

Maximum number of MaxLoginRetry=4 retries

TerminalServerUsers=tsusers allows user groups to connect (all users are allowed to connect by default if it does not exist)

TerminalServerAdmins=tsadmins allows connected superusers (if it does not exist, all users are allowed to connect by default)

[Sessions]

Maximum number of MaxSessions=10 sessions

Whether KillDisconnected=0 closes the disconnected connection immediately (if it is 1, it will log out automatically when it is disconnected)

IdleTimeLimit=0 idle session time limit (0 means no limit)

Time to live when DisconnectedTimeLimit=0 is disconnected (0 means no limit)

[Logging]

LogFile=./sesman.log login log file

LogLevel=DEBUG login log recording level (core,error,warn,info,debug, respectively)

Whether log is enabled by EnableSyslog=0

SyslogLevel=DEBUG system logging level

Start xrdp#/etc/xrdp/xrdp.sh start

Restart xrdp#/etc/xrdp/xrdp.sh restart

Restart the computer: shutdown-r now

Directly use the windows remote Desktop connection to enter 192.168.76.201 3389, enter the user name and password of the Linux machine, and you can connect.

Two. matters needing attention

Note: the failure of client connection may be caused by firewall blocking. Add a policy (modify configuration file / etc/sysconfig/iptables to copy a port 22 configuration, modify port to 6666, and then restart firewall serviceiptables restart) or stop firewall (serviceiptables stop) to connect successfully.

Note: if there is an error in the following picture

Xrdp_mm_process_login_response:login successful for displa started connecting

Connecting to 127.0.0.1 5910

Error-problem connecting

[root@web~] # rpm-qa | grep vnc

If nothing is displayed, the vnc package is not installed on the system and needs to be installed.

If the display:

Vnc-server-4.1.2-14.el5_3.1 (mainly this package, this is fine)

Vnc-4.1.2-14.el5_3.1

It indicates that the installation is successful, and if it is displayed after the first execution, the system has installed the vnc package.

Start VNCserver

[root@web~] # service vncserver start (launch only the interface defined by / etc/sysconfig/vncservers)

Let xrdp boot automatically:

# vi / etc/rc.local edit it, and then add:

/ etc/xrdp/xrdp.sh start

This is how RedHat 6 uses xrdp to log in to Windows remote Desktop. Although Linux and Windows are two different systems, the strength of RedHat 6 lies in its compatibility, so RedHat 6 can also log in to Windows remote Desktop.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.