Not sure what you mean by a Win2k domain. I'm running
Windows 2000 on an internal network. I have no idea what
caused services.exe to grab and hold on to 90% of the CPU
but we did a Windows 2000 repair over the weekend and it
seems to have resolved the issue. I just wish I knew what
caused it in the first place so I can avoid it happening
again.
We saw it about two months ago after applying one of the MS patches or
hotfixes. We tracked it down to a registry setting that caused the machine
(both workstations and servers) to do an LDAP refresh or something, every 2
hours. The default was to check every 12 hours.
I'm guessing that doing the repair rolled some of the settings back to the
default settings - could be that's what resolved it for you.
Ask a Question
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.
