locked
error code 0x0000232B RCODE_NAME_ERROR when attempting to add Windows 7 workstaion to my home domain. RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    This error pops up when I am attempting to add my Win7 workstation to my domain.

    Platform Windows Server 2008 R2 Enterprise with SP1. (x64)

    All 4 workstations are running Windows 7 Ultimate with SP1. (x64)

    Here is what is returned when I run dcdiag.exe:

    Directory Server Diagnosis


    Performing initial setup:

       Trying to find home server...

       Home Server = zappy

       * Identified AD Forest.
       Done gathering initial info.


    Doing initial required tests

      
       Testing server: Default-First-Site\ZAPPY

          Starting test: Connectivity

             The host 918420fb-33a2-4adb-b802-efaac18a6496._msdcs.deltpc.local could not be resolved to an IP address.

             Check the DNS server, DHCP, server name, etc.

             Got error while checking LDAP and RPC connectivity. Please check your firewall settings.

             ......................... ZAPPY failed test Connectivity

    I have exhausted this forum as well as technet and knowledge base.

    I am NOT using my router as DNS or DHCP servers.  Disabled these.

    I found 918420fb-33a2-4adb-b802-efaac18a6496 in my registry as HKEY_LOCAL_MACHINE,Software,Microsoft,Cryptography,AutoEnrollment,AEDirectory Cache.

    It has been several months since I attempted to add a box to the domain, which was successful.

    I have not added hardware or changed anything on my server setup except for installing updates and changing my router IP address.

    I hate admitting defeat but, this one's got me.

    David Lambert
    • Moved by Brent Hu Friday, May 27, 2011 6:40 AM (From:General)
    Friday, May 27, 2011 4:52 AM

Answers

  • Question
    Sign in to vote
    1
    Sign in to vote
    Hi David,

    Please make sure that you have to use DC as your preferred DNS server. Can you post an output of "ipconfig /all" from the affected computer?

    "DNS name does not exist" error code 0x0000232B RCODE_NAME_ERROR
    http://blogs.msdn.com/b/alross/archive/2011/04/26/quot-dns-name-does-not-exist-quot-error-code-0x0000232b-rcode-name-error.aspx

    Troubleshooting Domain Join Error Messages
    http://social.technet.microsoft.com/wiki/contents/articles/troubleshooting-domain-join-error-messages.aspx

    Brent
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
    • Marked as answer by delttech Saturday, May 28, 2011 12:24 AM
    Friday, May 27, 2011 6:49 AM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Hello,

       Testing server: Default-First-Site\ZAPPY

          Starting test: Connectivity

             The host 918420fb-33a2-4adb-b802-efaac18a6496._msdcs.deltpc.local could not be resolved to an IP address.

             Check the DNS server, DHCP, server name, etc.

             Got error while checking LDAP and RPC connectivity. Please check your firewall settings.

             ......................... ZAPPY failed test Connectivity

    I see that 918420fb-33a2-4adb-b802-efaac18a6496._msdcs.deltpc.local can not be resolved to an IP address.This is due to a DNS problem.

    Please post the output of ipconfig /all on all your DCs.

    You have to make sure that:

    • Traffic to post 53 of your DNS servers is not blocked
    • Each DC/DNS server points to itself as primary DNS server and to other internal DNS servers as secondary ones
    • Each DC without DNS points to internal DNS servers as DNS servers
    • Each public DNS server is set as a fowarder and not in IP settings

    Once done, run ipconfig /registerdns on each DC and restart netlogon service on them.

    Also, please check that these ports are opened: http://technet.microsoft.com/en-us/library/bb727063.aspx

     

    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration

    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration

    • Marked as answer by delttech Saturday, May 28, 2011 12:24 AM
    Friday, May 27, 2011 6:55 AM
  • Question
    Sign in to vote
    1
    Sign in to vote

    The above error is due to the fact client can't locate srv records in DNS. Verify DC is not multihomed.

    Make sure Win7 points to local dns server only as the preferred DNS server in their NIC, no APIPA or public IP has been configured.

    Netbios (NetBT)over TCP/IP is not disabled as well as local windows firewall is disabled or any firewall is not blocking the DNS traffic.

    Troubleshooting Domain Join Error Messages

    http://social.technet.microsoft.com/wiki/contents/articles/troubleshooting-domain-join-error-messages.aspx

     

    Regards

    Awinish Vishwakarma| CHECK MY BLOG

    Disclaimer: This posting is provided AS-IS with no warranties or guarantees and confers no rights.

    • Marked as answer by delttech Saturday, May 28, 2011 12:25 AM
    Friday, May 27, 2011 7:27 AM
  • Question
    Sign in to vote
    1
    Sign in to vote

    http://support.microsoft.com/kb/331072 was written specifically for WinXP client joining an SBS domain, but the same principles apply here:

    - ensure that DNS settings are configured properly on both the client and DC (as others have pointed out). If you need assistance regarding this, post the output of IPCONFIG /ALL from both

    - disable firewall on both the client and DC

    - enable NetBT on both

    hth
    Marcin


    • Marked as answer by delttech Saturday, May 28, 2011 12:25 AM
    Friday, May 27, 2011 12:45 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    All AD-specific SRV records are recreated automatically when you restart Netlogon service on the domain controller - assuming that its IP settings are configured properly.

    Post

    - output of IPCONFIG /ALL from the domain controller
    - output of IPCONFIG /ALL from the client 
    - output of DCDIAG /v /c
    - content of the %windir%\debug\NetSetup.LOG file

    hth
    Marcin

    • Marked as answer by delttech Saturday, May 28, 2011 3:13 PM
    Saturday, May 28, 2011 12:24 AM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Hello,

    on the DC disable RRAS services,  IP Routing Enabled. . . . . . . . : Yes, this is not recommended on DCs.

    Do you have the forward llokup zone containing the A and Nameserver record for the DC and also complete folder structure?

    Is the DHCP client service started and set to automatic?

    Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
    • Marked as answer by delttech Saturday, May 28, 2011 3:13 PM
    Saturday, May 28, 2011 8:51 AM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Hello,

    your RRAS description is correct.

    DHCP client service must be started on all domain machines, also the ones with fixed ip addresses, this service is required for DNS registration.

    You should also have the Nameserver record for the DC in the zone listed, please check/correct the DHCP client service, then run ipconfig /registerdns and restart the netlogon service.

    Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
    • Marked as answer by delttech Sunday, May 29, 2011 7:14 PM
    Sunday, May 29, 2011 9:39 AM

