Article ID: 172831 - View products that this article applies to.
This article was previously published under Q172831
This article has been archived. It is offered "as is" and will no longer be updated.
Between 5 and 6 P.M. eastern time on August 13, 1997, the TimeServ service may have begun consuming 100 percent of your system's resources.
This problem appears to be caused by a change in the United States Naval Observatory's time server. At this time, the problem does not appear to be caused by an error in the TimeServ utility, or by a malicious attack.
Change the TimeServ.ini file to use a Simple Network Time Protocol Server instead of a TCP/IP Server by using the following steps.
NOTE: These steps will not work correctly if you are behind a firewall that passes TCP but not UDP (datagrams).
Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.
Additional information about this problem and other known issues with the Timeserv utility can be found at the following Web address:
http://www.niceties.com/TimeServ.htmlPlease note that this site is not under the control of Microsoft and may change without notice. For Microsoft's official statement regarding other servers, please see the following World Wide Web site:
Article ID: 172831 - Last Review: February 28, 2014 - Revision: 1.2