Windows Apps Can't Connect to Certain IPv6 Addresses. Any Ideas?

Start with the least disruptive checks, then move to configuration changes.

1. Verify whether IPv6 is generally healthy on the machine

• Windows prefers IPv6 global unicast addresses over IPv4 by default.
• If only some apps fail, compare whether the issue is app-specific or system-wide.
• If WSL is also affected, check whether IPv6 was disabled through HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\DisabledComponents, because WSL networking can fail when IPv6 is disabled that way.

2. Check whether IPv6 was disabled or altered

• IPv6 is a mandatory part of Windows Vista, Windows Server 2008, and later.
• Disabling IPv6, disabling IPv6 components, or unbinding IPv6 from interfaces is not recommended because some Windows components might not function.
• If troubleshooting requires changing behavior, prefer Prefer IPv4 over IPv6 in prefix policies instead of disabling IPv6.

3. If registry-based IPv6 changes were made, review them carefully

• Registry path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\
• Value: DisabledComponents (REG_DWORD)
• Valid range: 0x00 to 0xFF
• A restart is required after changes.
• Values other than 0 or 32 can cause the Routing and Remote Access service to fail.

Warning: incorrect registry edits can cause serious problems. Back up the registry before modifying it.

4. Check adapter-level IPv6 binding

• If a workaround is needed for a specific adapter, review whether Internet Protocol Version 6 (TCP/IPv6) is enabled on that adapter.
• In Windows, this is available from Control Panel > Network and Sharing Center > select the active connection > Properties.
• If IPv6 was manually unchecked earlier, some destinations and apps may fail.

5. Test whether the problem is DNS selection versus raw IPv6 reachability

• Since Windows uses address selection rules when multiple addresses are available, name resolution can return IPv6 and IPv4 candidates, and Windows may choose IPv6 first.
• If the issue affects only certain destinations, compare behavior when connecting by name versus by IPv6 literal address. That helps separate DNS/address selection issues from routing/connectivity issues.

6. If Outlook is one of the affected apps

• A known symptom is Outlook showing Disconnected when IPv6 is enabled and the IPv6 network has connectivity issues.
• The documented resolution is to fix the IPv6 network connectivity issue.
• A workaround is either disabling IPv6 on the adapter or using the Prefer IPv4 over IPv6 fix referenced in the Windows IPv6 guidance.

7. If 6to4 or tunneling is involved, test the path

• Check IPv4 connectivity to the 6to4 relay router:
  • ping 6to4.ipv6.microsoft.com
• Check IPv6 encapsulation:
  • ping6 ::131.107.152.32
• If the second test fails, there might be a firewall or NAT between the computer and the Internet.

8. For application-specific failures, review whether the app is IPv6-aware

• Older apps may still rely on hard-coded IPv4 addresses or older name-resolution APIs.
• For Windows sockets applications, the recommended modernization path includes moving to getaddrinfo and getnameinfo, reviewing hard-coded IPv4 literals, and checking protocol dependencies.

A practical starting point is:

1. Check whether DisabledComponents was changed.
2. Confirm IPv6 is still enabled on the affected adapter.
3. Compare hostname access versus direct IPv6 address access.
4. If only one app is affected, test whether it is a known IPv6-sensitive app such as Outlook.
5. If tunneling is in use, run the 6to4 connectivity tests.

• Guidance for configuring IPv6 in Windows for advanced users
• Troubleshooting Windows Subsystem for Linux
• Outlook displays a Disconnected status when IPv6 is enabled
• Configuration 2: IPv6 Traffic Between Nodes on Different Subnets of an IPv4 Internetwork (6to4)
• IPv6 Guide for Windows Sockets Applications
• Using the Checkv4.exe utility