Use Ubuntu to build a thin client machine based on XDMCP

Yesterday, the lab boss did not know where to turn out a broken Dell host, and then sat there alone for a long time.

 

After all the work was done, I ran to the audience and said, "What is this old machine ?"

 

Boss: "No machine is used. The purchased Dell machine was damaged when it was sent, and it was returned. They had to wait for it to be sent. Get this machine and use it for students ."

 

"Oh"

 

Boss: "But this machine is too old. It would be nice to automatically connect to the server to log on"

 

"LTSP? VNC ?"

 

Boss: "no"

 

"XDMCP ?"

 

Boss: "What is that ?"

 

"Self wiki"

 

......

 

Boss: "set the XDMCP on this machine. The root password is ....."

 

Bitter me ~~ Starting work!

Server Settings

XDMCP support is disabled by default in Ubuntu 9.10. You can enable it by modifying the configuration file.

Copy the configuration file

CP/usr/share/doc/TPD/examples/custom. conf/etc/TPD/now this custom. the conf file is as follows: # change the configuration storage [XDMCP] [chooser] [security] [debug] to this file: # em configuration storage [XDMCP] Enable = truedisplaysperhost = 2 [chooser] [security] [debug] Save and restart the EM service. Server Side handling ~~

Client settings

First install the required software package:

 

Sudo apt-Get install xnest

 

1. Method 1: Use the Applications> Internet> Terminal Server Client tool to connect to the XDMCP server. This is a graphical interface. The disadvantage is that you have to log on to the local machine before logging on to the XDMCP server. In addition, remote logon is also in the form of a window, which is unpleasant and incomplete.
2. Method 2: open a terminal and enter:

    

   Xinit --: 1-query xdmcp_ip_address

    

   After you press enter, the system starts a new X session and the logon interface of the server appears. Advantage: full screen without local graphical interface; disadvantage: You must log on to the local machine.

3. Method 3: the most thorough. Add the commands in method 2 to the/etc/rc. Local file. Then, you can delete useless graphic interfaces such as gnome and gmt1. After the user is started, the logon interface of the remote server is displayed, and the operation is directly performed on the server.

 

Several Problems

After method 3 is used, if a network problem occurs, a black screen is displayed after the client is started. No response is returned: Use CTRL + ALT + F2 to switch to the console to operate the client.

 

The shutdown and restart buttons are displayed on the client machine interface, but they do not actually work.

 

If the client plays music on the server, the sound will be played from the server's audio interface instead of the client. This problem can be solved, but it is of no use to me.