All replies

  • Question
    Sign in to vote
    1
    Sign in to vote
    Hi David,

    Please make sure that you have to use DC as your preferred DNS server. Can you post an output of "ipconfig /all" from the affected computer?

    "DNS name does not exist" error code 0x0000232B RCODE_NAME_ERROR
    http://blogs.msdn.com/b/alross/archive/2011/04/26/quot-dns-name-does-not-exist-quot-error-code-0x0000232b-rcode-name-error.aspx

    Troubleshooting Domain Join Error Messages
    http://social.technet.microsoft.com/wiki/contents/articles/troubleshooting-domain-join-error-messages.aspx

    Brent
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
    • Marked as answer by delttech Saturday, May 28, 2011 12:24 AM
    Friday, May 27, 2011 6:49 AM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Hello,

       Testing server: Default-First-Site\ZAPPY

          Starting test: Connectivity

             The host 918420fb-33a2-4adb-b802-efaac18a6496._msdcs.deltpc.local could not be resolved to an IP address.

             Check the DNS server, DHCP, server name, etc.

             Got error while checking LDAP and RPC connectivity. Please check your firewall settings.

             ......................... ZAPPY failed test Connectivity

    I see that 918420fb-33a2-4adb-b802-efaac18a6496._msdcs.deltpc.local can not be resolved to an IP address.This is due to a DNS problem.

    Please post the output of ipconfig /all on all your DCs.

    You have to make sure that:

    • Traffic to post 53 of your DNS servers is not blocked
    • Each DC/DNS server points to itself as primary DNS server and to other internal DNS servers as secondary ones
    • Each DC without DNS points to internal DNS servers as DNS servers
    • Each public DNS server is set as a fowarder and not in IP settings

    Once done, run ipconfig /registerdns on each DC and restart netlogon service on them.

    Also, please check that these ports are opened: http://technet.microsoft.com/en-us/library/bb727063.aspx

     

    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration

    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration

    • Marked as answer by delttech Saturday, May 28, 2011 12:24 AM
    Friday, May 27, 2011 6:55 AM
  • Question
    Sign in to vote
    1
    Sign in to vote

    The above error is due to the fact client can't locate srv records in DNS. Verify DC is not multihomed.

    Make sure Win7 points to local dns server only as the preferred DNS server in their NIC, no APIPA or public IP has been configured.

    Netbios (NetBT)over TCP/IP is not disabled as well as local windows firewall is disabled or any firewall is not blocking the DNS traffic.

    Troubleshooting Domain Join Error Messages

    http://social.technet.microsoft.com/wiki/contents/articles/troubleshooting-domain-join-error-messages.aspx

     

    Regards

    Awinish Vishwakarma| CHECK MY BLOG

    Disclaimer: This posting is provided AS-IS with no warranties or guarantees and confers no rights.

    • Marked as answer by delttech Saturday, May 28, 2011 12:25 AM
    Friday, May 27, 2011 7:27 AM
  • Question
    Sign in to vote
    1
    Sign in to vote

    http://support.microsoft.com/kb/331072 was written specifically for WinXP client joining an SBS domain, but the same principles apply here:

    - ensure that DNS settings are configured properly on both the client and DC (as others have pointed out). If you need assistance regarding this, post the output of IPCONFIG /ALL from both

    - disable firewall on both the client and DC

    - enable NetBT on both

    hth
    Marcin


    • Marked as answer by delttech Saturday, May 28, 2011 12:25 AM
    Friday, May 27, 2011 12:45 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    All AD-specific SRV records are recreated automatically when you restart Netlogon service on the domain controller - assuming that its IP settings are configured properly.

    Post

    - output of IPCONFIG /ALL from the domain controller
    - output of IPCONFIG /ALL from the client 
    - output of DCDIAG /v /c
    - content of the %windir%\debug\NetSetup.LOG file

    hth
    Marcin

    • Marked as answer by delttech Saturday, May 28, 2011 3:13 PM
    Saturday, May 28, 2011 12:24 AM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Hello,

    on the DC disable RRAS services,  IP Routing Enabled. . . . . . . . : Yes, this is not recommended on DCs.

    Do you have the forward llokup zone containing the A and Nameserver record for the DC and also complete folder structure?

    Is the DHCP client service started and set to automatic?

    Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
    • Marked as answer by delttech Saturday, May 28, 2011 3:13 PM
    Saturday, May 28, 2011 8:51 AM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Hello,

    your RRAS description is correct.

    DHCP client service must be started on all domain machines, also the ones with fixed ip addresses, this service is required for DNS registration.

    You should also have the Nameserver record for the DC in the zone listed, please check/correct the DHCP client service, then run ipconfig /registerdns and restart the netlogon service.

    Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
    • Marked as answer by delttech Sunday, May 29, 2011 7:14 PM
    Sunday, May 29, 2011 9:39 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi David,

    Please make sure you disable IPv6 from both side. then try again

    Monday, May 29, 2017 6:53 PM