locked
DirectAccess works but shows "Connecting" RRS feed

 , 
 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I have a strange issue with a Windows Server 2012 DirectAccess deployment and a Windows 8.1 client. The client has corporate connectivity via DirectAccess but the status of the connection always shows "Connecting" even though the connection is OK. When it is connected to VPN the status shows correctly. It is not much of a problem, rather annoying. What can I do to try to trace this somehow?


    Monday, May 26, 2014 6:01 PM

Answers

  • Question
    Sign in to vote
    1
    Sign in to vote

    The DirectAccess network tool on the clients will show "Connecting" until they can successfully contact the things that it is being told to contact, which are defined inside the NCA settings inside Step 1 of the DirectAccess wizards. Re-visit step 1, and take a look at the NCA settings. Whatever probes are defined here, the NCA tool will only show Connected once it has successfully validated these probes.

    The wizard likes to auto-insert a "webprobehost" entry. It is supposed to then register webprobehost into your internal DNS and point it back at the DirectAccess server, but this doesn't always work well. If webprobehost is defined in the NCA settings, make sure that you have a corresponding webprobehost entry in your internal DNS, and make sure it points to a server that is online so that it can verify that probe.

    Thursday, May 29, 2014 1:02 PM

All replies

  • Question
    Sign in to vote
    1
    Sign in to vote

    Have you collected the logs from the 8.1 machine? You can access them from the modern control panel, under Network. Make sure you've set an email address in the DA config.

    Monday, May 26, 2014 9:37 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    The DirectAccess network tool on the clients will show "Connecting" until they can successfully contact the things that it is being told to contact, which are defined inside the NCA settings inside Step 1 of the DirectAccess wizards. Re-visit step 1, and take a look at the NCA settings. Whatever probes are defined here, the NCA tool will only show Connected once it has successfully validated these probes.

    The wizard likes to auto-insert a "webprobehost" entry. It is supposed to then register webprobehost into your internal DNS and point it back at the DirectAccess server, but this doesn't always work well. If webprobehost is defined in the NCA settings, make sure that you have a corresponding webprobehost entry in your internal DNS, and make sure it points to a server that is online so that it can verify that probe.

    Thursday, May 29, 2014 1:02 PM
  • Question
    Sign in to vote
    0
    Sign in to vote


    Hi,

    Just want to confirm the current situations.

    Please feel free to let us know if you need further assistance.

    Regards.

    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

    Wednesday, June 4, 2014 6:44 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    I am sorry I delayed my reply so much. Indeed, the issue was exactly what Jordan Krause suggested - the DirectAccess-WebProbeHost was specified, but did not exist as a DNS record. I suppose the record might have been scavenged by DNS at some point. I created manually a static entry and now the connection shows Connected when through DirectAccess. Thank you for the accurate information.
    Monday, August 11, 2014 2:11 PM