• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1031
  • Last Modified:

Caching Domain Credentials Not Working

Hi All,

I am currently having issues with the caching of credentials when some of our notebook users are logging onto their notebooks off-line (when not connected to the domain).
If they log onto the computer when connected to the domain it will allow them anywhere from 1-5 login's after disconnecting (no pattern nailed down yet), but will then give them the "domain is not available" message.

I have checked the users registry at:
HKLM\Software\microsoft\windows nt\current version\win logon
Value: CachedLogonsCount
Set to 10

The users are using a mix of Windows XP SP2 and Windows 2K Pro SP4.

I do have users that don't have any problems with caching credentials (like myself) but I don't want to rule out the DC...

The default domain policy looks ok in GPMC.

Any ideas??

Thanks,
cn
0
coenewnes
Asked:
coenewnes
  • 2
  • 2
1 Solution
 
bbrunningCommented:
Disjoin them from the domain, reboot, then add them to a workgroup with the same name as the domain. microsoft.com = microsoft (workgroup)

Delete/rename/move the profile in documents and settings, rejoin the domain and let it recreate the profile.

See if you still have the same problems. I've run into similar problems and that has fixed the issue.

0
 
coenewnesAuthor Commented:
Thanks bbrunning,

Problem is that I have a large network and I am getting this on a lot of computers.  Also, many of the applications have large amounts of customization that are stored in the local profile.  

I need to find out the cause of the problem as I am worried that all of my notebook users are going to have this.
Also, I am worried that the problem will come back after I do make the above changes...

Any help would be appreciated...
cn
0
 
bbrunningCommented:
If this is happening on more than one machine you probably have a problem with active directory.
0
 
coenewnesAuthor Commented:
It ended up being specific to Windows 2000 SP4....
The problem was that the "Update Rollup 1 For Windows Service Pack 1" patch changes some dll's and causes the problem...
Uninstalled it and the problems were solved...

Thanks for the time spent....

cn
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now