Error Message Applying the Settings of the DirectAccess Setup Wizard
Updated: April 15, 2010
Applies To: Windows Server 2008 R2
When you click Apply from the DirectAccess Review dialog box, the DirectAccess Server Setup Wizard configures the DirectAccess server and a set of Group Policy objects and their settings. The following table lists the most common types of error messages that you might encounter during this step.
| Error message | Error condition and the steps to correct |
|---|---|
Registration of Intra-Site Automatic Tunnel Addressing Protocol (ISATAP) in Domain Name System (DNS) failed. |
The DirectAccess server computer cannot use DNS dynamic update to create an Address (A) record in its DNS server for the name ISATAP. This most commonly occurs when using a DNS server that is not running Windows. Troubleshoot DNS dynamic update between the DirectAccess server and its configured DNS server. |
Membership in the local Administrators group, or equivalent, is the minimum required to complete this operation. |
You must log on to the DirectAccess server computer with a user account that has local administrator privileges. |
DirectAccess server configuration failed because the IP-HTTPS interface cannot be configured. |
The IP-HTTPS interface is not active. Use the netsh interface httpstunnel show interfaces command to display the state of the IP-HTTPS interface. |
DirectAccess server configuration failed because the 6to4 interface is not operational. |
The 6to4 service is not active. Use the netsh interface 6to4 show state command to display the state of the 6to4 service. If needed, start the 6to4 service with the netsh interface 6to4 set state enabled command. |
DirectAccess server configuration failed because the Teredo interface is not operational. |
The Teredo service is not active. Use the netsh interface teredo show state command to display the state of the Teredo service. If needed, start the Teredo service with the netsh interface teredo set state default command. |
If you see the DirectAccess server configuration failed. message, ensure that the Internet and intranet interfaces have been configured with different connection-specific DNS suffixes. The connection-specific DNS suffix of the intranet interface should be the DNS suffix of the Active Directory domain of the DirectAccess server. A specific DNS suffix for the Internet interface is not needed, but it must be different than the DNS suffix of the intranet interface.
If you see the DirectAccess server configuration failed. message, see the %SystemRoot%\Tracing\DASetup.log file for additional information about events and errors encountered by the DirectAccess Setup Wizard. For example, if the DirectAccess server cannot register the IPv6 Address (AAAA) record for corpConnectivityHost.DomainName and the IPv6 address of ::1 with a DNS server that is not running Windows, the DirectAccess Setup Wizard displays the DirectAccess server configuration failed. message