server 2019 join domain after disabling ipv6

Question

Last year we disabled ipv6 in order to join win10 to 2019 domain. This year, a few win 11 computers were able to join after disabling IPv6. This month, that "disable" work-around no longer works.

What is the preferred method or work-around to get these clients to join domain?

an fyi, years ago we had an easy link on client ....I miss not having that link!

Answer 1

Hi G. K r e n i k,

I’m following up to check whether the issue has been resolved. Feel free to reply if you need further information. If the information provided was helpful, please click "Accept Answer" to help others in the community. Thank you!

Answer 2

Hi G. K r e n i k,

Disabling IPv6 was never the preferred method for domain joins, but in some cases it appeared to bypass certain configuration issues. With newer versions of Windows 11 and updated domain controllers, that approach is no longer reliable, which is why you’re seeing inconsistent results now.

The recommended method is to leave IPv6 enabled, as Microsoft fully supports IPv6 in modern domain environments. Instead, please ensure that DNS is correctly configured on your clients, pointing to your domain controller’s DNS server. Misconfigured DNS is the most common reason domain joins fail. Also, verify that your domain controller and clients are on the same network segment and that firewall rules allow domain traffic (Kerberos, LDAP, etc.).

If you continue to have trouble, you can use the System Properties > Computer Name > Change option to join the domain, or run the PowerShell command Add-Computer -DomainName <yourdomain> with administrator rights. These are the supported ways to join, and they don’t require disabling IPv6. I know you mentioned missing the old easy link, that was part of earlier versions of Windows, but the supported tools now are System Properties and PowerShell.

I hope this helps you move forward smoothly. If you find this answer helpful, please consider clicking Accept Answer so others can benefit too.

Jason.

Answer 3

IPv6 should not be disabled to make domain joins work. IPv6 is a mandatory part of modern Windows versions, and the recommended approach is to fix the underlying networking/AD/DNS issue rather than rely on disabling IPv6 as a workaround.

Preferred approach:

1. Re‑enable IPv6 on clients
   • Ensure IPv6 is not disabled via the DisabledComponents registry value at: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\DisabledComponents.
   • If it was set to 0xFF (255) or another non‑default value, set it back to 0 (or use the “Prefer IPv4 over IPv6” value 0x20 if needed) and reboot.
   • This keeps IPv6 functional while allowing IPv4 to be preferred, which is the recommended configuration.
2. Prefer IPv4 instead of disabling IPv6
   • To prefer IPv4 over IPv6, configure DisabledComponents to decimal 32 (hex 0x20).
   • After reboot, verify that IPv4 is preferred:
     • Run ping <your-domain> or ping bing.com and confirm an IPv4 address is returned.
     • Run netsh interface ipv6 show prefixpolicies and ensure the ::ffff:0:0/96 prefix has higher precedence than ::/0.
3. Fix the actual domain join problem (DNS/AD) When domain join fails, the primary cause is usually DNS/AD connectivity, not IPv6 itself. Use the standard domain join troubleshooting steps:
   • Verify correct DNS configuration on the client:
     • Preferred DNS server must be a DNS server that hosts or can resolve the AD domain zone.
     • Ensure the domain name and domain controllers can be pinged.
   • Confirm domain controllers and DNS are reachable:
     • Use nltest /dsgetdc:<DNS domain name> /force or nltest /dsgetdc:<netbios domain name> /force to verify a DC can be located.
   • Check C:\Windows\Debug\netsetup.log on the client for detailed join errors.
   • Ensure required ports between client and DC are open (per AD domain join requirements).
4. Join the domain using supported methods
   • Use GUI (Server Manager / Control Panel → System → Change settings → Domain) or command line:

          netdom join %COMPUTERNAME% /domain:YourDomainName /userd:DomainUsername /passwordd:*
     

   • After a successful join, reboot the client.
5. Consider domain join hardening changes
   • Recent updates (KB5020276) introduce domain join hardening. If reusing existing computer accounts, ensure the joining user is either the creator of the account or a domain admin, or adjust the process so a domain admin creates/joins the computer as required.

Summary: Re‑enable IPv6, optionally configure “Prefer IPv4 over IPv6,” then focus on DNS/AD connectivity and use standard domain join procedures. Disabling IPv6 is no longer recommended and can break Windows components.

---

References:

• Guidance for configuring IPv6 in Windows for advanced users
• Active Directory domain join troubleshooting guidance
• Join a computer to a domain (windows-server-2019)
• Troubleshoot networking errors that occur when you join Windows-based computers to a domain