| Previous | Next |
| STATUS_MUTANT_LIMIT_EXCEEDED | STATUS_ACCOUNT_EXPIRED |
STATUS_NETLOGON_NOT_STARTED
What the status identifies
STATUS_NETLOGON_NOT_STARTED names a local dependency: the operation attempted a domain logon path while the Netlogon service was not started. Netlogon participates in domain membership and secure-channel operations, so its absence can affect more than a single application. However, starting the service blindly is not a complete diagnosis; a service that stops again or cannot establish its expected relationship may be signalling an underlying DNS, trust, machine-account or policy problem.
This status is more specific than “no logon servers.” The latter focuses on finding or reaching a validation service, while this one points first to the client or server that should be running Netlogon for the requested operation.
What to check
- Inspect the Netlogon service state, startup configuration and recent service-control or system-log events on the computer returning the status.
- Confirm whether the computer is intended to be domain joined and whether its secure channel and machine account are healthy.
- Validate DNS discovery and time after the service is available, because Netlogon still depends on domain infrastructure.
- Do not replace a domain join or trust repair with a permanent manual service restart; capture the reason it was stopped.
References
- Microsoft Open Specifications: NTSTATUS reference
- Microsoft: domain controller troubleshooting
- Samba Wiki: troubleshooting domain members
Looking for a different code? Search another status or error code.