Figure 9-14 shows how the client
connects to your terminal servers or other RDP hosts. From the Internet, a client will establish
an SSL tunnel to the TS Gateway. Before a connection is granted, it checks the client credentials
with its Connection Authorization Policies (CAPs) to determine whether the client
is authorized to connect to the gateway. If authorized, the client can then request access to
the resources on the private network. The gateway then checks whether the requested resource
is listed in the gateway??™s Resource Authorization Policies (RAPs). If this authorization
check is successful, the gateway then connects to the requested resource. It completes
the process by establishing a secure tunnel between the client and requested resource. The
gateway acts exactly as a gateway should, by facilitating communication between the client
and resource. At this point, the user must authenticate to that resource just as it would
if it had attempted the connection from the local network. The only difference is that the
communication is being encapsulated over HTTPS traffic through the TS Gateway.
303 Chapter 9: Terminal Services
Hands-On Exercise: Installing and Configuring TS Gateway
TS Gateway relies on multiple pieces. This hands-on exercise will focus on a specific scenario
and then implement each piece as part of one big exercise. The scenario is straightforward:
We will allow a Windows Vista client to access a Windows Server 2008 terminal server called
WIN2K8TS through a Terminal Services Gateway, WIN2K8TSG, using the following steps:
1.
Pages:
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343