WARNING: Two consecutive IPv4 addresses have been detected on the Remote Access server, and Teredo is enabled. Once complete, you’ll receive a warning message that states: To enable Teredo support after you’ve configured DirectAccess, add the second consecutive public IPv4 address to the external network interface and then execute the following PowerShell command from an elevated command prompt.

If you neglect to add the second consecutive public IPv4 address to the external network interface and configure DirectAccess, the installation will complete successfully without enabling Teredo support and Teredo will not appear in the list of services operations status, as shown here. When you configure DirectAccess for the first time, Teredo will automatically be configured if the installation detects the proper requirements for it. To support Teredo, the DirectAccess server must be configured with two consecutive public IPv4 addresses. Note: It is generally recommended that the 6to4 IPv6 transition protocol be proactively disabled. When the DirectAccess server is edge facing with public IPv4 addresses assigned to the external interface, the 6to4 and Teredo IPv6 transition protocols are also supported. When the DirectAccess server is located in a perimeter or DMZ network behind a NAT device, only the IP-HTTPS IPv6 transition protocol is used. DirectAccess leverages IPv6 transition protocols to enable clients to connect to the DirectAccess server when both are located on the IPv4 Internet.

How to enable teredo in windows 10