Unable to join domain Network path not found

Yann Dias de novaes 21 Reputation points
2021-03-05T13:22:53.55+00:00

I have a AD on an OVH server with WS2019 installed.
When I try to join the domain, I have the following error message: Network Path was not found
The server's ip is static, the client has the server as primary DNS.
I can ping the server with the ip and I can ping the domain
I disabled ipv6 on client and server
The server's primary DNS is his public ip and the secondary is 127.0.0.1
I configured the DNS so it

Active Directory
Active Directory
A set of directory-based technologies included in Windows Server.
5,911 questions
0 comments
Accepted answer
  1. Dave Patrick 426.1K Reputation points MVP
    2021-03-05T13:31:40.007+00:00

    Is this a single domain controller? Try restarting the Network Location Awareness service.

    --please don't forget to Accept as answer if the reply is helpful--

10 additional answers

Sort by: Newest
Most helpful Newest Oldest
  1. Yann Dias de novaes 21 Reputation points
    2021-03-05T17:01:36.357+00:00

    Okay, I will try next week then and informed you

  2. Dave Patrick 426.1K Reputation points MVP
    2021-03-05T16:57:58.32+00:00

    That is one issue but usually resolves itself in 10 minutes or so. The bigger issue is
    The DFS Replication service failed to register the WMI providers. Replication is disabled until the problem is resolved.

    Since a new installation I'd suggest clean installing it, patch fully and try again.

    0 comments
  3. Yann Dias de novaes 21 Reputation points
    2021-03-05T16:52:38.837+00:00

    It didn't. I builded this server today so I don't have backup.
    The problem cannot be due to "The DNS server is waiting for Active Directory Domain Services (AD DS) to signal that the initial synchronization of the directory has been completed." ?

    0 comments
  4. Dave Patrick 426.1K Reputation points MVP
    2021-03-05T15:54:03.483+00:00

    What's the history here? Did this domain controller just break? If so you may want to consider restoring a recent known good backup.

    0 comments