I recently set up the Time Server service on several servers in my domain. One goes out to NIST to find the time, the other servers look to that server for their time. On some of my machines, server performance was unchanged when the Time Service was started; on others, the server ground to a halt. When I was finally able to take a look at what sort of resources were being tied up, I saw the time service was using up to 98% of the CPU resources.<br><br>Does anyone know why this happens & how I can fix it? There is no significant difference between these servers in terms of CPU, Ram or OS (NT 4.0 SP4).