Imagine a scenario when you are normally capable of login to your system with cached credentials and get the next error:
We can’t sign you with this credential because your domain isn’t available. Make positive your system is related to your group’s community and check out once more. If you beforehand signed in on this system with one other credential, you can sign in with that credential.
Ideally, as quickly because it factors to a difficulty with the domain becoming a member of, customers would delete the pc/s from the domain and rejoin them. However, it doesn’t normally assist. Just a few different preliminary steps that could possibly be tried try as well the system with no community connectivity, eradicating the native profile listing for the person, altering GPO for occasion log retention, and many others.
We can’t sign you with this credential because your domain isn’t available
If it nothing work, we might proceed to the next troubleshooting:
1] Remove the person from the protected person’s group
Many customers reporting this challenge reported the trigger because the person being added to a particularly protected person group within the energetic listing. For firm managed methods, please contact the system administrator for a similar. Learn extra about protected person teams on docs.microsoft.com.
2] Verify the DNS settings
Conflict with the DNS settings might probably trigger this error. Check this reference to study extra about .
three] Using Security Policy snap-in
Please backup your knowledge earlier than trying this repair.
- Press Win + R to open the Run window and sort the command secpol.msc. Press Enter and it open the Security Policy snap-in.
- In the safety coverage snap-in window, navigate to Security Settings > Local Policies > Security Options.
- In the right-pane, seek for the coverage Interactive logon: Number of earlier logons to cache (in case domain controller just isn’t available). Double-click on the coverage to change the worth of the coverage.
- Set the worth of “Do not cache logons” to zero.
This troubleshooting was referred from the Microsoft Answers web site here.