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 No comments

72 answers

Sort by: Most helpful
  1. Anonymous
    2025-01-02T17:26:59+00:00

    Hi,

    My issue is not quite similar (we had company.local domain so not single label).

    I always disable IPV6 first, because so far it has brought nothing but trouble, no upsides.

    I enabled smb1 (on the client side), yeah I know, will get rid of the one old 2003 AD server soon.

    I managed to join domain with fresh 24H2 W11 installation, BUT...

    I could not access sysvol or netlogon shares (no logon scripts etc.). "Ordinary" shares I could access.

    DNS etc. are working nicely.

    What helped (at least for now) is disabling Netbios over TCP/IP

    (TCP/IPv4 settings / advanced / WINS tab in the advanced settings)

    Hope this helps somebody out there :-)

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2024-12-23T17:19:22+00:00

    I had a similar issue today, after disabling IP6 it worked.

    Best Regards

    Christian Lützeler

    Furtok Media

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2024-12-20T16:54:03+00:00

    Thank you my savior

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2024-12-17T17:22:49+00:00

    also tried this one...still no change although after network reset the network changed from "guest" to "network". effect is still the same: no connection to domain network drives.

    connection via Citrix remote connection is still the only workaround at this time.... :-(

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2024-12-17T15:46:56+00:00

    запросил данные, вошел в домен, и.... после перезагрузки блокировка - что ни нажми "заблокировано, обратитесь к админу"

    Was this answer helpful?

    0 comments No comments