Window 11 24H2 / Can't Join Domain

Anonymous
2024-08-28T15:27:07+00:00

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.

0 comments

72 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2024-11-15T07:41:24+00:00

    as if it was possible to still get 23H2 version somewhere, that would help. Then we were able to roll back, even trough reinstall.

    Now we are stuck with 24H2 that has this big issue with domains......

    As a VM, I supply you two trusted sources:

    os.click/en/Windows:Windows_11:23H2

    Downloading Windows 11 23H2 ISO - Your Windows Guide

    Was this answer helpful?

    0 comments
  2. Anonymous
    2024-11-15T21:16:15+00:00

    Same issue

    Was this answer helpful?

    0 comments
  3. Anonymous
    2024-11-19T14:53:12+00:00

    https://blogs.windows.com/windows-insider/2023/08/16/announcing-windows-11-insider-preview-build-25931-canary-channel/

    DC location will no longer use NetBIOS\WINS\mailslot-based discovery by default

    https://blogs.windows.com/wp-content/uploads/prod/sites/44/2023/08/dc-locator-changes-blocknetbiosdiscovery-policy.png

    When BlockNetBIOSDiscovery is Disabled it takes a bit longer to get the same failure message.

    [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Netlogon\Parameters]

    "BlockNetbiosDiscovery"=dword:00000000

    This time nbtstat -A IP_of_PDC correctly shows ALL domain records:

    NetBIOS Remote Machine Name Table 

        Name               Type         Status 

--------------------------------------------- 

FS             <00>  UNIQUE      Registered 

FS             <03>  UNIQUE      Registered 

FS             <20>  UNIQUE      Registered 

☺☻\_\_MSBROWSE\_\_☻<01>  GROUP       Registered 

DOMAIN          <00>  GROUP       Registered 

DOMAIN          <1B>  UNIQUE      Registered 

DOMAIN          <1C>  GROUP       Registered 

DOMAIN          <1D>  UNIQUE      Registered 

DOMAIN          <1E>  GROUP       Registered 

 MAC Address = 00-00-00-00-00-00

    But nbtstat -r shows still nothing resolved via Broadcast:

    NetBIOS Names Resolution and Registration Statistics 

---------------------------------------------------- 

Resolved By Broadcast     = 0 

Resolved By Name Server   = 3

Registered By Broadcast   = 0 

Registered By Name Server = 3

    Was this answer helpful?

    0 comments
  4. Anonymous
    2024-11-19T17:23:27+00:00

    Any conclusion here that leads to a (perhaps temporary) solution?

    Goal remains that I/we are able to log on to our domain as before, up until W11 23H2.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2024-11-19T19:20:27+00:00

    https://www.anoopcnair.com/windows-11-dc-location-no-longer-use-netbios/https://www.anoopcnair.com/windows-11-features-dc-locator-algorithm-25931/ "Block NetBIOS-based Discovery for Domain Controller Location

    If you enable or do not configure this policy setting, the DC location algorithm will never use NetBIOS-based discovery. This is the default behaviour. If you turn off this policy setting, the DC location algorithm may use NetBIOS-based discovery when necessary. The final behaviour is further governed by the AvoidFallbackNetbiosDiscovery setting."

    [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Netlogon\Parameters]

    "AvoidFallbackNetbiosDiscovery"=dword:00000000

    Was this answer helpful?

    0 comments