Share via

Unable to join domain "DNS name does not exist."

Anonymous
2011-08-19T20:43:19+00:00

Working on this computer remotely in my company, it has more than one problem but right now we are focusing on trying to re-join it to the domain. We removed it first off to see if it would fix the trust relationship issues it was having along side not being able to browse the network files of any computers or servers.

When attempting to join the domain this is what we get in the dcdiag.txt in the debug folder.

The domain name "xxxxx" might be a NetBIOS domain name.  If this is the case, verify that the domain name is properly registered with WINS.

If you are certain that the name is not a NetBIOS domain name, then the following information can help you troubleshoot your DNS configuration.

The following error occurred when DNS was queried for the service location (SRV) resource record used to locate an Active Directory Domain Controller (AD DC) for domain "xxxxx":

The error was: "DNS name does not exist."

(error code 0x0000232B RCODE_NAME_ERROR)

The query was for the SRV record for _ldap._tcp.dc._msdcs.xxxxx

Common causes of this error include the following:

  • The DNS SRV records required to locate a AD DC for the domain are not registered in DNS. These records are registered with a DNS server automatically when a AD DC is added to a domain. They are updated by the AD DC at set intervals. This computer is configured to use DNS servers with the following IP addresses:

198.6.1.5

198.6.100.38

  • One or more of the following zones do not include delegation to its child zone:

xxxxx

. (the root zone)

xxxxx = domain

Also the IPs listed have been changed.

I've been working on this computer for about 2 days, and while the user is able to work remotely through a terminal server, they are going to need to get access to the server eventually.

Windows for home | Previous Windows versions | Internet and connectivity

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
Answer accepted by question author
  1. Anonymous
    2011-08-19T20:49:43+00:00

    Reset the network device - completely.  Uninstall the network driver and have someone there install the latest one from the manufacturer.

    Manually enter the DNS information for your company's DNS servers on the machine - even if it uses DHCP.

    Make sure its time/time zone is the same as your DNS server's.

    Reset any HOSTS file to the default.

    Ping the DNS server.

    When joining the domain - use the FQDN (mycompany.local, etc.)

    20+ people found this answer helpful.
    0 comments

8 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2013-10-25T14:13:43+00:00

    I just had similar problem and I found "Client for Microsoft Networks" is missing on NIC property protocol and installed. Restarted machine, Able to join

    Cause of missing: unknown ,

    Resolution: added Client for Microsoft Networks

    2 people found this answer helpful.
    0 comments
  2. Anonymous
    2014-10-08T20:20:31+00:00

    This is what ended up fixing the problem that I had.  I worked for way too long on this issue on a Windows 8 tablet.  I had deleted the network connection early on and let it reinstall itself and it added everything else back in so I assumed it was intact.  It wasn't until I saw your comment that I realized that the client wasn't there.   I was about to pull my hair out over this issue.

    Thanks,

    0 comments
  3. Anonymous
    2014-02-05T20:28:19+00:00

    adding "Client for Microsoft Networks" solved my problem of client can't connect to normal corp network shares;

    removed from domain but not able to add back;

    after install client for ms nw, it rejoined perfectly;

    Good solution for my problem.

    Thanks,

    0 comments
  4. Anonymous
    2011-08-23T17:24:43+00:00

    This fixed the initial problem. But another has surfaced. 

    It comes up with an error after putting in my credentials and following is from the Netsetup.log in the debug folder.

    NetpValidateName: checking to see if 'COMPUTER' is valid as type 1 name

    NetpCheckNetBiosNameNotInUse for 'COMPUTER' [MACHINE] returned 0x0

    NetpValidateName: name 'COMPUTER' is valid for type 1

    NetpValidateName: checking to see if 'computer' is valid as type 5 name

    NetpValidateName: name 'computer' is valid for type 5

    checking to see if 'xxxxx.com' is valid as type 3 name

    08/23/2011 10:56:41:724 NetpCheckDomainNameIsValid [ Exists ] for 'xxxxx.com' returned 0x0

    NetpValidateName: name 'xxxxx.com' is valid for type 3

    NetpDoDomainJoin

    NetpMachineValidToJoin: 'COMPUTER'

    OS Version: 6.1

    Build number: 7600 (7600.win7_gdr.110622-1503)

    SKU: Windows 7 Professional

    NetpDomainJoinLicensingCheck: ulLicenseValue=1, Status: 0x0

    NetpGetLsaPrimaryDomain: status: 0x0

    NetpMachineValidToJoin: status: 0x0

    NetpJoinDomain

    Machine: COMPUTER

    Domain: xxxxx.com

    MachineAccountOU: (NULL)

    Account: xxxxx\administrator

    Options: 0x25

    NetpLoadParameters: loading registry parameters...

    NetpLoadParameters: DNSNameResolutionRequired not found, defaulting to '1' 0x2

    NetpLoadParameters: DomainCompatibilityMode not found, defaulting to '0' 0x2

    NetpLoadParameters: status: 0x2

    NetpValidateName: checking to see if 'xxxxx.com' is valid as type 3 name

    NetpCheckDomainNameIsValid [ Exists ] for 'xxxxx.com' returned 0x0

    NetpValidateName: name 'xxxxx.com' is valid for type 3

    NetpDsGetDcName: trying to find DC in domain 'xxxxx.com', flags: 0x40001010

    NetpDsGetDcName: failed to find a DC having account 'COMPUTER$': 0x525, last error is 0x0

    NetpLoadParameters: loading registry parameters...

    NetpLoadParameters: DNSNameResolutionRequired not found, defaulting to '1' 0x2

    NetpLoadParameters: DomainCompatibilityMode not found, defaulting to '0' 0x2

    NetpLoadParameters: status: 0x2

    NetpDsGetDcName: status of verifying DNS A record name resolution for 'XXXXXserver.XXXXX.com': 0x0

    NetpDsGetDcName: found DC '\XXXXserver.XXXX.com' in the specified domain

    NetpJoinDomainOnDs: NetpDsGetDcName returned: 0x0

    NetUseAdd to \XXXXserver.XXXX.com\IPC$ returned 1231

    NetpJoinDomain: status of connecting to dc '\XXXXserver.XXXXX.com': 0x4cf

    NetpJoinDomainOnDs: Function exits with status of: 0x4cf

    NetpDoDomainJoin: status: 0x4cf

    xxxxx = domain

    xxxxxserver = dns/ad server

    COMPUTER = client computer

    After searching it appears that this is a common problem and has a list of causes and solutions that are presented do not work most of the time, the only way I'm reading is a full re-image or re-install of windows. This is absolute last resort, I don't understand because it seems to be just this machine as we have 3 other windows 7 machines down there amung a few window xp boxes that all work fine.

    0 comments