Problem connecting Direct Access clients


hi,

i'm trying days connect clients (windows 10 ent) direct access, cannot make it. have tried 3 possible configuration, , gives same errors in direct access client troubleshooting tool. debug error given below. have split dns scenario.

[6/23/2017 8:39:54 am]: in worker thread, going start tests.
[6/23/2017 8:39:54 am]: running network interfaces tests.
[6/23/2017 8:39:54 am]: wi-fi (intel(r) dual band wireless-ac 7265): 192.168.1.114/255.255.255.0;
[6/23/2017 8:39:54 am]: default gateway found wi-fi.
[6/23/2017 8:39:54 am]: iphttpsinterface (iphttpsinterface): 2002:2e63:918d:1000:50a7:53e9:5244:9ed5;: 2002:2e63:918d:1000:2dc8:36ba:59f7:8198;: fe80::50a7:53e9:5244:9ed5%8;
[6/23/2017 8:39:54 am]: no default gateway found iphttpsinterface.
[6/23/2017 8:39:54 am]: wi-fi has configured default gateway 192.168.1.1.
[6/23/2017 8:39:54 am]: default gateway 192.168.1.1 wi-fi replies on icmp echo requests, rtt 1 msec.
[6/23/2017 8:39:54 am]: received response public dns server (8.8.8.8), rtt 19 msec.
[6/23/2017 8:39:54 am]: public dns server (2001:4860:4860::8888) not reply on icmp echo requests, request or response maybe filtered?
[6/23/2017 8:39:54 am]: running inside/outside location tests.
[6/23/2017 8:39:54 am]: nls https://nls.domain.com/.
[6/23/2017 8:39:54 am]: nls not reachable via https, client computer not connected corporate network (external) or nls offline.
[6/23/2017 8:39:54 am]: nrpt contains 4 rules.
[6/23/2017 8:39:54 am]:   found (unique) dns server: 2002:2e63:918d:3333::1
[6/23/2017 8:39:54 am]:   send icmp message check if server reachable.
[6/23/2017 8:39:54 am]: dns server 2002:2e63:918d:3333::1 online, rtt 4 msec.
[6/23/2017 8:39:54 am]: running ip connectivity tests.
[6/23/2017 8:39:54 am]: 6to4 interface disabled.
[6/23/2017 8:39:55 am]: teredo inferface status offline.
[6/23/2017 8:39:55 am]:  the configured directaccess teredo server win10.ipv6.microsoft.com..
[6/23/2017 8:39:55 am]: iphttps interface operational.
[6/23/2017 8:39:55 am]:  the iphttps interface status iphttps interface active.
[6/23/2017 8:39:55 am]: iphttps used ipv6 transition technology.
[6/23/2017 8:39:55 am]:  the configured iphttps url https://dacs.domain.com:443.
[6/23/2017 8:39:55 am]: iphttps has single site configuration.
[6/23/2017 8:39:55 am]: iphttps url endpoint is: https://dacs.domain.com:443.
[6/23/2017 8:39:55 am]:  successfully connected endpoint https://dacs.domain.com:443.
[6/23/2017 8:40:07 am]: no response received domain.com.
[6/23/2017 8:40:07 am]: running windows firewall tests.
[6/23/2017 8:40:07 am]: current profile of windows firewall public.
[6/23/2017 8:40:07 am]: windows firewall enabled in current profile public.
[6/23/2017 8:40:07 am]: outbound windows firewall rule core networking - teredo (udp-out) enabled.
[6/23/2017 8:40:07 am]: outbound windows firewall rule core networking - iphttps (tcp-out) enabled.
[6/23/2017 8:40:07 am]: running certificate tests.
[6/23/2017 8:40:07 am]: found 1 machine certificates on client computer.
[6/23/2017 8:40:07 am]: checking certificate cn=datest.domain.com serial number [20000002881361078d21ccf522000000000288].
[6/23/2017 8:40:07 am]:  the certificate [20000002881361078d21ccf522000000000288] contains eku client authentication.
[6/23/2017 8:40:07 am]:  the trust chain certificate [20000002881361078d21ccf522000000000288] sucessfully verified.
[6/23/2017 8:40:07 am]: running ipsec infrastructure tunnel tests.
[6/23/2017 8:40:07 am]: failed connect domain sysvol share \\domain.com\sysvol\domain.com\policies.
[6/23/2017 8:40:07 am]: running ipsec intranet tunnel tests.
[6/23/2017 8:40:07 am]: reached 2002:2e63:918d::2e63:918d, rtt 4 msec.
[6/23/2017 8:40:07 am]: reached 2002:2e63:918d:5::1, rtt 4 msec.
[6/23/2017 8:40:07 am]: running selected post-checks script.
[6/23/2017 8:40:07 am]: no post-checks script specified or file not exist.
[6/23/2017 8:40:07 am]: finished running post-checks script.
[6/23/2017 8:40:07 am]: finished running tests.

thank help.


alfa21

hi alfa21

>>failed connect domain sysvol share

it possible win10 machines able access internal resources nls detection , therefore believe still internal.

you try configure dnssec through gpo of client manually.

for reference:

https://social.technet.microsoft.com/forums/en-us/4982999b-b4dc-4140-9602-11049e0c4124/direct-access-configuration-problem-failed-to-connect-to-domain-sysvol-share?forum=winservernis

best regards,

candy


please remember mark replies answers if help.
if have feedback technet subscriber support, contact tnmff@microsoft.com.



Windows Server  >  Windows Server 2016 General



Comments

Popular posts from this blog

CRL Revocation always failed

Failed to query the results of bpa xpath

0x300000d errors in Microsoft Remote Desktop client