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
    2025-02-11T06:15:05+00:00

    After long attempts, I was unsuccessful. I'm glad you came across me, thank you.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. 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

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. 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!!

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2025-01-15T23:25:19+00:00

    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.

    OK -- I run these commands on an older system, and whether I use the older NetBIOS name of simply "NAME" or if I use the full "NAME.ORG.COM", I get back the same data fro either command, and all is well.

    On my 24H2 laptop, though, I get the same (good) results from NAME.ORG.COM, but for just NAME, I get Status 1355, No Such Domain on the NLTEST request.

    Both machines use the same DHCP server (one of the DC's). Both machines use the same DNS servers (the two DC's in the domain). Both machines are using the same logins. I tried enabling the AllowSingleLabelDnsDomain setting in the registry, but no change. This is quite maddening.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. Anonymous
    2024-08-29T07:01:21+00:00

    Hi DZIERZEK Dale,

    Thank you for posting in the Microsoft Community Forums.

    The key point in your log is that Error: 0x54b indicates that there was a problem when attempting to access or manipulate a specified domain, specifically because the domain did not exist or could not be reached. This error usually occurs during network programming, system configuration, or when a user tries to access a network resource.

    Below are some of the common causes and solutions that may lead to this error:

    Common Causes

    Domain name does not exist: The domain name entered may be a misspelling or the domain name has never been registered.

    DNS problem: The DNS server may not be able to resolve the domain name, or the DNS settings may be incorrect.

    Network Problems: The network connection may be unstable, or there may be network devices such as firewalls, routers, etc. that are blocking access to the domain name.

    Domain Controller Unavailable: In an Active Directory environment, this error may also result if the domain controller cannot be accessed.

    Solution

    Check the domain name:

    Verify that the domain name is correct.

    Use the ping or nslookup command to check if the domain name resolves to an IP address.

    Check DNS settings:

    Make sure your DNS server settings are correct and that the DNS server is working properly.

    Try changing your DNS server (for example, use Google's public DNS 8.8.8.8 and 8.8.4.4).

    Check the network connection:

    Make sure your device is connected to the Internet or an internal network.

    Check if any firewall or router rules are blocking access to the domain.

    Contact the network administrator:

    If you are on a business or organizational network, contact the network administrator for assistance.

    Ask if there are any specific configurations or restrictions regarding the domain.

    Check Active Directory (if applicable):

    Verify that the domain controller is online and accessible.

    Check the replication and synchronization status of Active Directory.

    Check log files:

    Check the system or application log files for more detailed information about the error.

    Use command-line tools:

    Use command line tools such as dsquery (in an Active Directory environment) to query domain information.

    Best regards

    Neuvi

    Was this answer helpful?

    0 comments