Microsoft KB Archive/172878
Article ID: 172878
Article Last Modified on 10/31/2006
- Microsoft Windows NT Workstation 4.0 Developer Edition
- Microsoft Windows NT Server 4.0 Standard Edition
This article was previously published under Q172878
Your Windows NT 4.0 computer that is running the Windows NT 4.0 Resource Kit utility Timeserv.exe may slow down in its performance, even stop responding at times. If you check Performance Monitor or Task Manager, you may notice the Timeserv utility displays the CPU Utilization at 100%.
One of the time servers on the Internet that the Timeserv utility contacts has sent no data in its return TCP packet.
To resolve this issue, use either of the following methods:
Obtain the updated Timeserv.exe file from the following Microsoft FTP sites:
Edit the Timeserv.ini file. To do so, follow these steps:
- Click Start, point to Settings, click Control Panel, and then double- click Services.
- Click Time Service, and then click Stop.
- Using a text editor (such as Notepad.exe or Edit.com), open the Timeserv.ini file that exists in your %SystemRoot% folder.
Below the section heading [TimeServ], add the following line:
- Save the file and close the text editor.
- From a command prompt, type timeserv -update.
- Click Start, point to Settings, click Control Panel, and then double- click the Services icon.
- Click Time Service, and then click Restart.
This issue may occur when the Windows NT server computer running Time Service receives no data in the TCP packet from the Internet server when Internet type is selected in the Timeserv.ini file.
When Internet type is selected, your Windows NT server computer will attempt to connect to one of the two time servers on the Internet provided by the United States Naval Observatory (USNO). These time servers provide an accurate time that is used by Windows NT to synchronize its time. The time servers are:
tick.usno.navy.mil 220.127.116.11 tock.usno.navy.mil 18.104.22.168
Occasionally, the server at IP address 22.214.171.124 might not accept time requests sent to the TCP port daytime(13) and sends a TCP RST in return. This will prompt your Windows NT server to try the alternate server, 126.96.36.199, and continues with time synchronization. Alternately, the first server may accept a TCP connection request but does not send any data in the reply message packet. This causes CPU Utilization to go to 100% on the Windows NT Server.
NOTE: The above USNO servers also provide Network Time Protocol (NTP) service. NTP uses UDP port 123. In order to use NTP service, enable NTP in the Timeserv.ini file by adding the following line before updating Time Service:
For more information regarding Time Service, please refer to the "Windows NT 4.0 Resource Kit."
Keywords: kbbug kbenv kbnetwork KB172878