In the year 2000, the /times switch does not work correctly with the net user command. Any day and time range yields one of the following error messages:

Back to the top

The time interval for the /times parameter is passed in local time. However, the information about logon hours in the account database is stored in Universal Time Coordinate (UTC) time format. Therefore, Net.exe must take the current date into account for the daylight savings offset. The current algorithm does not handle the year 2000 (or later) correctly.

Back to the top

Windows NT 4.0

To resolve this problem, obtain the latest service pack for Windows NT 4.0 or the individual software update. For information on obtaining the latest service pack, please go to:

•	http://www.microsoft.com/downloads/details.aspx?familyid=E396D059-E402-46EF-B095-A74399E25737&displaylang=en/ (http://www.microsoft.com/downloads/details.aspx?familyid=E396D059-E402-46EF-B095-A74399E25737&displaylang=en/) -or-
•	152734 (http://support.microsoft.com/kb/152734/EN-US/) how to obtain the latest windows nt 4.0 service pack

For information on obtaining the individual software update, contact Microsoft Product Support Services. 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: If you are running Windows NT 4.0 Service Pack 5:

To determine if a localized version of this software update is available, change ""USA"" in the URL above to the appropriate localized abbreviation. Click here (ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/readme.txt) for a list of these abbreviations.

If you are running Windows NT 4.0 Service Pack 4:

To determine if a localized version of this software update is available, change ""USA"" in the URL above to the appropriate localized abbreviation. Click here (ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/readme.txt) for a list of these abbreviations.

If you are running Windows NT 4.0 Service Pack 3:

To determine if a localized version of this software update is available, change ""USA"" in the URL above to the appropriate localized abbreviation. Click here (ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/readme.txt) for a list of these abbreviations.

Back to the top

Windows NT Server 4.0, Terminal Server Edition

The English version of this software update should have the following file attributes or later:

   Date       Time     Size        File name      Platform
   -------------------------------------------------------
   08/25/99  09:11p  142,096       net1.exe       x86
   08/25/99  09:09p  235,792       net1.exe       Alpha
				

To determine if a localized version of this software update is available, change ""USA"" in the URL above to the appropriate localized abbreviation. Click here (ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/readme.txt) for a list of these abbreviations.

Back to the top

Windows NT 3.51

The English version of this software update should have the following file attributes or later:

   Date       Time     Size        File name      Platform
   -------------------------------------------------------
   08/25/99  09:11p  142,096       net1.exe       x86
   08/25/99  09:09p  235,792       net1.exe       Alpha
				

If you are running Windows NT 3.51 Service Pack 5:

To determine if a localized version of this software update is available, change ""USA"" in the URL above to the appropriate localized abbreviation. Click here (ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/readme.txt) for a list of these abbreviations.

Back to the top

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 Server version 4.0, Terminal Server Edition Service Pack 6.

Back to the top

Windows NT Server 4.0, Terminal Server Edition

Microsoft has confirmed that this is a problem in Windows NT Server 4.0, Terminal Server Edition.

Back to the top

Windows NT 3.51

Microsoft has confirmed that this is a problem in Windows NT 3.51.

Back to the top