none
Cannot join Windows 7 to domain even after setting DNS to domain controller IP

    Question

  • I've been trying to join a new Windows 7 Professional machine to a domain controller running Windows 2003 Server with no luck.  We currently have 4 Windows XP machines running on that domain without any issues, but when I try to add the Windows 7 computer, here is what happens:

    1. A computer account on the domain could not be found (confirmed it is already there)
    2. I put in the computer name and domain again, and Administrator credentials
    3. Now it tells me: "An attempt to resolve the DNS name of a DC in the domain being joined has failed."

    I currently have DNS on the Windows 7 PC set to the Domain Controller and have IPv6 unchecked under Network Properties.  I can even ping the domain name (resolves to IP of the domain controller).  It looks like it can, indeed, find the domain from the message in step 1, so am I missing something here?

    Thanks in advance for any help!

    Thursday, January 9, 2014 7:20 PM

Answers

  • Hi,

    You need flush your DNS cache in client side first.

    Then, let’s create the following registry value for a try:

    HKLM\System\CurrentControlSet\Services\LanManWorkstation\Parameters

     

     - Created a DWORD DomainCompatibilityMode = 1

     - Created a DWORD DNSNameResolutionRequired = 0

    Reboot the machine and check the result again.


    Alex Zhao
    TechNet Community Support

    • Marked as answer by hey_bink Thursday, February 13, 2014 3:23 PM
    Monday, February 10, 2014 6:45 AM
    Moderator

