

- TEREDO TUNNELING PSEUDO INTERFACE MISSING MICROSOFT WINDOWS 8
- TEREDO TUNNELING PSEUDO INTERFACE MISSING MICROSOFT WINDOWS
In the Windows PowerShell window, type ipconfig /flushdns and press ENTER. You will not see a default gateway listed for the Teredo tunnel adapter. If you do not see the Teredo section, enable Teredo with the following command: netsh interface Teredo set state enterpriseclient and then rerun the ipconfig command. If you look at the output of the ipconfig command, you should see a section for Tunnel adapter Teredo Tunneling Pseudo-Interface and then a description Microsoft Teredo Tunneling Adapter, with an IP address that starts with 2001: consistent with being a Teredo address. When the DirectAccess client is behind a NAT device and assigned a private IPv4 address, the preferred IPv6 transition technology is Teredo. On CLIENT1, open an elevated Windows PowerShell window, type ipconfig /all and press ENTER.Įxamine the output of the ipconfig command.ĬLIENT1 is now connected to the Internet from behind a NAT device and is assigned a private IPv4 address. Start EDGE1 and EDGE2 if they are not already running. If asked what type of network you want to define the current network, select Home Network. Prerequisitesīefore performing these tests, unplug CLIENT1 from the Internet switch and connect it to the Homenet switch. We recommend that you clear the Internet Explorer cache before performing these procedures to make sure that you are testing the connection and not retrieving the website pages from the cache. In order to demonstrate IP-HTTPS connectivity, Teredo is disabled on the client computers. Test IP-HTTPS connectivity-The second set of tests are performed when the DirectAccess client is configured to use IP-HTTPS. This is the automatic setting when the NAT device allows outbound access to UDP port 3544. Test Teredo connectivity-The first set of tests are performed when the DirectAccess client is configured to use Teredo. The following procedures are performed on both client computers: In this section you will perform the same tests performed when connecting using a 6to4 connection in the previous section. IP-HTTPS connections also fail if the web proxy performs outbound SSL inspection, due to the fact that the HTTPS session is terminated at the web proxy instead of the Remote Access server. If the web proxy requires authentication, the IP-HTTPS connection will fail. If Teredo access is not available, the DirectAccess client falls back to IP-HTTPS over outbound TCP port 443, which enables access through firewalls or web proxy servers over the traditional SSL port. If the NAT device enables outbound UDP port 3544 to the Remote Access server’s public IP address, then Teredo is used. When a DirectAccess client is connected to the Internet from behind a NAT device or a web proxy server, the DirectAccess client uses either Teredo or IP-HTTPS to connect to the Remote Access server.
TEREDO TUNNELING PSEUDO INTERFACE MISSING MICROSOFT WINDOWS 8
Applies To: Windows Server 2012 R2, Windows Server 2012, Windows 8
