Defining the SecureNAT Client
The second defined client type in ISA Server 2006 is the SecureNAT client, which is essentially
any IP client that can be physically routed to the ISA server in one manner or
another. This includes any type of client with a TCP/IP stack that is forced to send its
traffic through the ISA server.
299 Outlining Client Access with ISA Server 2006
11
For example, a simple network with a single internal subnet that has the ISA server??™s internal
IP address listed as the default gateway for that subnet would see all client requests
from that network as SecureNAT client traffic, as shown in Figure 11.1.
The SecureNAT client scenario could also apply to more complicated networks with multiple
subnets and routers, provided that the routes defined in the network topology route
traffic through the ISA server, as shown in Figure 11.2.
SecureNAT clients are the easiest to work with: They do not require any special configuration
or client software. On the flip side, it is not possible to authenticate SecureNAT
clients automatically or to determine individual user accounts that may be sending traffic
through the ISA server.
Pages:
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509