All replies


    1. A computer account on the domain could not be found (confirmed it is already there)
    2. I put in the computer name and domain again, and Administrator credentials
    3. Now it tells me: "An attempt to resolve the DNS name of a DC in the domain being joined has failed."

    I currently have DNS on the Windows 7 PC set to the Domain Controller and have IPv6 unchecked under Network Properties.  I can even ping the domain name (resolves to IP of the domain controller).  It looks like it can, indeed, find the domain from the message in step 1, so am I missing something here?

    Thanks in advance for any help!

    This is for windows 8.. but same tcp/ip setting can be applied to 7... 

    http://www.pcandtablet.com/windows-8-errors-and-crashes/451/when-i-try-to-join-my-windows-8-professional-to-domain-it-gives-an-error.html

    Sunday, January 12, 2014 3:04 AM
  • Hi,

    On your XP computer, use ipconfig /all command  to get the current DNS server address, compare this address with that in windows 7 computer, if they are not the same one, try to replace the correct one.


    Alex Zhao
    TechNet Community Support

    Monday, January 13, 2014 6:30 AM
    Moderator
  • Thanks for replying.  The DNS server is also the domain controller.  DNS for the Windows 7 and XP machines are all set to the DC's IP address.

    I can ping the domain by name from the Windows 7 machine, and can also ping the DC by name.  The strange thing is that it first tells me a computer account on the domain cannot be found (which I think it also told me when I joined the XP machines), has me input the administrator password and domain name again, and finally tells me it cannot join the domain because the DNS could not be resolved.

    From the first error message, it sounds like it can, indeed, find the domain?

    Tuesday, January 14, 2014 6:39 PM
  • Hi,

    If your domain controller is holding DNS role, point the DC to itself for DNS, and make the same setting on your client.

    If it is possible, give me the ipconfig /all result of both good Windows XP and problematic  Windows 7. Let’s find something about this issue.


    Alex Zhao
    TechNet Community Support

    Wednesday, January 15, 2014 2:08 AM
    Moderator
  • Hi Alex,

    The DC (IP address 192.168.2.1) is already pointing to itself for primary DNS and to the router for secondary DNS.  All clients are pointing to the DC for DNS as well.

    Here is the ipconfig readout for one of the good Windows XP computers:

    Windows IP Configuration

            Host Name . . . . . . . . . . . . : member08
            Primary Dns Suffix  . . . . . . . : MEMBERS.local
            Node Type . . . . . . . . . . . . : Unknown
            IP Routing Enabled. . . . . . . . : No
            WINS Proxy Enabled. . . . . . . . : No
            DNS Suffix Search List. . . . . . : MEMBERS.local

    Ethernet adapter Local Area Connection:

            Connection-specific DNS Suffix  . :
            Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network Connection
            Physical Address. . . . . . . . . : 00-16-76-8C-5A-05
            Dhcp Enabled. . . . . . . . . . . : Yes
            Autoconfiguration Enabled . . . . : Yes
            IP Address. . . . . . . . . . . . : 192.168.2.161
            Subnet Mask . . . . . . . . . . . : 255.255.255.0
            Default Gateway . . . . . . . . . : 192.168.2.254
            DHCP Server . . . . . . . . . . . : 192.168.2.254
            DNS Servers . . . . . . . . . . . : 192.168.2.1
                                                8.8.8.8
            Lease Obtained. . . . . . . . . . : Wednesday, January 15, 2014 7:58:29 AM
            Lease Expires . . . . . . . . . . : Friday, January 17, 2014 7:58:29 AM

    And here is the ipconfig readout for the Windows 7 computer:

    Windows IP Configuration

       Host Name . . . . . . . . . . . . : MEMBER09
       Primary Dns Suffix  . . . . . . . :
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : local

    Ethernet adapter Local Area Connection:

       Connection-specific DNS Suffix  . : local
       Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
       Physical Address. . . . . . . . . : 78-45-C4-37-7D-82
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 192.168.2.164(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Lease Obtained. . . . . . . . . . : Wednesday, January 15, 2014 8:25:31 AM
       Lease Expires . . . . . . . . . . : Friday, January 17, 2014 10:05:09 AM
       Default Gateway . . . . . . . . . : 192.168.2.254
       DHCP Server . . . . . . . . . . . : 192.168.2.254
       DNS Servers . . . . . . . . . . . : 192.168.2.1
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Thanks for your help!

    -Sonja

    Wednesday, January 15, 2014 6:16 PM
  • Hi,

    You can try to set the same Primary Dns Suffix for Windows 7 clients.

    Under Advanced TCP / IP settings, DNS tab, you have a selection to configure  primary suffixes for DNS.


    Alex Zhao
    TechNet Community Support

    Thursday, January 16, 2014 7:21 AM
    Moderator
  • Hi Alex,

    I've tried setting the connection-specific DNS suffix, no luck joining the domain (same sequence of events as described in the original post).  I've also tried adding MEMBERS.local to the list under "append these DNS suffixes", still get the same thing.

    I believe the XP machines are getting the DNS suffix after joining the domain?  I did not set the DNS suffix for those workstations beforehand, and they joined without any problems.

    When I try to join using the name "MEMBERS.local" it tells me no DC could be found for that domain.  But using just "MEMBERS" goes through all the steps in OP.  So it looks like it recognizes the DC, but just won't complete the entire process of joining the domain.

    Thanks,
    Sonja

    Thursday, January 16, 2014 3:24 PM
  • Hi,

    Check this following path to read the netsetup.log which record the operation of joining domain:

    %windir%\debug\Netsetup.log

    Also, you can try this solution for a try:

    Unable to Join Windows Server 2008 R2 or Windows 7 Computer to Active Directory Domain

    http://support.microsoft.com/kb/2008652/en-us


    Alex Zhao
    TechNet Community Support

    • Marked as answer by Karen HuModerator Thursday, January 23, 2014 2:38 AM
    • Unmarked as answer by hey_bink Wednesday, February 5, 2014 6:11 PM
    Friday, January 17, 2014 8:17 AM
    Moderator
  • Hi Alex,

    Sorry it's taken me so long to respond, I have been out of the country.

    Here is the last entry in the Netsetup.log:

    01/16/2014 09:50:06:594 -----------------------------------------------------------------
    01/16/2014 09:50:06:594 NetpValidateName: checking to see if 'MEMBER10' is valid as type 1 name
    01/16/2014 09:50:09:651 NetpCheckNetBiosNameNotInUse for 'MEMBER10' [MACHINE] returned 0x0
    01/16/2014 09:50:09:651 NetpValidateName: name 'MEMBER10' is valid for type 1
    01/16/2014 09:50:09:667 -----------------------------------------------------------------
    01/16/2014 09:50:09:667 NetpValidateName: checking to see if 'MEMBERS' is valid as type 3 name
    01/16/2014 09:50:09:776 NetpCheckDomainNameIsValid [ Exists ] for 'MEMBERS' returned 0x0
    01/16/2014 09:50:09:776 NetpValidateName: name 'MEMBERS' is valid for type 3
    01/16/2014 09:50:14:269 -----------------------------------------------------------------
    01/16/2014 09:50:14:269 NetpDoDomainJoin
    01/16/2014 09:50:14:269 NetpMachineValidToJoin: 'MEMBER09'
    01/16/2014 09:50:14:269 OS Version: 6.1
    01/16/2014 09:50:14:269 Build number: 7601 (7601.win7sp1_gdr.130828-1532)
    01/16/2014 09:50:14:269 ServicePack: Service Pack 1
    01/16/2014 09:50:14:269 SKU: Windows 7 Professional
    01/16/2014 09:50:14:269 NetpDomainJoinLicensingCheck: ulLicenseValue=1, Status: 0x0
    01/16/2014 09:50:14:269 NetpGetLsaPrimaryDomain: status: 0x0
    01/16/2014 09:50:14:269 NetpMachineValidToJoin: status: 0x0
    01/16/2014 09:50:14:269 NetpJoinDomain
    01/16/2014 09:50:14:269 Machine: MEMBER09
    01/16/2014 09:50:14:269 Domain: MEMBERS
    01/16/2014 09:50:14:269 MachineAccountOU: (NULL)
    01/16/2014 09:50:14:269 Account: MEMBERS\wong
    01/16/2014 09:50:14:269 Options: 0x23
    01/16/2014 09:50:14:269 NetpLoadParameters: loading registry parameters...
    01/16/2014 09:50:14:269 NetpLoadParameters: DNSNameResolutionRequired not found, defaulting to '1' 0x2
    01/16/2014 09:50:14:269 NetpLoadParameters: DomainCompatibilityMode not found, defaulting to '0' 0x2
    01/16/2014 09:50:14:269 NetpLoadParameters: status: 0x2
    01/16/2014 09:50:14:269 NetpValidateName: checking to see if 'MEMBERS' is valid as type 3 name
    01/16/2014 09:50:14:394 NetpCheckDomainNameIsValid [ Exists ] for 'MEMBERS' returned 0x0
    01/16/2014 09:50:14:394 NetpValidateName: name 'MEMBERS' is valid for type 3
    01/16/2014 09:50:14:394 NetpDsGetDcName: trying to find DC in domain 'MEMBERS', flags: 0x40001010
    01/16/2014 09:50:29:401 NetpLoadParameters: loading registry parameters...
    01/16/2014 09:50:29:401 NetpLoadParameters: DNSNameResolutionRequired not found, defaulting to '1' 0x2
    01/16/2014 09:50:29:401 NetpLoadParameters: DomainCompatibilityMode not found, defaulting to '0' 0x2
    01/16/2014 09:50:29:401 NetpLoadParameters: status: 0x2
    01/16/2014 09:50:29:401 NetpDsGetDcName: status of verifying DNS A record name resolution for 'memberdc': 0x232b
    01/16/2014 09:50:29:401 NetpDsGetDcName: failed to find a DC in the specified domain: 0xa8b, last error is 0x0
    01/16/2014 09:50:29:401 NetpJoinDomainOnDs: NetpDsGetDcName returned: 0xa8b
    01/16/2014 09:50:29:401 NetpJoinDomainOnDs: Function exits with status of: 0xa8b
    01/16/2014 09:50:29:401 NetpDoDomainJoin: status: 0xa8b

    I can't recall now if I had tried to join the domain with the wizard by using MEMBER10 (I may have tried to rename the machine at the same time) or MEMBER09 (current machine name).  Both computer accounts are valid on the DC.

    Thank you again for all your help!

    -Sonja

    Wednesday, February 5, 2014 3:50 PM
  • Hi,

    You situation is similar with the symptom in the link above:

    http://support.microsoft.com/kb/2008652/en-us

    Do you try the solution to check the result?


    Alex Zhao
    TechNet Community Support

    Thursday, February 6, 2014 3:30 AM
    Moderator
  • Hi Alex,

    I tried the solution in the KB, but got the same result.  The error I am getting is slightly different--I don't get a "DC could not be contacted" type error; it is a "could not resolve DNS name for the DC" error.

    Here is the latest from NetSetup.log:

    02/06/2014 22:23:03:516 -----------------------------------------------------------------
    02/06/2014 22:23:03:516 NetpValidateName: checking to see if 'MEMBERS' is valid as type 3 name
    02/06/2014 22:23:03:625 NetpCheckDomainNameIsValid [ Exists ] for 'MEMBERS' returned 0x0
    02/06/2014 22:23:03:625 NetpValidateName: name 'MEMBERS' is valid for type 3
    02/06/2014 22:23:18:695 -----------------------------------------------------------------
    02/06/2014 22:23:18:695 NetpDoDomainJoin
    02/06/2014 22:23:18:695 NetpMachineValidToJoin: 'MEMBER09'
    02/06/2014 22:23:18:695     OS Version: 6.1
    02/06/2014 22:23:18:695     Build number: 7601 (7601.win7sp1_gdr.130828-1532)
    02/06/2014 22:23:18:695     ServicePack: Service Pack 1
    02/06/2014 22:23:18:695     SKU: Windows 7 Professional
    02/06/2014 22:23:18:695 NetpDomainJoinLicensingCheck: ulLicenseValue=1, Status: 0x0
    02/06/2014 22:23:18:695 NetpGetLsaPrimaryDomain: status: 0x0
    02/06/2014 22:23:18:695 NetpMachineValidToJoin: status: 0x0
    02/06/2014 22:23:18:695 NetpJoinDomain
    02/06/2014 22:23:18:695     Machine: MEMBER09
    02/06/2014 22:23:18:695     Domain: MEMBERS
    02/06/2014 22:23:18:695     MachineAccountOU: (NULL)
    02/06/2014 22:23:18:695     Account: MEMBERS\Administrator
    02/06/2014 22:23:18:695     Options: 0x23
    02/06/2014 22:23:18:695 NetpLoadParameters: loading registry parameters...
    02/06/2014 22:23:18:695 NetpLoadParameters: DNSNameResolutionRequired not found, defaulting to '1' 0x2
    02/06/2014 22:23:18:695 NetpLoadParameters: DomainCompatibilityMode not found, defaulting to '0' 0x2
    02/06/2014 22:23:18:695 NetpLoadParameters: status: 0x2
    02/06/2014 22:23:18:695 NetpValidateName: checking to see if 'MEMBERS' is valid as type 3 name
    02/06/2014 22:23:18:819 NetpCheckDomainNameIsValid [ Exists ] for 'MEMBERS' returned 0x0
    02/06/2014 22:23:18:819 NetpValidateName: name 'MEMBERS' is valid for type 3
    02/06/2014 22:23:18:819 NetpDsGetDcName: trying to find DC in domain 'MEMBERS', flags: 0x40001010
    02/06/2014 22:23:33:827 NetpLoadParameters: loading registry parameters...
    02/06/2014 22:23:33:827 NetpLoadParameters: DNSNameResolutionRequired not found, defaulting to '1' 0x2
    02/06/2014 22:23:33:827 NetpLoadParameters: DomainCompatibilityMode not found, defaulting to '0' 0x2
    02/06/2014 22:23:33:827 NetpLoadParameters: status: 0x2
    02/06/2014 22:23:33:827 NetpDsGetDcName: status of verifying DNS A record name resolution for 'memberdc': 0x232b
    02/06/2014 22:23:33:827 NetpDsGetDcName: failed to find a DC in the specified domain: 0xa8b, last error is 0x0
    02/06/2014 22:23:33:827 NetpJoinDomainOnDs: NetpDsGetDcName returned: 0xa8b
    02/06/2014 22:23:33:827 NetpJoinDomainOnDs: Function exits with status of: 0xa8b
    02/06/2014 22:23:33:827 NetpDoDomainJoin: status: 0xa8b

    • Proposed as answer by Aforaker Wednesday, October 19, 2016 6:44 PM
    Friday, February 7, 2014 6:24 AM
  • Hi,

    You need flush your DNS cache in client side first.

    Then, let’s create the following registry value for a try:

    HKLM\System\CurrentControlSet\Services\LanManWorkstation\Parameters

     

     - Created a DWORD DomainCompatibilityMode = 1

     - Created a DWORD DNSNameResolutionRequired = 0

    Reboot the machine and check the result again.


    Alex Zhao
    TechNet Community Support

    • Marked as answer by hey_bink Thursday, February 13, 2014 3:23 PM
    Monday, February 10, 2014 6:45 AM
    Moderator
  • That did it!  I successfully joined the domain.

    Thank you so much for your help, Alex!

    -Sonja

    Thursday, February 13, 2014 3:23 PM
  • Excellent Sir

    Thank You very much for your valuable replay.

    i was tried more and more but didn't connect to domai.

    i was follow this format connect immediately

    Thank you very much for you wonderful  job

    KAMALAKANNAN


     

    Monday, September 29, 2014 10:01 AM
  • This worked for me as well.  However, now when I try to add a user I get

    Any suggestions?


    Jim Pfingst Scottsdale Technology Solutions

    Wednesday, October 15, 2014 6:52 PM
  • Nevermind.  Re-booted and it worked.

    Thanks!


    Jim Pfingst Scottsdale Technology Solutions

    Thursday, October 16, 2014 2:09 PM
  • This solution worked for me.

    Friday, September 11, 2015 6:43 PM
  • Thank you so much! It worked perfectly! 
    Tuesday, September 19, 2017 6:45 PM