Specifies resources on your intranet that are normally accessible to DirectAccess clients. Each entry is a string that identifies the type of resource and the location
of the resource.
Each string can be one of the following types:
- A DNS name or IPv6 address that NCA pings. The syntax is “PING:” followed by a fully qualified domain name (FQDN) that resolves to an IPv6 address, or an
IPv6 address. Examples: PING:myserver.corp.contoso.com or PING:2002:836b:1::1.
We recommend that you use FQDNs instead of IPv6 addresses wherever possible.
At least one of the entries must be a PING: resource.
- A Uniform Resource Locator (URL) that NCA queries with a Hypertext Transfer Protocol (HTTP) request. The contents of the web page do not matter. The syntax
is “HTTP:” followed by a URL. The host portion of the URL must resolve to an IPv6 address of a Web server or contain an IPv6 address.
Examples: HTTP:http://myserver.corp.contoso.com/ or HTTP:http://2002:836b:1::1/.
- A Universal Naming Convention (UNC) path to a file that NCA checks for existence. The contents of the file do not matter. The syntax is “FILE:” followed by a
UNC path. The ComputerName portion of the UNC path must resolve to an IPv6 address or contain an IPv6 address. Examples: FILE:\\myserver\myshare\test.txt or
You must configure this setting to have complete NCA functionality.
At least Windows Server 2008 R2 or Windows 7
In Registry Editor we can see the following changes:
For Enabled we get:
FullKeyPath : HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\NetworkConnectivityAssistant\Probes
ValueName : test
Value : test