Quick troubleshooting view
A user can no longer log in with his domain account.
- Invalid or expired password
- Locked or deactivated account
- Inaccessible domain controller
- Test another account
- Control Domain Connectivity
- Check the account status
- Unlock or re-open account if justified
- Correct the DNS of the post
- Restoring communication with a domain controller
Contextual technician plan
Determine if the problem is with the user or the position.
nltest /dsgetdc:example.localThe command should complete without an unexpected error and return data consistent with the intended service.
If the result is normal, keep this layer lower in the hypothesis ranking and continue with the next discriminating check.
If the result is abnormal, preserve the output and investigate this layer before making broader changes.
Check DNS and access to the domain controller.
The new and updated version of the document is available on the website of the European Commission.The command should complete without an unexpected error and return data consistent with the intended service.
If the result is normal, keep this layer lower in the hypothesis ranking and continue with the next discriminating check.
If the result is abnormal, preserve the output and investigate this layer before making broader changes.
Check lock, deactivate and expire.
arami /fqdnThe command should complete without an unexpected error and return data consistent with the intended service.
If the result is normal, keep this layer lower in the hypothesis ranking and continue with the next discriminating check.
If the result is abnormal, preserve the output and investigate this layer before making broader changes.
Distinguish incorrect password, domain unavailable or relationship of approval.
The exact failing name should resolve through the expected DNS server to the expected record without timeout.
If the exact name resolves correctly, compare application cache, suffix/search domain and the client or network where the failure remains.
If resolution fails or returns the wrong record, keep the queried server and answer and correct the resolver, zone/record or DNS path that is actually wrong.
Repeat the same validation test after the correction and confirm the original symptom is gone. Validate stability before closing the incident.
Before changing configuration, record the current value and a way back.
Climb if multiple positions no longer find a domain controller.
A user can no longer log in with his domain account.
Causes probables
- Invalid or expired password
- Locked or deactivated account
- Inaccessible domain controller
- Invalid DNS
- Relationship problem of approval
Diagnostic étape par étape
- 1
Test another account
Determine if the problem is with the user or the position.
- 2
Control Domain Connectivity
Check DNS and access to the domain controller.
- 3
Check the account status
Check lock, deactivate and expire.
- 4
Read the exact message
Distinguish incorrect password, domain unavailable or relationship of approval.
Commands utiles
nltest /dsgetdc:example.localThe new and updated version of the document is available on the website of the European Commission.arami /fqdnSolutions possibles
- Unlock or re-open account if justified
- Correct the DNS of the post
- Restoring communication with a domain controller
- Treat the relationship of approval without withdrawing the position from the domain as a first-line
Climb if multiple positions no longer find a domain controller.