|Access Violation May Occur in Termsrv.exe When You Are Using Time-Outs
Microsoft Knowledge Base Article: 256843 - An access violation may occur in Termsrv.exe
when you are using idle connection and disconnected session
Cannot Log On If Time and Date Are Not Synchronized
Microsoft Knowledge Base Article: 232386 - When you attempt to log on to the network, you may receive the following error message: The system cannot log you on due to the following error: There is a time difference between the Client and Server. Please try
again or consult your system administrator. This behavior can occur if the time or date is not synchronized between your computer and the domain to which you are attempting to log on.
Clients May Not Synchronize the System Time Accurately in Windows 2000
Microsoft Knowledge Base Article: 321290 - If you restore a system to different hardware, the system may start to lose time when Windows tries to synchronize the time by using the Windows Time service. This issue may also occur if you use images to install Windows 2000 on a different
"Could Not Locate a Time Server" After Setting SNTP Time Server Using NET TIME Command
Microsoft Knowledge Base Article: 243574 - When you use the net time command, you may receive the following error message: Could not locate a time-server. More help is available by typing NET HELPMSG 3912. This error message can occur even if
you set a valid Simple Network Time Protocol (SNTP) time server using the net time /setsntp command and network connectivity to the external time server exists.
Daylight Saving Time Option Is Not Retained While Installing Windows 2000
Microsoft Knowledge Base Article: 235417 - During the Windows 2000 installation process, a dialog box appears prompting you to set the time zone.
Internet Time Feature Is Not Available When a Computer Is a Domain Member
Microsoft Knowledge Base Article: 289689
- On a Windows XP-based computer, the Internet Time tab
does not appear in the Date and Time tool in Control Panel. This
behavior occurs because the Windows XP-based computer is a
member of a domain. The Internet Time feature is only available
in workgroup environments.
Logon Time Restrictions Prevent Users on Windows NT 4.0 from Remotely Accessing Windows 2000 Resources
Microsoft Knowledge Base Article: 263006 - In an environment with a Microsoft Windows NT 4.0-based primary domain controller (PDC) and Windows 2000-based computers, non-administrative users who are logged on to Windows NT 4.0-based computers may not be able to gain access to Windows
RPC Error Messages Returned for Active Directory Replication When Time Is Out of Synchronization
Microsoft Knowledge Base Article: 257187 - When you are viewing the status of Active Directory replication between two domain controllers, the following messages may be displayed for the result of the last replication attempt:
SetLocalTime/GetLocalTime Not the Same if Adjusting for Daylight Savings Time
Microsoft Knowledge Base Article: 234735 - Calling SetLocalTime() while the "Automatically adjust clock for daylight saving changes" option is selected in the Date/Time Control Panel Tool does not set the time correctly from the point of view of the GetLocalTime() API.
Time Stamp Changes with Daylight Savings
Microsoft Knowledge Base Article: 129574 - When Windows NT automatically adjusts for daylight savings time, the times on files on Windows NT file system (NTFS) partitions and the events in the event logs are retroactively shifted by one hour, even though the files and event records
were created before the daylight savings time change.
W32Time Client Does Not Fail Over to Secondary NTP Servers by FQDN
Microsoft Knowledge Base Article: 285641 - If you place multiple Network Time Protocol (NTP) servers by IP address in the NTPServer registry value, Windows tries each listed address. If you specify the NTP servers by DNS name (or the FQDN), Windows loops through the list once for server, but attempts to connect to the first name in the list each time instead of trying each name.
W32tm Command Generates Error Messages When Run on a Windows 2000 Domain Controller
Microsoft Knowledge Base Article: 247321 - The W32tm command is used to test and maintain time synchronization between workstations and servers in an enterprise. If you use the command on a Windows 2000 domain controller, you may receive an error message in the output of the
Win32 Time Service Informational, Warning, and Error Messages
Microsoft Knowledge Base Article: 232209 - Windows 2000 uses a new time synchronization service to synchronize the date and time of computers on a Windows 2000-based network. Synchronized time is critical in Windows 2000 because the default authentication protocol (Kerberos version
5) uses workstation time as part of the authentication ticket generation process. The Windows Time Synchronization service (W32Time) is a fully compliant implementation of the Simple Network Time Protocol (SNTP) as detailed in IETF RFC 1769.
Windows 2000 Adjusts Time of Files on CD-ROMs for Local Time Zones
Microsoft Knowledge Base Article: 242059 - This article describes why files on CD-ROMs are adjusted to use the date and time for your local time zone when you are running Windows 2000.
Windows 2000 Loses Date and Time on Every Boot
Microsoft Knowledge Base Article: 243883 - After you install Windows 2000 and reboot, you may receive a message stating that the system's date and time are invalid. When this occurs, the date may be set for January 1, 1601, or another invalid date.
Windows Time Service Continues to Monitor Secondary Client Broadcasts
Microsoft Knowledge Base Article: 243993 - After you upgrade your Microsoft Windows NT 4.0-based computer to Windows 2000 and then you use W32time.exe to configure the Windows Time service to ignore secondary client broadcasts, your Windows 2000-based computer continues to monitor
secondary client broadcasts.