I have been working on getting Direct Access up for months on Server 2012R2 and Windows 10 Enterprise clients and I am very, very close. In fact, clients can actually connect to internal file and desktop servers. However, their connection status is still in error. Get-DAConnectionStatus returns
Status: Error
Substatus: NameResolutionFailure
The report generated by the Windows 10 Direct Access on-board debugging elaborates with:
"Error: Corporate connectivity is not working. Windows is unable to resolve DNS names for probes. "
Our implementation is a single server, edge installation. We have native IPv6 internally so ISATAP disabled by policy throughout our environment. The NLS server resides on the DA server.
I can NSLOOKUP any of our internal servers (except the NLS website) using the DA server and can ping, net view, RDP, any that we have configured a return IPV6 route for (we don't want our DA clients accessing anything more that what is required).
I am perplexed by this error. I thought the whole point of the NLS (network location server) website was to NOT be accessible from outside. Why is this being looked up, and particularly, why after connectivity has already apparently been established? Can anyone shed light on this?