How to Configure and Troubleshoot Teredo Tunneling in Windows 11 Using PowerShell

In modern computer networking, transitioning from IPv4 to IPv6 often presents significant routing challenges, particularly across legacy home routers, corporate firewalls, and carrier-grade Network Address Translation (CGNAT) gateways that do not natively route IPv6 traffic. To bridge this gap, Microsoft Windows includes built-in support for Teredo—an IPv6 transition protocol (RFC 4380) that encapsulates IPv6 packets within IPv4 User Datagram Protocol (UDP) datagrams (typically using destination port 3544).

In Windows 11, Teredo plays a pivotal role in consumer and enterprise applications alike, including Xbox network multiplayer, Remote Assistance, peer-to-peer communications, and DirectAccess connectivity. When Teredo encounters strict symmetric NAT firewalls, disabled network services, or stale server endpoints, peer-to-peer connectivity fails with cryptic NAT errors. Utilizing the native NetTCPIP PowerShell module allows administrators to inspect Teredo client states, configure relay servers, and remediate NAT traversal failures directly from the terminal.

Understanding Teredo Operational States and NAT Types

When Windows evaluates local network conditions to establish an encapsulated IPv6 tunnel, the Teredo client progresses through several internal operational states:

  • Disabled: The Teredo interface is explicitly turned off by policy or operating system configuration.
  • Client: Teredo is active only when an application specifically requests IPv6 connectivity across a non-domain network.
  • EnterpriseClient: Forces Teredo to remain active and negotiate tunneling even when the workstation is joined to an Active Directory domain (by default, Windows disables Teredo on domain-joined machines to prioritize native enterprise IPv6).
  • Dormant: The client is configured but waiting for active IPv6 peer-to-peer traffic before binding network sockets.

Furthermore, Teredo classifies the local router’s NAT topology: Cone (ideal open connectivity), Restricted, Port Restricted (moderate NAT), or Symmetric (strict NAT, which inherently blocks peer-to-peer Teredo encapsulation).

Auditing Active Teredo Configuration via PowerShell

To inspect the current status and server parameters of the Windows Teredo interface, launch PowerShell as an Administrator and execute:

Get-NetTeredoConfiguration

The console outputs a structured object containing key diagnostic parameters:

Type                    : Client
ServerName              : win1910.ipv6.microsoft.com.
RefreshInterval         : 30
ClientPort              : 0
ServerShunt             : False

To view the operational tunneling state (including NAT classification and IP resolution) using native Windows networking diagnostics:

netsh interface teredo show state

Inspect the State line. Healthy connections report qualified or dormant. If the state indicates offline, failed to resolve server name, or blocked, remediation is required.

Configuring Teredo Client Type for Enterprise and Home Systems

On domain-joined machines, corporate virtual private networks (VPNs), or managed laptops, Windows automatically suppresses Teredo by default. To force Teredo to remain active across all network environments:

Set-NetTeredoConfiguration -Type EnterpriseClient

To restore standard client-on-demand behavior for non-domain machines:

Set-NetTeredoConfiguration -Type Client

To completely disable the Teredo tunneling interface across hardened enterprise endpoints where IPv6 tunneling is prohibited by security policy:

Set-NetTeredoConfiguration -Type Disabled

Updating the Teredo Relay Server Name

If the default Microsoft Teredo server fails to resolve due to ISP DNS filtering or regional routing outages, point the client to a functional public or private Teredo server endpoint:

Set-NetTeredoConfiguration -ServerName "teredo.remlab.net"

To revert to Microsoft’s primary global Teredo server cluster:

Set-NetTeredoConfiguration -ServerName "win1910.ipv6.microsoft.com."

Configuring Fixed Local UDP Ports for Port Forwarding

By default, ClientPort is set to 0 (dynamic ephemeral UDP port allocation). Behind strict routers or symmetric corporate firewalls, dynamic port assignment causes NAT mapping timeouts. You can bind Teredo to a static UDP port (for example, UDP 35444) so you can forward that port in your local router settings:

Set-NetTeredoConfiguration -ClientPort 35444

Remember to create an inbound firewall allowance in Windows Defender Firewall for the static UDP port:

New-NetFirewallRule -DisplayName "Teredo Static UDP Port" -Direction Inbound -Protocol UDP -LocalPort 35444 -Action Allow

Verifying Supporting Windows Services

Teredo relies on the iphlpsvc (IP Helper) system service to maintain tunnel state. If this service is stopped, Teredo cannot function:

Get-Service -Name iphlpsvc | Set-Service -StartupType Automatic -PassThru | Start-Service

Testing End-to-End Teredo Resolution

After applying configuration changes, trigger state renegotiation by issuing an ICMP ping to a well-known public IPv6 address:

ping -6 2001:4860:4860::8888

Then re-check the interface state:

netsh interface teredo show state

The state transitions to qualified, confirming that the Teredo virtual adapter has acquired an IPv6 tunnel prefix and is actively relaying packets across NAT boundaries.

Configuring Teredo tunneling via PowerShell ensures reliable peer-to-peer connectivity and resolves NAT traversal issues across Windows 11 systems.

Get the best tech tips delivered straight to your inbox.

Join thousands of readers mastering Apple, Google, Microsoft, and Linux.