Consider the following scenario:
- You deploy DirectAccess on a computer that is running Windows Server 2012 in a network environment. The environment contains some intranet resources that only have IPv4 addresses.
- You enable external load balancing in the environment.
- A DirectAccess client connects from the Internet to internal resources that only have IPv4 addresses.
In this scenario, DNS64 does not resolve the computer names of the internal resources. Therefore, clients cannot connect to the internal resources.
If you’re running into this problem, check out the KB article and download the fix at:
DEBRA LITTLEJOHN SHINDER
MVP (Enterprise Security)