none
Windows 10 Direct Access Workplace Connection keeps Connecting

    Question

  • Hi,

    I'm using two Win 10 computers with Win 10 1803. As far as I can tell both computers have the same configuration and I'm using the same user. Though only one computer has since one of the last Windows Updates a reliable Direct Access connection to our Windows Server 2016 Direct Access Server. I ran the build-in the Direct Access troubleshooter, but it couldn't identify the issue. The log tells what I pasted below

    What can I do for further analysis? Is anyone else experiencing this issue with the latest Windows 10 Updates?

    Any advice in advance

    John

    ------------------------------------------------------------------------------

    PrintConnection to a Workplace Using DirectAccess Publisher details 

    No issues detected
    Detection details Expand 

    InformationalDiagnostics Information (IPHTTPS) 
    Details about IPHTTPS diagnosis: 


    Interface iphttpsinterface Parameters
    ------------------------------------------------------------
    Total bytes received       : 907726
    Total bytes sent           : 523344

    Interface IPHTTPSInterface (Group Policy)  Parameters
    ------------------------------------------------------------
    Role                       : client
    URL                        : https://ras.mydomain.com:443/IPHTTPS
    Last Error Code            : 0x0
    Interface Status           : IPHTTPS interface active 

     
     
    InformationalDiagnostics Information (Teredo) 
    Details about Teredo diagnosis: 

    Teredo Parameters
    ---------------------------------------------
    Type                    : disabled
    Server Name             : win1711.ipv6.microsoft.com.
    Client Refresh Interval : 30 seconds
    Client Port             : unspecified
    State                   : offline
    Error                   : none

     
     
    InformationalDiagnostics Information (IPHTTPS) 
    Details about IPHTTPS diagnosis: 


    Interface iphttpsinterface Parameters
    ------------------------------------------------------------
    Total bytes received       : 908774
    Total bytes sent           : 524104

    Interface IPHTTPSInterface (Group Policy)  Parameters
    ------------------------------------------------------------
    Role                       : client
    URL                        : https://ras.mydomain.com:443/IPHTTPS
    Last Error Code            : 0x0
    Interface Status           : IPHTTPS interface active 

     
     
    InformationalDiagnostics Information (Teredo) 
    Details about Teredo diagnosis: 

    Teredo Parameters
    ---------------------------------------------
    Type                    : disabled
    Server Name             : win1711.ipv6.microsoft.com.
    Client Refresh Interval : 30 seconds
    Client Port             : unspecified
    State                   : offline
    Error                   : none

     
     
    InformationalNetwork Diagnostics Log 
    File Name:  B00AFB88-6483-4AD3-85F7-942279952698.Diagnose.0.etl 
     
    InformationalOther Networking Configuration and Logs 
    File Name:  NetworkConfiguration.cab 
     
    Collection information 
    Computer Name:  MyPC
    Windows Version: 10.0 
    Architecture: x64 
    Time: Thursday, May 31, 2018 1:10:13 AM 

    Publisher details Expand 

    Windows Network Diagnostics 
    Detects problems with network connectivity. 
    Package Version: 4.0 
    Publisher: Microsoft Windows 
    Connection to a Workplace Using DirectAccess 
    Find and fix problems with connecting to your workplace network using DirectAccess. 
    Package Version: 3.0 
    Publisher: Microsoft Corporation 


    John

    Wednesday, May 30, 2018 11:18 PM

All replies

  • Hi,

    The Diagnostic log shows a lot more than this ;-)
    According to your post, the HTTPS Tunnel is up so your client is able to join the DirectAccess server.

    After that, several things can explains the message.
    Most of the time, a  DA client that stays on "Connecting" is because it can't contact the NCA probes defined in the Remote Client part of the server's configuration.

    Check in the diagnostic log if the client can validate them.

    Are you able to ping your internal servers ?

    Gérald

    Monday, June 04, 2018 7:52 PM