Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Wednesday, April 25, 2018 6:36 PM
Hello,
We have DirectAccess in use for about 100client computers. Its single NIC PKI system with windows 10 clients. Most of the clients work fine but there are few that have some really weird connection issues. DA will remain in connecting state when exiting internal network and wont connect. However it will connect if you restart ip helper service. BUT it only works for few seconds to few mins. Totally random. Once it disconnects, Get-DAconnectionStatus shows as "couldnotcontactdaserver". Then if you restart the service again it connects fine and same thing repeats itself.
iphttps interface also looks fine even when its in connecting state
PS netsh interface https show int
Interface IPHTTPSInterface (Group Policy) Parameters
Role : client
URL : https://XXXXXXXXX:443/IPHTTPS
Last Error Code : 0x0
Interface Status : IPHTTPS interface active
I've been battling this but can't seem to find a resolution.. Any help would be appreciated.
All replies (4)
Thursday, April 26, 2018 4:12 AM
Hi,
Thanks for your question.
IP Helper service: Provides tunnel connectivity using IPv6 transition technologies (6to4, ISATAP, Port Proxy, and Teredo) and IP-HTTPS. As indicated in the service description, the IP Helper service is leveraged in IPv4-to-IPv6 transitions. Therefore, it's important for Direct Access connection.
Based on my experience, you could try the following suggestions to see if it will help.
1）When the DA client disconnects or on connecting state, please type the command ipconfig /all on the client to check if its tunnel adapter exists or generates on the result. If the tunnel doesn’t apprear, the issue cause may be that the service or corresponding components get failure on local client.
If this problem, you may try repairing the client system service through SFC tool.
Additional important information:
It is always a good habit to back up the system prior to any component changes. So certainly you can back up your system before proceeding just in case of any unexpected disaster.
2）Please try this link to troubleshooting with powershell command.
Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
3）Besides, please make sure the IP Helper Service is configured to automatic startup on the client.
Reference links:
System Services
http://technet.microsoft.com/en-us/library/dd349799(v=ws.10).aspx
IP Helper
http://msdn.microsoft.com/en-us/library/windows/desktop/aa366073(v=vs.85).aspx
Hope above information can help you.
Highly appreciate your effort and time. If you have any questions and concerns, please feel free to let me know.
Best regards,
Michael
Please remember to mark the replies as an answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected]
Monday, April 30, 2018 10:09 AM
Hi,
How are things going on? Was your issue resolved?
Please let me know if you would like further assistance.
Best regards,
Michael
Please remember to mark the replies as an answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected]
Sunday, May 6, 2018 10:30 AM
Hi,
How are things going on? Was your issue resolved?
Please let me know if you would like further assistance.
Best regards,
Michael
Please remember to mark the replies as an answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected]
Tuesday, May 8, 2018 2:02 PM
Hi,
How are things going on? Was your issue resolved?
Please let me know if you would like further assistance.
Best regards,
Michael
Please remember to mark the replies as an answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected]