Hi All,
I'm trying to re-set up DirectAccess for our internal users as the old environment just stopped working one day. The DA servers is Windows2012R2 with a single NIC behind an Edge router. Our internal domain name is not reachable from the outside, but we do have a public domain name that points to the internal server. On the DA server, all dashboard diagnostics show green so I'm fairly confident that the issue is with the client machine.
On the client, I've confirmed that it has the proper security group and GPO. It passes the WMI filtering as well. When I connect to a network that's not on the domain, the DirectAccess service tries to connect but never fully establishes a connection. I'm posting the output of the DirectAccess Client Troubleshooting Tool and have changed the internal and external domain names for security. Any help would be greatly appreciated.
[4/13/2016 2:47:07 PM]: User canceled the tests.[4/13/2016 2:47:08 PM]: In worker thread, going to start the tests.
[4/13/2016 2:47:08 PM]: Running Network Interfaces tests.
[4/13/2016 2:47:08 PM]: VMware Network Adapter VMnet1 (VMware Virtual Ethernet Adapter for VMnet1): fe80::3426:769:fbee:6e74%27;: 192.168.52.1/255.255.255.0;
[4/13/2016 2:47:08 PM]: No default gateway found for VMware Network Adapter VMnet1.
[4/13/2016 2:47:08 PM]: VMware Network Adapter VMnet8 (VMware Virtual Ethernet Adapter for VMnet8): fe80::cd01:47d0:a9f8:834a%6;: 192.168.135.1/255.255.255.0;
[4/13/2016 2:47:08 PM]: No default gateway found for VMware Network Adapter VMnet8.
[4/13/2016 2:47:08 PM]: Wi-Fi (Marvell AVASTAR Wireless-AC Network Controller): 2602:304:b319:d780:1d81:5c4e:f26f:5077;: 2602:304:b319:d780:edec:6b68:55eb:5192;: fe80::1d81:5c4e:f26f:5077%21;: 192.168.1.240/255.255.255.0;
[4/13/2016 2:47:08 PM]: Multiple default gateways found for Wi-Fi!
[4/13/2016 2:47:08 PM]: Teredo Tunneling Pseudo-Interface (Teredo Tunneling Pseudo-Interface): 2001:0:9d38:90d7:1036:f29:b4ce:6287;: fe80::1036:f29:b4ce:6287%17;
[4/13/2016 2:47:08 PM]: No default gateway found for Teredo Tunneling Pseudo-Interface.
[4/13/2016 2:47:08 PM]: Warning - this client computer has multiple default gateways defined!
[4/13/2016 2:47:08 PM]: Wi-Fi has configured the default gateway fe80::3e36:e4ff:fe66:7ca0%21.
[4/13/2016 2:47:08 PM]: Default gateway fe80::3e36:e4ff:fe66:7ca0%21 for Wi-Fi replies on ICMP Echo requests, RTT is 3 msec.
[4/13/2016 2:47:08 PM]: Wi-Fi has configured the default gateway 192.168.1.254.
[4/13/2016 2:47:08 PM]: Default gateway 192.168.1.254 for Wi-Fi replies on ICMP Echo requests, RTT is 1 msec.
[4/13/2016 2:47:08 PM]: Received a response from the public DNS server (8.8.8.8), RTT is 67 msec.
[4/13/2016 2:47:08 PM]: Received a reply from the public DNS server (2001:4860:4860::8888), RTT is 66 msec.
[4/13/2016 2:47:08 PM]: Running Inside/Outside location tests.
[4/13/2016 2:47:08 PM]: NLS is https://DirectAccess-NLS.<internal name>.com:62000/insideoutside.
[4/13/2016 2:47:08 PM]: NLS is not reachable via HTTPS, the client computer is not connected to the corporate network (external) or the NLS is offline.
[4/13/2016 2:47:08 PM]: NRPT contains 2 rules.
[4/13/2016 2:47:08 PM]: Found (unique) DNS server: fded:4b9:e759:3333::1
[4/13/2016 2:47:08 PM]: Send an ICMP message to check if the server is reachable.
[4/13/2016 2:47:14 PM]: DNS Server fded:4b9:e759:3333::1 does not reply on ICMP Echo requests.
[4/13/2016 2:47:20 PM]: DNS Server fded:4b9:e759:3333::1 does not reply on ICMP Echo requests.
[4/13/2016 2:47:20 PM]: Running IP connectivity tests.
[4/13/2016 2:47:20 PM]: The 6to4 interface service state is default.
[4/13/2016 2:47:20 PM]: Teredo inferface status is online.
[4/13/2016 2:47:20 PM]: The configured DirectAccess Teredo server is win10.ipv6.microsoft.com..
[4/13/2016 2:47:20 PM]: The IPHTTPS interface is operational.
[4/13/2016 2:47:20 PM]: The IPHTTPS interface status is IPHTTPS interface active.
[4/13/2016 2:47:20 PM]: IPHTTPS is used as IPv6 transition technology.
[4/13/2016 2:47:20 PM]: The configured IPHTTPS URL is https://directaccess.<external name>.com:443.
[4/13/2016 2:47:20 PM]: IPHTTPS has a single site configuration.
[4/13/2016 2:47:20 PM]: IPHTTPS URL endpoint is: https://directaccess.<external name>.com:443.
[4/13/2016 2:47:20 PM]: Successfully connected to endpoint https://directaccess.<external name>.com:443.
[4/13/2016 2:47:20 PM]: No response received from <internal name>.com.
[4/13/2016 2:47:20 PM]: Running Windows Firewall tests.
[4/13/2016 2:47:20 PM]: The current profile of the Windows Firewall is Public.
[4/13/2016 2:47:20 PM]: The Windows Firewall is enabled in the current profile Public.
[4/13/2016 2:47:20 PM]: The outbound Windows Firewall rule Core Networking - Teredo (UDP-Out) is enabled.
[4/13/2016 2:47:20 PM]: The outbound Windows Firewall rule Core Networking - IPHTTPS (TCP-Out) is enabled.
[4/13/2016 2:47:20 PM]: Running certificate tests.
[4/13/2016 2:47:20 PM]: No usable machine certificate found.
[4/13/2016 2:47:20 PM]: Found 0 machine certificates on this client computer.
[4/13/2016 2:47:20 PM]: Running IPsec infrastructure tunnel tests.
[4/13/2016 2:47:20 PM]: Failed to connect to domain sysvol share \\<internal name>.com\sysvol\<internal name>.com\Policies.
[4/13/2016 2:47:20 PM]: Running IPsec intranet tunnel tests.
[4/13/2016 2:47:20 PM]: Successfully reached fded:4b9:e759:1000::1, RTT is 11 msec.
[4/13/2016 2:47:20 PM]: Successfully reached fded:4b9:e759:1000::2, RTT is 10 msec.
[4/13/2016 2:47:20 PM]: Failed to connect to HTTP probe at http://directaccess-WebProbeHost.<internal name>.com.
[4/13/2016 2:47:20 PM]: Successfully reached HTTP probe at http://directaccess.<external name>.com/.
[4/13/2016 2:47:20 PM]: Running selected post-checks script.
[4/13/2016 2:47:20 PM]: No post-checks script specified or the file does not exist.
[4/13/2016 2:47:20 PM]: Finished running post-checks script.
[4/13/2016 2:47:20 PM]: Finished running all tests.