The local domain controller could not connect with the following domain controller hosting the following directory partition to resolve distinguished names.

Blake 1 Reputation point
2020-08-14T20:11:32.82+00:00

I am trying to setup a Active Directory and cant seem to find the solution on my own. The network also has a firewall, but I dont think that is the issue since the domain controller and AD are on the same machine.

The local domain controller could not connect with the following domain controller hosting the following directory partition to resolve distinguished names.

Domain controller:

Directory partition:
redacted.com

Additional Data
Error value:
1355 The specified domain either does not exist or could not be contacted.
Internal ID:
3201395

Windows IP Configuration

Host Name . . . . . . . . . . . . : Redacted
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Ethernet 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) 82574L Gigabit Network Connection #2
Physical Address. . . . . . . . . : D0-50-99-C1-EB-DC
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::e571:7b1d:c7a9:445c%6(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.168.65(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Friday, August 14, 2020 12:54:44 PM
Lease Expires . . . . . . . . . . : Saturday, August 15, 2020 1:03:01 PM
Default Gateway . . . . . . . . . : 192.168.168.168
DHCP Server . . . . . . . . . . . : 192.168.168.168
DHCPv6 IAID . . . . . . . . . . . : 265310361
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-22-94-F3-A7-D0-50-99-C1-EB-DC
DNS Servers . . . . . . . . . . . : 127.0.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{62CC7E69-5195-4C8B-9BE3-E02D07B12411}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:34f1:8072:c37:e1d1:b8f6:96ac(Preferred)
Link-local IPv6 Address . . . . . : fe80::c37:e1d1:b8f6:96ac%7(Preferred)
Default Gateway . . . . . . . . . : ::
DHCPv6 IAID . . . . . . . . . . . : 520093696
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-22-94-F3-A7-D0-50-99-C1-EB-DC
NetBIOS over Tcpip. . . . . . . . : Disabled

Windows Server 2016
Windows Server 2016
A Microsoft server operating system that supports enterprise-level management updated to data storage.
2,374 questions
Active Directory
Active Directory
A set of directory-based technologies included in Windows Server.
5,895 questions
Windows DHCP
Windows DHCP
Windows: A family of Microsoft operating systems that run across personal computers, tablets, laptops, phones, internet of things devices, self-contained mixed reality headsets, large collaboration screens, and other devices.DHCP: Dynamic Host Configuration Protocol (DHCP). A communications protocol that lets network administrators manage centrally and automate the assignment of Internet Protocol (IP) addresses in an organization's network.
1,023 questions
0 comments No comments
{count} votes

7 answers

Sort by: Newest
  1. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  2. Blake 1 Reputation point
    2020-08-17T20:57:16.56+00:00

    Directory Server Diagnosis

    Performing initial setup:
    Trying to find home server...
    Home Server = AMADSERVER
    * Identified AD Forest.
    Done gathering initial info.

    Doing initial required tests

    Testing server: Default-First-Site-Name\AMADSERVER
    Starting test: Connectivity
    The host 960f30f9-e9d7-48fd-bd35-fe1741b18561._msdcs.amad.com 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.
    ......................... AMADSERVER failed test Connectivity

    Doing primary tests

    Testing server: Default-First-Site-Name\AMADSERVER
    Skipping all tests, because server AMADSERVER is not responding to directory service requests.

    Running partition tests on : Schema
    Starting test: CheckSDRefDom
    ......................... Schema passed test CheckSDRefDom
    Starting test: CrossRefValidation
    ......................... Schema passed test CrossRefValidation

    Running partition tests on : Configuration
    Starting test: CheckSDRefDom
    ......................... Configuration passed test CheckSDRefDom
    Starting test: CrossRefValidation
    ......................... Configuration passed test CrossRefValidation

    Running partition tests on : amad
    Starting test: CheckSDRefDom
    ......................... amad passed test CheckSDRefDom
    Starting test: CrossRefValidation
    ......................... amad passed test CrossRefValidation

    Running enterprise tests on : amad.com
    Starting test: LocatorCheck
    Warning: DcGetDcName(GC_SERVER_REQUIRED) call failed, error 1355
    A Global Catalog Server could not be located - All GC's are down.
    Warning: DcGetDcName(TIME_SERVER) call failed, error 1355
    A Time Server could not be located.
    The server holding the PDC role is down.
    Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed, error 1355
    A Good Time Server could not be located.
    Warning: DcGetDcName(KDC_REQUIRED) call failed, error 1355
    A KDC could not be located - All the KDCs are down.
    ......................... amad.com failed test LocatorCheck
    Starting test: Intersite
    ......................... amad.com passed test Intersite

    0 comments No comments

  3. Vicky Wang 2,646 Reputation points
    2020-08-17T09:28:38.74+00:00

    Let's suppose that your Active Directory Domain Controller (and DNS Server) is a Windows Server 2016 machine and is responsible for the domain "wintips.local" and has the IP Address "192.168.1.10".

    At this example, the IP and the Preferred DNS address on the Primary Domain Controller (Server 2016) must be the same, e.g.

    Primary Domain Controller (Server 2016)
    Computer Name: Server2k16
    Domain Name: WINTIPS.LOCAL
    IP Address (Static): 192.168.1.10
    Subnet Mask: 255.255.255.0
    Default Gateway: 192.168.1.1
    Preferred DNS Server: 192.168.1.10
    Method 1. Set the Preferred DNS Server Address to match the Domain Controller's IP Address (on Client Workstation)
    To resolve the "Specified Domain Does Not Exist or Could Not Be Contacted" error, you have to set the Preferred DNS IP to point to Primary Domain Controller's IP address, on each client workstation that you want to join in the domain. To do that:

    1. Open Network and Sharing Center.
    2. Right click on Local Area Connection and click Properties.
    3. Double click on Internet Protocol TCP/IPv4.
    4. Change the Preferred DNS server address to match the Primary Domain Controller's IP Address (e.g. "192.168.1.10" in this example).
    5. Click OK twice and close all windows.

    6 Try to join the workstation in the Domain.

    1 person found this answer helpful.

  4. Thameur-BOURBITA 32,586 Reputation points
    2020-08-14T22:04:42.33+00:00

    Hi,

    To get more details about the DC health on each domain controller you can run the following command dcdiag

    Dcdiag 
    repadmin /showrepl
    

    Check also the event viewer on each DC.

    0 comments No comments

  5. Dave Patrick 426.1K Reputation points MVP
    2020-08-14T20:42:48.877+00:00

    Please run;

    • Dcdiag /v /c /d /e /s:%computername% >c:\dcdiag.log
    • repadmin /showrepl >C:\repl.txt
    • ipconfig /all > C:\dc1.txt
    • ipconfig /all > C:\dc2.txt
    • (etc. as other DC's exist)

    then put unzipped text files up on OneDrive and share a link.