WINS and DHCP Admin Display Expiration Dates 2000 Through 2009 with Only One Digit

This article was previously published under Q193371
This article has been archived. It is offered "as is" and will no longer be updated.
Windows Internet Name Service (WINS) Admin and Dynamic Host ConfigurationProtocol (DCHP) Service Admin display the expiration dates 2000 through2009 with only one digit (for example, 1/1/2000 is displayed as 1/1/0instead of 1/1/00).

Windows NT 4.0

To 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 theMicrosoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack

Windows NT 3.51

A supported fix that corrects this problem is now available from Microsoft,but has not been fully regression tested and should be applied only tosystems 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 andinformation on support costs, please go to the following address on theWorld Wide Web:

The English version of this fix should have the following file attributesor 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 asY2k351-i.exe (x86) and Y2k351-a.exe (Alpha):


Windows NT 4.0

Microsoft 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.51

Microsoft has confirmed this to be a problem in Windows NT version 3.51.

Article ID: 193371 - Last Review: 12/28/2014 19:58:23 - Revision: 1.3

Microsoft Windows NT Server 4.0, Terminal Server Edition, Microsoft Windows NT Server 3.51, Microsoft Windows NT Server 4.0 Standard Edition

  • kbnosurvey kbarchive kbhotfixserver kbqfe kbbug kbfix KB193371