The information in this article applies to:
SYMPTOMSThe 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. CAUSEWhen 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:
STATUSMicrosoft 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. MORE INFORMATION
When using NET TIME /DOMAIN:<DomainName>, a browse list is never requested
from the domain listed to obtain a list of time source (TS) servers. This
may cause problems if the PDC is not the domain time source server because
some applications may be highly time sensitive.
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LANManServer\ParametersWhen NET TIME /SET is sent without the /DOMAIN switch, the computer will obtain a browse list for the domain in which it is a member, select a time source server from the list, and then send a NetrRemoteTOD call to synchronize the time. REFERENCES
For additional information, please see the following articles in the
Microsoft Knowledge Base:
Q135646 Err Msg: Could Not Locate a Time-Server Additional query words: timesource net time sync domain timeserve
Keywords : kbnetwork ntdomain kbbug4.00 |
Last Reviewed: January 4, 2000 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |