We have a Windows 7 laptop which was recently joined to our SBS 2003 domain. While connected to the network everything works perfectly, but when the network cable is removed we start to have problems.
Most accounts logged in after a delay of around 40-60 seconds. Is this normal for logging on with cached credentials? I was expecting it to be much faster.
Worse still, a couple of domain user accounts behaved as though their credentials were not cached, with the following error appearing after attempting to sign in:
I read on other similar questions titled "There are currently no logon servers available to service the logon request" that removing a PC from the domain then rejoining can sometimes work, but was wondering if anyone could a) explain the underlying problem here and b) come up with alternative solutions which might permanently resolve the issue (we cannot afford to have staff locked out of this device when using it off-site).
Best Answer
As the comments suggest, your problem is that you have more users logging on than you have credentials being cached, so some of those credentials you want cached are being overwritten by more recent logins.
Up the number of cached credentials and the problem should go away. This can be controlled by GPO on the domain, or local security policy. Either way, you open up the policy editor, navigate to
Computer Configuration
->Policies
->Windows Settings
->Security Settings
->Local Policies
->Security Options
and editInteractive logon: Number of previous logons to cache (in case domain controller is not available)
.By default, it's 10, set to at least the number of accounts you'll have logging on, and that should take care of the problem.