Dell Wyse Enhanced Ubuntu Linux T50 Manual de usuario Pagina 14

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 220
  • Tabla de contenidos
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 13
Chapter 2. ThinLinc Architecture
Figure 2-1 gives an overview of the ThinLinc architecture.
Several different clients can be used to connect to a ThinLinc system. Clients are available for Linux,
OSX, Solaris and Windows, as well as a client for any web browser with support for HTML5.
The clients connect to a ThinLinc system located on the Local Area Network (LAN) or on a Wide Area
Network (WAN) such as the Internet. Depending on the network type and the bandwidth available,
several bandwidth-saving algorithms can be used to provide good performance even over narrow-banded
links. Encryption is used to secure all information sent between the client and the server.
When a user connects to a ThinLinc server, a session is created. This session is the user’s starting point
for running applications either on the ThinLinc server(s) or on other servers reachable from the ThinLinc
server. ThinLinc has a Single Sign-On (SSO) mechanism that enables passwordless but secure logins to
(for example) Windows Terminal Servers and other Unix Servers running special applications.
The ThinLinc servers can run either Linux or Solaris. There is support for High Availability and
advanced two-level load balancing.
2.1. Session Overview
When a user logs in from a native ThinLinc client, the following will happen:
The client establishes a SSH tunnel to the server entered in the server field of the client interface. If
this fails, then the login process will be interrupted and an error message will be displayed.
The client tries to authenticate with the VSM server, through the SSH tunnel. The VSM server (VNC
Session Manager) is the main process of ThinLinc, responsible for allocating and keeping track of user
sessions.
If the authentication succeeds, the server will check if there already exists a session for the user. If
there is a session, then information about it will be returned. If there is no session a new one will be
started on a terminal server and information about it will be returned. If more than one terminal server
exists, load balancing will be used to select which server to start a session on.
The client now disconnects the SSH tunnel to the VSM server and checks the information it received
to see which terminal server it should connect against.
The client now establishes a new SSH tunnel to the VSM agent server it received information about
from the VSM server. Port forwarding for VNC is always established, as well as other ports depending
on which local devices have been enabled. All tunnels are multiplexed over the same SSH connection.
The client now starts the VNC viewer, which will connect to the remote VNC server via the SSH
tunnel.
4
Vista de pagina 13
1 2 ... 9 10 11 12 13 14 15 16 17 18 19 ... 219 220

Comentarios a estos manuales

Sin comentarios