Network problems with DirectAccess 2012


  • Within the corporation we are having a problem with the implementation of direct access, the problem is  when computers are in the internal network, somehow lose proper communication with the local domain, and server resources in the network adapter loses the network and shows or places another network, eg network 2 instead  the network domain, the solution that we found is to disable direct access policies (DirectAccess Client Settings, DirectAccess Server Settings) and rejoining computers the domain, but if we re-enable the policies the problem happens again.


    Friday, June 21, 2013 3:24 PM


All replies

  • Hi,

    The DirectAccess Design, Deployment, and Troubleshooting Guides:

    Would you please provide us unedited ipconfig /all information both your DA and client when the problem occur or not.


    Alex Lv

    Monday, June 24, 2013 8:24 AM
  • Hi,

    It sounds like that the clients cannot see the server configured af the "Network Location Server" (NLS) on the DirectAccess server. Have you configured a NLS server with at corresponding SSL certificate? 

    When you experience the problem and if you have "DirectAccess Connectivity Assistant" installed just right click on in in the notification area next to the clock and select "Use local DNS resolution".

    Alternatively stop the "IP Helper" service on the client(s).

    Then just disable the DA policy on the Domain Controller and do a "GPUPDATE /Force" on each client with the problem.

    There should be no need to rejoin the computers to the domain.

    Thomas Forsmark Soerensen

    Thursday, August 15, 2013 2:04 PM