Revision #2

Cause—On Forefront UAG activation, a timeout occurred and the Teredo interface could not be enabled.

Warning: Serious problems may occur if you modify the registry incorrectly using the Registry Editor or another method. These problems may require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

Solution 1— Ensure that IPv6 components are fully enabled as follows:

1. At an elevated command prompt, type reg query HKLM\SYSTEM\CurrentControlSet\Services\tcpip6\Parameters /v DisabledComponents.
   If the DisabledComponents registry value is not present, the command displays ERROR: The system was unable to find the specified registry key or value. In such a case, IPv6 components are enabled. 
2. If the DisabledComponents registry value is present, the command displays its value. If DisabledComponents is present and it is not 0, change it to 0.
3. Restart the Forefront UAG server.
4. At an elevated command prompt, type netsh int ipv6 show teredo. The output should show that the Teredo interface is Online and has the 1st external IPv4 address.
5. Reactivate Forefront UAG.

Solution 2— Manually change the Teredo state to online as follows:

1. At an elevated command prompt, type netsh int ipv6 set Teredo server <server FQDN or 1st external IPv4 address>.
2. Run netsh int ipv6 show teredo. The output should show that the Teredo interface is Online and has the 1st external IPv4 address.
3. Reactivate Forefront UAG.
4. If the Teredo interface is still offline, use the resulting error message from step 2 to troubleshoot the problem further.