DirectAccess + AirCard + docked to corporate LAN = OUTSIDE Network

Question

We're deploying laptops and tablets with windows 8.1 and are having an issue where the network location service determines the system is "outside" and DirectAccess constantly attempts to connect when the system is connected to the domain network. 
The odd behavior is that the domain network connection takes the name of the wifi/air card connection they were using when the error happened.
We're at a loss to figure out what is causing this.
We have verified that the DHCP server is handing out and the client receives appropriate IP address, netmask, and DNS server information.
DNS appears to resolve in IE but the same name will fail a ping with a could not be found error.  Run nslookup and it connects to the name server and returns names.
Sometimes all it takes to trigger the error is to dock a system with an active air card connection (DirectAccess connected) and then the system determines the lan connection is OUTSIDE the network and the devices no longer act as if they are domain connected.
We thought there might be an issue with the CRL list on the cert associated with the NLS server as the prior admin failed to configure our PKI infrastructure to post a CRL.  After fixing that the problem still has not gone away.
So far the only solution that works (and that is temporary) is to remove the system from the domain and add it again.  We have a couple of trouble free users who meticulously disconnect their air card or wifi sessions prior to reconnecting to the corporate
network.
Has anyone else seen this issue?  better yet, has it been solved? :)
TIA for any help you can provide!

Answer 1

Hi   VinceDude,
The main issue is that the network location of the client in the domain is identified wrongly,right?
Would you please share us with the exact details of the error? Have you checked the Event Viewer both from the client and the server for related error information?
This path may be helpful
Event Viewer \Applications and Services logs\Microsoft \Windows \NetworkProfile
Here is a KB showing  a similar symptom ,is this symptom corresponding with yours?（Win8.1  takes with the same registry path）：
A computer cannot identify the network when the computer is running Windows Vista, Windows Server 2008, Windows 7, or Windows Server 2008 R2, and is a member of a child domain
https://support.microsoft.com/kb/980873?wa=wsignin1.0
Meanwhile here is a link  showing us how NLA determines a network profile:
http://blogs.technet.com/b/networking/archive/2010/09/08/network-location-awareness-nla-and-how-it-relates-to-windows-firewall-profiles.aspx
Best regards