Dell Wyse Enhanced Ubuntu Linux T50 Manual de usuario descargar pdf (Pagina 22)

Chapter 3. Installation

3.3.4.2. DNS

After conﬁguring the relays, DNS must be conﬁgured so DNS queries for the hostnames of the ThinLinc

servers get different answers depending on the origin of the query. DNS queries originating from the

internal network should be answered with the real IP adresses of the servers, and DNS queries

originating from the outside network should be answered with the IP adresses on the ﬁrewall, where the

relays are listening.

In our example, if a host on the internal network is asking for the IP adress of the hostname

thinlinc.example.com it should get the IP address 10.0.0.12 as answer. If a outside host is asking for the

IP adress of the same hostname it should instead get the IP address x.12.253.1 as answer.

When conﬁgured this way, a client connecting from the internal network will communicate directly with

the ThinLinc servers, without the need to pass the ﬁrewall, while clients connecting from the outside will

pass through the ﬁrewall and the relays to communicate with the ThinLinc servers. This will ensure

optimal performance for clients from the internal network, at the same time lowering the load on the

ﬁrewall.

3.3.4.3. Conﬁguring the VSM Agents

Finally, after conﬁguring relays and DNS, the VSM agents must be conﬁgured to respond with the

correct hostname when asked by the VSM server what hostname the clients should connect to. The

default behaviour is to respond with the IP adress of the host, but that will not work in this case since

clients connecting from the external network won’t have any route to for example 10.0.0.13. Instead, the

VSM agents should be conﬁgured to respond with the hostnames that can be found in both the internal

and the external DNS.

This is done by setting the parameter /vsmagent/agent_hostname on each of the VSM agents in the

ThinLinc cluster. In our example, set /vsmagent/agent_hostname to tlagent1.example.com on the

machine with IP adress 10.0.0.13.

3.3.5. Using the ThinLinc HTML5 Client

If users are supposed to be able to connect using a web browser, using the ThinLinc HTML5 Browser

Client, they must be able to connect to port 300 on both the VSM server and on all VSM agents.

In the NAT/Split-DNS setup, relays must obviously be conﬁgured in the ﬁrewall for each ThinLinc

server and the port 300.

3.3.6. Other Services Required by ThinLinc Servers

In order for ThinLinc to function properly together with the rest of the network, they will need to

synchronize time with some internal or external time source. Linux machines use the Network Time

Protocol (NTP), so if there is one or several NTP servers on the internal network, the ThinLinc servers

will need to communicate with them. Otherwise, the ThinLinc servers should be conﬁgured to use some

external time source, and should be allowed to communicate with it.

1 2 ... 17 18 19 20 21 22 23 24 25 26 27 ... 219 220

Sin comentarios

Dell Wyse Enhanced Ubuntu Linux T50 Manual de usuario Pagina 22