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--
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
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
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--
1). Start a Command Prompt (cmd.exe) RunAs administrator
2). Change the folder to the WMI folder:
CD %windir%\system32\wbem
3). Reregister all the Windows Management Instrumentation DLLs:
For /f %s in ('dir /b /s *.dll') do regsvr32 /s %s
4). Reregister the MOF files.
for /f %s in ('dir /b *.mof *.mfl') do mofcomp %s
5). Type the following command to make sure that the provider host is registered correctly:
wmiprvse /regserver
6). Reboot
The workstation files appear to have come from the server.
If problems persist then put up a new set of files to look at.
I runned your commands, it didn't change anything. I pushed on the drive the new file
What's the history here? Did this domain controller just break? If so you may want to consider restoring a recent known good backup.
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." ?