Microsoft Direct Access stuck on connecting

[swarohi]

When I bring up the Direct Access panel in settings, it says connecting under the connection name but goes no further than that. It is definitely not working as I cannot open any networked drives etc.

 

There are no errors on the remote management tool on Server 2012.

 

Any suggestions for troubleshooting this issue will be much appreciated!

 

Thanks a bunch .

[RobD]

Its either not building the DA tunnels or DA is actually working in the background and the probe that tells the NCA is just failing.

 

If DirectAccess is actually not working, then try a reboot or restart the IP Helper service on the client computer.

 

Also a hotfix for Windows server 2012 R2:

 

https://support.microsoft.com/en-us/kb/2883952

Edited July 7, 2017 by RobD
words

[swarohi]

Restarting the IP helper service did not work. I will try the hotfixes on the server after a meeting that's about to start, but from the descriptions, they don't sound like the problem I am having.

 

[RobD]

This is pretty interesting:

https://blogs.technet.microsoft.com/ripom/2014/07/25/direct-access-status-always-connecting-on-windows-8/

[deano]

How have you deployed DirectAccess? IP-HTTPS?

[dezt]

If you are using IP-HTTPS try disabling teredo using

netsh int teredo set state disabled

and also disable 6to4 using

netsh int 6to4 set state disabled

on your client.

[mattpant]

Sorry to bring up an old thread, but thought it was best to pop it here than to start of a new thread with a similar issue...

 

I have DirectAccess setup and working fine - but I have a particular client accessing direct access which will work, then a few day will just stop connecting - with the message showing as "Connecting" but it never connects - other clients offsite can still connect up fine.

 

In order to "fix" the problem with this client - when it's back connected locally to our network - I run GPUpdate / force and restart the machine it's then able to work remotely again for a few more days - until it breaks again! - I'm not 100% sure what fixing it when I run gpupdate / force but it's annoying as obviously they can't access the network whilst away from site.

 

I'd love to find the source of the problem and get it working all the time (or at least see if there's a way they can fix things whilst being away from the site)

 

Yesterday I had the device with me whilst it was in a non-working state and ran the DirectAccess Troubleshooter tool - this is where I think the source of the problem is when it's not working, but I can't find any reference to this error anywhere online...

 

The IPHTTPS interface is not operational, last error code is 0x3e3.

 

The IPHTTPS interface status is failed to connect to the IPHTTPS server. Waiting to reconnect.

 

After doing the gpupdate / force and restart I then get:

 

The IPHTTPS interface is operational.

The IPHTTPS interface status is IPHTTPS interface active.

 

And Direct Access connects fine. (For at least a few days anyway!)

 

Any help / pointers would be greatly appreciated!

 

Thanks

 

Matt

[TonyH]

We are seeing this same issue and wondered if you found what was causing it.