Problem Start Windows Server 2022

Question

Hi,

Since few weeks I search a resolve to start the Windows server 2022 normally.

Anytime the server start, I see on the screen just before the screen connect "Waiting NTDS". It call the principal server active directory, but after 30 second it start OS in fail mode.

We have a PDC and the second server who there is the problem.

I have try to repair Active Directory but that 's not resolve.

I do call you for your help precious.

Have you seen this problem ?

Have you got a solution to resolve this ?

Thank a lot.

Jack Michael A.

Answer 1

Hi AMAR Jacques,

Thank you for posting in the Microsoft Community Forums.

Check network connectivity:

Ensure that the server with the problem is able to communicate properly with other servers on the network (especially the PDC). Check that the network hardware (e.g., switches, routers) and network interface cards (NICs) on the server are working properly.

Check the Event Viewer:

Look for errors related to NTDS or Active Directory in the Event Viewer. In particular, system logs and security logs may contain detailed information about the problem.

Check the Active Directory service status:

If the server is able to enter some form of recovery mode (e.g., Safe Mode or Safe Mode with Network Connectivity), attempt to start the Active Directory services (typically the Netlogon and NTDS services). See if these services are able to start successfully and review their event log entries for more information.

Run the DCDiag utility:

DCDiag is a tool for diagnosing Active Directory-related problems. It can help you identify communication problems between domain controllers, replication problems, or database problems.

Check the Active Directory database:

If you suspect database corruption, you can try to restore a database backup in a non-production environment. If no backup is available, you may need to consider rebuilding the domain controller.

Check system files:

Use the System File Checker (SFC) tool to scan and repair corrupted system files. Run sfc /scannow at the command prompt.

Rebuild the domain controller:

If all else fails and you have no backups to restore, rebuilding the domain controller may be the only solution. This usually involves restoring data from a backup (if available) or reinstalling the operating system and Active Directory on new hardware or virtual machines.

Consider hardware issues:

If the problem persists and you've ruled out all software issues, then you may need to consider a hardware failure (e.g., hard drive failure, memory failure, etc.).

Best regards

Neuvi