I had the same problem, and the problem was with the antivirus on the server, as soon as I temporarily disabled it, users were able to join
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: Oldest
-
Anonymous
2024-11-25T07:59:54+00:00 -
Anonymous
2024-11-29T14:59:56+00:00 Hi
We also encountered this problem of connecting to a single-label DNS domains with Windows 11 24H2. Spent hours trying to figure out a dns issue. However, unlike you, adding a key in the registry allowed us to resolve the problem. I post the procedure below:
To resolve this issue, a registry modification is required. Follow the steps below:
Open the Registry Editor:
Press Win + R, type regedit, and press Enter.
Navigate to the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters
In the right pane, right-click and select New > DWORD (32-bit) Value.
Name the new DWORD as AllowSingleLabelDnsDomain
Double-click AllowSingleLabelDnsDomain and set its value to 1.
Close the Registry Editor.
Restart the computer to apply the changes.
This modification allows support for single-label DNS domains on Windows 11 version 24H2, resolving the connection issue.
After deleting the registry key the issue is back so it confirms that this modification should bypass this issue nethertheless others issues with netlogon and group policy still there.
-
Anonymous
2024-12-01T14:24:53+00:00 Thanks much Sebastien. After two days worth of trying various fixes listed on this and other forums, this very simple regedit allowed a fresh out of the box Dell workstation (Win 11 ver 24H2) to join our company domain.
-
Anonymous
2024-12-01T15:04:57+00:00 Hi Matt,
Glad I could help.
-
Anonymous
2024-12-02T08:05:28+00:00 Hi
We also encountered this problem of connecting to a single-label DNS domains with Windows 11 24H2. Spent hours trying to figure out a dns issue. However, unlike you, adding a key in the registry allowed us to resolve the problem. I post the procedure below:
To resolve this issue, a registry modification is required. Follow the steps below:
Open the Registry Editor:
Press Win + R, type regedit, and press Enter.
Navigate to the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters
In the right pane, right-click and select New > DWORD (32-bit) Value.
Name the new DWORD as AllowSingleLabelDnsDomain
Double-click AllowSingleLabelDnsDomain and set its value to 1.
Close the Registry Editor.
Restart the computer to apply the changes.
This modification allows support for single-label DNS domains on Windows 11 version 24H2, resolving the connection issue.
After deleting the registry key the issue is back so it confirms that this modification should bypass this issue nethertheless others issues with netlogon and group policy still there.
This method adding reg key, is not solved , not working for me.