Article ID: 193371 - View products that this article applies to.
This article was previously published under Q193371
Windows Internet Name Service (WINS) Admin and Dynamic Host Configuration Protocol (DCHP) Service Admin display the expiration dates 2000 through 2009 with only one digit (for example, 1/1/2000 is displayed as 1/1/0 instead of 1/1/00).
Windows NT 4.0To resolve this problem, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/152734/EN-US/ )How to Obtain the Latest Windows NT 4.0 Service Pack
Windows NT 3.51A supported fix that corrects this problem is now available from Microsoft, but has not been fully regression tested and should be applied only to systems experiencing this specific problem.
To resolve this problem immediately, download the fix as described below. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMSThe English version of this fix should have the following file attributes or later:
Date Time Size File Name Platform ------------------------------------------------------------- 09/11/98 07:08p 174,592 Dhcpadmn.exe (x86) 09/11/98 07:08p 183,840 Winsadmn.exe (x86) 09/11/98 07:16p 246,032 Dhcpadmn.exe (Alpha) 09/11/98 07:16p 254,224 Winsadmn.exe (Alpha)
NOTE: Y2k351-i.exe and Y2k351-a.exe were updated on November 5, 1998.
This hotfix has been posted to the following Internet location as Y2k351-i.exe (x86) and Y2k351-a.exe (Alpha):
Windows NT 4.0Microsoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4.
Windows NT 3.51Microsoft has confirmed this to be a problem in Windows NT version 3.51.