After long attempts, I was unsuccessful. I'm glad you came across me, thank you.
Window 11 24H2 / Can't Join Domain
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous
We have about 500 PCs on our domain. Functional level is Server 2016. We received our first laptop from Dell which shipped with Windows 11 Pro 24H2 and it will not join. Since it's failure, I've tested various versions of Win10 and Win11 not running 24H2 and they all join just fine.
netsetup.log shows:
08/28/2024 08:09:17:784 -----------------------------------------------------------------
08/28/2024 08:09:17:784 NetpValidateName: checking to see if 'XPS' is valid as type 1 name
08/28/2024 08:09:17:784 NetpCheckNetBiosNameNotInUse for 'XPS' [MACHINE] returned 0x0
08/28/2024 08:09:17:784 NetpValidateName: name 'XPS' is valid for type 1
08/28/2024 08:09:17:810 -----------------------------------------------------------------
08/28/2024 08:09:17:810 NetpValidateName: checking to see if 'xps' is valid as type 5 name
08/28/2024 08:09:17:810 NetpValidateName: name 'xps' is valid for type 5
08/28/2024 08:09:17:816 -----------------------------------------------------------------
08/28/2024 08:09:17:816 NetpValidateName: checking to see if 'domainname' is valid as type 3 name
08/28/2024 08:09:17:816 NetpValidateName: 'domainname' is not a valid NetBIOS domain name: 0x7b
08/28/2024 08:09:28:877 NetpCheckDomainNameIsValid for domainname returned 0x54b, last error is 0x0
08/28/2024 08:09:28:877 NetpCheckDomainNameIsValid [ Exists ] for 'domainname' returned 0x54b
The PC attempting to join sits on the same subnet as our DCs and there are no security appliances/firewalls filtering traffic.
From the 24H2 PC that won't join, I have tried or am able to:
- perform name resolution to various hostnames via nslookup
- verified inbound/outbound AD ports are open on our DCs
- DCs are replicating and are healthy (other PCs join w/o issue)
- Access any other resource on our LAN
- Tried statically assigning DNS servers (which are our DCs) on the PCs NIC
- Disabled Windows firewall on the PC
- Factory reset the laptop (Dell XPS 13 9345) and attempted again with no success
Another post suggest searching for a registry key relating to NT4Emulator on the DCs in the event the domain ever had an NT4 DC. This key doesn't exist on our DCs and if we had a DC running NT4 here, it was way before my arrival.
I can't think of any reason why this laptop is different other than it's the first running 24H2. I can't seem to find anyone having this issue.
Any help or suggestions is appreciated.
Windows for business | Windows Server | Directory services | Active Directory
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
72 answers
Sort by: Newest
-
Anonymous
2025-02-11T06:15:05+00:00 -
Anonymous
2025-01-23T22:21:35+00:00 Figured it out. I had to turn off IPV6 on all network adapters on on the computer that is trying to connect to the domain
-
Anonymous
2025-01-22T13:44:52+00:00 this was the winner for me. Worked immediately! this should be pinned to the top.
Thank you! I have this printed and ready for the next PC in the door that won't connect.
Cheers!!
-
Anonymous
2025-01-16T19:09:25+00:00 5 months......5 months and we finally have a fix! Bless your heart. Just tried it. And it worked!
-
Anonymous
2025-01-16T16:23:44+00:00 I was having the same issue, I was entering in my domain and it would not find it until I included the .com to the domain name... then it found it. I guess the new version changed the way it locates the domain