Examples of using Directaccess client in English and their translations into Russian
{-}
-
Official
-
Colloquial
DirectAccess client connectivity methods.
Install Windows 7 on your DirectAccess clients and join them to your AD DS domain.
DirectAccess clients and servers must be members of an AD DS domain.
Create AD DS security groups that contain the computer accounts of your DirectAccess clients.
A DirectAccess client does not have access to the internal network.
In this step of the DirectAccess Setup wizard(step 1),you configure settings for DirectAccess clients.
A DirectAccess client cannot access a resource on the internal network.
The security groups containing the computer accounts of DirectAccess clients must exist before you configure step 1.
This allows the DirectAccess client to confirm that they are communicating with their intended servers.
To configure this scenario,you must modify the resulting connection security rules that are applied to DirectAccess clients.
DirectAccess clients use this URL to determine whether they are located on the Internet or the internal network.
You can require the use of smart cards when DirectAccess clients make a connection to the DirectAccess server.
A Network Load Balancing(NLB)cluster configured with two servers provide IPv6 connectivity to DirectAccess clients on the Internet.
Whether you want DirectAccess clients to perform end-to-end authentication and data protection for specific internal network servers?
Solution 2: To determine where tosend Domain Name System(DNS) name query requests, the DirectAccess client uses the NRPT.
Whether you want to restrict communication from DirectAccess clients to only those servers that are members of specific security groups?
A scalability model, which defines how many DirectAccess servers that you need to scale your DirectAccess infrastructures to meet the demands of DirectAccess clients.
Configure the location of an internal Web site so that DirectAccess client computers can determine when they are located on the internal network.
A DirectAccess client is a computer running Windows 7 or Windows Server 2008 R2 that is joined to an AD DS domain and uses IPv6 and Internet Protocol security(IPsec) to automatically initiate and maintain remote connectivity to an internal network from the Internet.
If the name of an internal network resource server is not matched to an entry in the NRPT, the DirectAccess client uses Internet-facing DNS servers and other methods to resolve the name.
To restrict the access of DirectAccess clients to the set of servers that are the members of the specified security groups, select Allow access to only those servers in the selected security groups.
Use a Network Address Translation-Protocol Translation(NAT-PT)device to translate traffic between your DirectAccess clients that are using IPv6 and servers and applications that can only use IPv4.
For the initial configuration of DirectAccess client settings in the DirectAccess snap-in, expand the DirectAccess node, click the Setup node, and then click Configure for step 1.
A DirectAccess server is a computer running Windows Server 2008 R2 that is joined to an AD DS domain and uses IPv6 andIPsec to respond to DirectAccess clients on the Internet and transparently connect them to an internal network.
The following table lists possible DirectAccess client configurations and their corresponding method of sending IPv6 traffic to the DirectAccess server.
Solution 1: To access a resource on the internal network, the resource must either be IPv6-capable, which requires that the computer and the application making the resourceavailable are both IPv6-capable, or that you use a Network Address Translation-Port Translation(NAT-PT) device between the DirectAccess client and the resource.
The end-to-edge access model allows DirectAccess clients to connect to all of the resources inside the internal network but does not use IPsec to protect the end-to-end communication with internal network servers.
This topic provides information about the components of a DirectAccess deployment, DirectAccess client connectivity methods, firewall configuration for DirectAccess traffic, and integration with smart cards.
With this setting enabled, DirectAccess clients and the specific internal network servers perform end-to-end IPsec authentication, but do not use IPsec protection to provide data integrity or privacy for the packets sent between DirectAccess clients and internal network servers.
On the DirectAccess Application Server Setup page, if you do not want DirectAccess clients to perform end-to-end authentication with internal network servers, select Require no additional end-to-end authentication.