Archived from groups: microsoft.public.windowsxp.general (More info?)
I have seen this question asked many times but without a verifiable answer.
There are numerous LAPTOP users who logon with cached credentials
successfully day after day. Then one day the users get an error advising they
can not be logged on because there are no DCs available. If we log them on
attached to the network their credentials are refreshed and they can again
logon while disconnected from the network using the SAME cahed credentials as
before the error.
One thing we are fairly sure of is that it has nothing to do with the
"interactive Lgon: number of previous logons to cache ...." policy. ( i am on
the # of sets of credentials side of this fence from what I have seen (as
apposed to the number of times a credential set can be used))
for background these user accounts are used to auto logon to a kiosk
environment for training purposes. Once logged on there is often a VPN
connection established for application demonstrations and all works fine
until this error condition occurrs.
At this stage I am starting to wonder if part of the credentials caching
process is tied to the computer's workstation account password and if this is
changed (30 day expiry ) by the computer while connected through VPN the
computer is then unable to read previously cached credentials, hence the
requirement to refresh them.
Has anyone found a verifiable solution\workaround to this problem?
Is it possible that the workstation password (or some other event) is
affecting the computer's ability to read the cached credentials?
Any other thoughts?
Thanks in advance for replies.
I have seen this question asked many times but without a verifiable answer.
There are numerous LAPTOP users who logon with cached credentials
successfully day after day. Then one day the users get an error advising they
can not be logged on because there are no DCs available. If we log them on
attached to the network their credentials are refreshed and they can again
logon while disconnected from the network using the SAME cahed credentials as
before the error.
One thing we are fairly sure of is that it has nothing to do with the
"interactive Lgon: number of previous logons to cache ...." policy. ( i am on
the # of sets of credentials side of this fence from what I have seen (as
apposed to the number of times a credential set can be used))
for background these user accounts are used to auto logon to a kiosk
environment for training purposes. Once logged on there is often a VPN
connection established for application demonstrations and all works fine
until this error condition occurrs.
At this stage I am starting to wonder if part of the credentials caching
process is tied to the computer's workstation account password and if this is
changed (30 day expiry ) by the computer while connected through VPN the
computer is then unable to read previously cached credentials, hence the
requirement to refresh them.
Has anyone found a verifiable solution\workaround to this problem?
Is it possible that the workstation password (or some other event) is
affecting the computer's ability to read the cached credentials?
Any other thoughts?
Thanks in advance for replies.
Facebook
Twitter
Instagram