| Event Id | 3096 |
| Source | Netlogon |
| Description | The Windows NT domain controller could not be located |
| Event Information | According to Microsoft: CAUSE: This problem occurs because WINS is starting too late in the process for name resolution to occur. RESOLUTION: WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.To resolve this problem, edit the registry and create a dependency for WINS in the Net Logon service: 1. Start Registry Editor (Regedt32.exe). 2. Locate the DependOnService value under the following key in the registry: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\ 3. On the Edit menu, click Multi String, type Wins to add it to the list of dependencies, and then click OK. 4. Quit Registry Editor. 5. Restart the computer. You are using Server Manager on a primary domain controller (PDC) to promote a backup domain controller (BDC) to be the PDC. Both computers are running Windows NT 3.51, but they have different Service Packs applied (Service Pack 4 on the new BDC and Service Pack 2 on the new PDC). The above event error appears in the new BDCs event log: CAUSE: The netlogon service is started on the new BDC before it is started on the new PDC. STATUS: Microsoft has confirmed this to be a problem in Windows NT version 3.51. For more causes and resolution refer the following Microsoft articles |
| Reference Links | event id:3096 AND Source:Net Logon Event 3096 Promoting BDC to PDC with Different Service Packs Unable to Promote Backup Domain Controller to Primary Domain Controller Event ID 5516 and 3096 A Backup Domain Controller That Is Running WINS May Log Event Error 3096 |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.