This is a continuation of the previous blog on XDMCP. Firstly we start off with the definition of an XMDCP client. The client is actually an xserver that collects information of the mouse, keyboard and other X matters from a XDMCP server. Well, atleast that is the easiest way to explain. An example of such a client is the multipurpose Xnest.
The Xnest software states the following:
Xnest is a client of the real server which manages windows and graphics requests on its behalf. Xnest is a server to its own clients. Xnest manages windows and graphics requests on their behalf. To these clients Xnest appears to be a conventional server.
The client environment I have tested is on Linux CentOs 5.1. On the XDMCP server is a user called username with the password as password. The example server IP used is 10.20.20.172.
1. Login to a graphical environment (I use GNOME) as a normal user. Choose Applications ->Accessories ->Terminal
2. At the terminal type the following:
$ ssh -X username@10.20.20.172
$ Xnest :1 -geometry 800x600 -query 10.20.20.172
3. Login with the given name and password.
Looking at alternative computer software solutions for a variety of reasons. This includes price, computer security, virus prevention and reliability. Here are my notes and great that if it helps you, otherwise please understand what you are doing and not follow blindly. All works expressed are my own and does not necessarily express the products or organisations mentioned here.
Subscribe to:
Post Comments (Atom)
Blog Archive
-
▼
2008
(85)
-
▼
March
(12)
- Screenlets to enhance Linux
- gdesklets to enhance Linux
- yum with RHEL 5.x and CentOS 5.x
- R60 laptop and projector display
- Its Good Friday.
- The thin client for XDMCP
- Creating an XDMCP server
- OSS in Japan Public Sector
- OpenOffice.org in Malaysian Public Sector
- Sending Linux Text to MS Windows
- Malaysia Polls for 2008
- OpenOffice.org and MS Office 2003 - Indentation
-
▼
March
(12)
No comments:
Post a Comment