Hello, we have an issue with our Direct Access deployment (running on Windows Server 2012). Our users get and stay connected typically without issue. For a reason we do not know, some users will occasionally drop their Direct Access connection and gets stuck on connecting... (not sure why). However, when this happens, they begin to have a lot of DNS issues while Direct Access is not connected.
For example, we use a split brain DNS, so our public DNS name (ie. mycompany.com) has to be listed in our Direct Access DNS List in Direct Access (specified in page 2 "DNS" of the Step 3 Direct Access Wizard). Because of this, when they go off Direct Access, they can no longer access resources that are available externally (such as company website (www.mycompany.com) and OWA (mail.mycompany.com)). How do we configure this, to when Direct Access is not connected (ie. down), the system will just use DNS configured on the NIC (local DNS) and resolve the host name to the external IP address (which they can then access)?
We have tried both settings in the Direct Access wizard: "Use local name resolution if the name does not exist in DNS or DNS servers are unreachable when the client computer is on a private network (recommended)" and "Use local name resolution for any kind of DNS resolution error (least restrictive)"; neither of them make any difference and resolutions still fail.
Any thoughts on how to fix this? Thanks!
You don't mention what client OS you are having.
For the reconnect issue, if is Windows 7, have a look at http://support.microsoft.com/kb/2796313
Or take your pick from http://support.microsoft.com/kb/2883952
Regarding your issue on DNS, I do recommend that you put any known names that are accessible externally (e.g. mail.domain.tld) in the NRPT so that they are not accessed through the tunnel. This will help the client.
Hth, Anders Janson Enfo Zipper
Anders is very right for the NRPT (Name Resolution Policy Table), entries present there will always work, independently if DA is up or down.
An additional comment on DNS: have you tried overriding DNS resolution by checking "Use local DNS" in the DirectAccess Connectivity Assistant on the client? For Windows 7 this is an additional piece of software that first needs to be configured via GPO, then rolled out to the DirectAccess clients.