It wasn't Winlogon.exe after all

A couple of posts ago I accused winlogon.exe of screwing up a server.
Turnes out the culprite was.... an ordinary network hub.
Believe it or not, even with approx. 1% of network load, the hub causes delays of up to 1.4 seconds in network traffic.
Problem solved by a simple cross-cable.
Lessons learned, question EVERYTHING!
Now i've seen it all, I hope ;-)

My first visit to the States

A couple of weeks ago I spent some time in the States. (Troy, Michigan).
Job related I'm afraid so very little time to be a tourist.
I now know that jet-lag can really wear you down. Took me about a week to get over it. ;-)

Winlogon.exe is giving me a headacke!

For several weeks now we are trying to solve a performance issue at one of our customers.
I'll skip the details and get right to the problem.
We have a Windows 2000 server running a critical application. Today we noticed that the winlogon.exe process is using a lot of CPU time. Even more than the sqlserver that is running on this machine. To give you an idea, the sqlserver process has used 2 hours and 45 minutes of CPU time up to now, winlogon has already used nearly 3 hours.
All I can find on the web are problems related to terminal services. But we don't use that.
The problem started after we installed service pack 4 on it.
If this sounds familiar, please please let me know.