Cached logon not working

David Dawson 246 Reputation points
2020-08-14T19:34:20.847+00:00

On one laptop we are seeing that cached credential don't work. We have DirectAccess set up so wherever they have an internet connection they should be able to log on, however, when this person doesn't have an internet connection because they're on the train or otherwise away from a fixed location they are offline. When they try to log on the see:

We can’t sign you with this credential because your domain isn’t available. Make sure your device is connected to your organization’s network and try again. If you previously signed in on this device with another credential, you can sign in with that credential.

I've checked Secpol.msc on this computer to confirm that the setting to allow cached credentials is set to the default. "Interactive logon: Number of previous logons to cache (in case domain controller is not available)" is set to 10.

She was logged onto the computer. She locked her computer and disconnected wifi and then tried to logon and it's not working. Is there somewhere else to look?

Windows for business | Windows Client for IT Pros | Directory services | Active Directory
0 comments

4 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Ivan Naydenov 0 Reputation points
    2024-04-30T10:15:30.8566667+00:00

    Our users are encountering a similar problem. They use up-to-date Windows 11 laptops that are domain-joined. When the laptop is connected to a VPN and enters sleep mode, upon waking, the user receives an error message stating: "We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential."

    Was this answer helpful?

    0 comments
  2. GЗ 6 Reputation points
    2020-11-19T18:56:12.01+00:00

    We had the same problem here, it turned out that on the laptop there was a local user with the same name as the domain user. We deleted the local user and the problem disappeared.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2020-08-17T00:42:14.597+00:00

    Hi,
    Firstly.i would suggest confirm the Registry key under
    HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\CachedLogonsCount type REG_SZ has the right value.

    Then,make sure that the user had logged on to the computer when it was connected to the domain.

    Or any other users had logged to this computer?Were the credentials working for other users.

    Best Regards,

    Was this answer helpful?

    1 person found this answer helpful.
  4. David Dawson 246 Reputation points
    2020-08-14T19:48:02.923+00:00

    The computer is running Windows 10 Enterprise with the latest updates and is joined to the domain. Due to current issues, this person is working outside the office full time and never has any trouble getting to resources such as files via mapped drives.

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.