Article ID: 193825
Article Last Modified on 10/31/2006
APPLIES TO
- Microsoft Windows NT Server 4.0 Standard Edition
- Microsoft Windows NT Workstation 4.0 Developer Edition
This article was previously published under Q193825
SYMPTOMS
The NET TIME /DOMAIN:<domainname> command does not attempt to obtain a list
of domain time source (TS) servers in the target domain. Instead, the
computer sending the command will synchronize its time directly with the
primary domain controller (PDC), not the time source (TS) server of the
domain specified by the /DOMAIN switch.
CAUSE
When the /DOMAIN switch is used with the NET TIME command, the computer
sending the command does a NetGetDcName to determine the PDC of the domain.
After the PDC is known, a call is made to synchronize the time with the
PDC.
RESOLUTION
To force a computer to synchronize its time with a specific computer, send
the following command:
NET TIME \\<MACHINENAME> /SET /Y
-or-
NET TIME \\<IP Address> /SET /Y
On computers running Windows NT 4.0 with Service Pack 3 installed, an
environment variable called LogonServer is set to the validating domain
controller. The LogonServer variable can be used to load balance the time
source responsibility by sending the following command:
NET TIME %LOGONSERVER% /SET /Y
STATUS
Microsoft has confirmed this to be a problem in Windows NT versions 4.0. We
are researching this problem and will post new information here in the
Microsoft Knowledge Base as it becomes available.
REFERENCES
For additional information, please see the following articles in the
Microsoft Knowledge Base:
135646
Err Msg: Could Not Locate a Time-Server
131715
How to Set UP and Synchronize with Domain Time Source Servers
174557
Time Sources Defined for the Windows NT Time Service
Additional query words: timesource net time sync domain timeserve
Keywords: kbbug kbnetwork kbpending KB193825