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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2024-12-13T18:27:38+00:00

    I still say, instead of editing the registry, just reinstalling windows 11 has fixed the issue for us!

    Was this answer helpful?

    0 comments
  2. Anonymous
    2024-12-11T11:32:02+00:00

    Abbiamo circa 500 PC sul nostro dominio. Il livello funzionale è Server 2016. Abbiamo ricevuto il nostro primo laptop da Dell che è stato spedito con Windows 11 Pro 24H2 e non si collega. Dal momento che è un fallimento, ho testato varie versioni di Win10 e Win11 che non eseguono 24H2 e si collegano tutte senza problemi.

    netsetup.log mostra:

    28/08/2024 08:09:17:784 -------------------------------------- ---------------------

    28/08/2024 08:09:17:784 NetpValidateName: verifica se 'XPS' è valido come nome di tipo 1

    28/08/2024 08:09:17:784 NetpCheckNetBiosNameNotInUse per 'XPS' [MACCHINA] ha restituito 0x0

    28/08/2024 08:09:17:784 NetpValidateName: il nome 'XPS' è valido per il tipo 1

    28/08/2024 08:09:17:810 -------------------------------------- ---------------------

    28/08/2024 08:09:17:810 NetpValidateName: verifica se 'xps' è valido come nome di tipo 5

    28/08/2024 08:09:17:810 NetpValidateName: il nome 'xps' è valido per il tipo 5

    28/08/2024 08:09:17:816 -------------------------------------- ---------------------

    28/08/2024 08:09:17:816 NetpValidateName: verifica se 'domainname' è valido come nome di tipo 3

    28/08/2024 08:09:17:816 NetpValidateName: 'domainname' non è un nome di dominio NetBIOS valido: 0x7b

    28/08/2024 08:09:28:877 NetpCheckDomainNameIsValid per domainname ha restituito 0x54b, l'ultimo errore è 0x0

    28/08/2024 08:09:28:877 NetpCheckDomainNameIsValid [ Esiste ] per 'nomedominio' ha restituito 0x54b

    Il PC che tenta di connettersi si trova sulla stessa subnet dei nostri DC e non ci sono dispositivi di sicurezza/firewall che filtrano il traffico.

    Dal PC 24H2 che non si unisce, ho provato o sono riuscito a:

    • eseguire la risoluzione dei nomi su vari nomi host tramite nslookup
    • le porte AD in entrata/uscita verificate sono aperte sui nostri DC
    • I DC si stanno replicando e sono sani (altri PC si uniscono senza problemi)
    • Accedi a qualsiasi altra risorsa sulla nostra LAN
    • Ho provato ad assegnare staticamente i server DNS (che sono i nostri DC) sulla NIC del PC
    • Disabilitato il firewall di Windows sul PC
    • Ho ripristinato le impostazioni di fabbrica del laptop (Dell XPS 13 9345) e ho riprovato senza successo

    Un altro post suggerisce di cercare una chiave di registro relativa a NT4Emulator sui DC nel caso in cui il dominio abbia mai avuto un DC NT4. Questa chiave non esiste sui nostri DC e se qui avevamo un DC che eseguiva NT4, era molto prima del mio arrivo.

    Non riesco a pensare a nessun motivo per cui questo laptop sia diverso, a parte il fatto che è il primo che funziona 24H2. Non riesco a trovare nessuno che abbia questo problema.

    Ogni aiuto o suggerimento è apprezzato.

    I have the same problem. Have you found any solution in the meantime?

    Was this answer helpful?

    0 comments
  3. Anonymous
    2024-12-10T14:35:57+00:00

    I am not the same person. But I have the same problem.

    I use OpenLDAP.

    Do you have a solution to the problem? Or any idea?

    Hi Filipe,

    Can you tell what is your openldap version?

    Was this answer helpful?

    0 comments
  4. Anonymous
    2024-12-10T14:22:55+00:00

    I am not the same person. But I have the same problem.

    I use OpenLDAP.

    Do you have a solution to the problem? Or any idea?

    nltest /dsgetdc:<domainname>

    nslookup -type=SRV _ldap._tcp.dc._msdcs.<domainname>

    Run these commands from windows clients, and confirm SRV location for your domain is available on DNS server. If not good to update. Give a try.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2024-12-10T13:59:10+00:00

    I am not the same person. But I have the same problem.

    I use OpenLDAP.

    Do you have a solution to the problem? Or any idea?

    Was this answer helpful?

    0 comments