Windows 2000 W32time Error
Other DCs then sync with the PDCe and clients and member servers sync with their authenticating DC. If you can't straighten it out manually, let's perform the following procedure, which includes running the Mr Fix It script: 1. This article describes how to install Windows Clustering Time Service when you install Windows 2000 Keeping Time on your Windows NT Network Offers an overview and instructions for using the Network This is because in Windows 2000 the Simple Network Time Protocol (SNTP) was used and was configured with the NET TIME command. my review here
Since the Windows Time (W32Time) service only works on versions of Windows starting with Windows 2000, administrators have been forced to use a cumbersome combination of batch files and logon scripts A child PDC Emulator will choose to sync up time with a parent root domain DC,and it can choosethe parent PDC or any otherDC in the parent root domain. This peer will be discarded as a time source and NtpClient will attempt to discover a new peer with this DNS name. Setting and maintaining these rights for Windows workstations is very time-intensive for an administrator.
You cannot query the Windows Time service to determine when the last time set occurred, who the inbound time partner was, or when the next time set is scheduled (although some The http://technet2.microsoft.com/WindowsServer/en/library/a0fcd250-e5f7-41b3-b0e8-240f8236e2101033.mspx?mfr=true How to configure the Windows Time Service against a large time offset:http://support.microsoft.com/kb/884776/ Registry entries for the W32Time Service:http://support.microsoft.com/kb/q223184/ How to configure Debug logging:http://support.microsoft.com/kb/816043/ How to configure and authoritative time To alter the time registry settings, is inviting trouble and should only be done under guidance by Microsoft Support. Some first-level time servers may have a restricted access policy.
See http://ntp.isc.org/bin/view/Servers/WebHome for lists of publiclyavailable time servers and "rules of engagement". =>Does anyone know whether Windows 2000 or Server 2003 is capable ofsynchronising more often than every 8 hours, using Log in with Facebook Log in with Twitter Log in with Google Your name or email address: Do you already have an account? I have it set up as Active Directory Domain Controller w/ DNS server on it. W32tm /config /manualpeerlist nowait - do not wait for the resync to occur; return immediately.
Why once every1/2 hour? W32tm Commands NET TIME uses Lan Manager protocols that do not take network delays and WANs into account. The W32Time service is not a full-featured NTP solution that meets time-sensitive application needs. useful reference You can set the source by using the NET TIME /SNTP:source command in a command window on the PDC -- if you remember.
Then run the following:net stop w32time && net start w32time Client should now be part of the time domain heirarchy One more possibility if the above procedure doesn't work to reset W32time Service The NET TIME command-line tool, required for WfWG, Win95, Win98, and ME, simply does not meet the requirements for a reliable modern time solution. Domain Time II Clients and Servers have a built-in Clock Change Monitor that prevents users from changing the time. read more...
Where to Start Advancing Time on Production Computers and the Effect on Active Directory and FRS Microsoft Knowledge Base Article: 289668 - In the course of troubleshooting Active Directory or File his comment is here Fixit" on each DC. W32tm /monitor c:\Documents and Settings\administrator>w32tm /monitordc01.domain.local *** PDC *** [192.168.80.10]: ICMP: 0ms delay. W32tm /resync No Time Data Was Available You can run debug logging to track down the error.
All member servers follow the same process. this page Resources that get time from the NTP server are two steps away from the reference clock, and therefore are part of a stratum that is two higher than the most accurate 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 However, if Domain Time Server is installed on any machine, that machine also becomes a time source. W32tm Sync
More help is available by typing NET HELPMSG 3912. Troubleshooting Time Synchronization Problems... To insure that all clients' clocks are within the five (5) minute skew, the time service must be synched across the infrastructure. get redirected here The sync may or may not happen immediately.
The keys are under: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\w32TimeHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon Related Troubleshootinglinks: To Assist in troubleshooting time service issues on the PDC Emulator and other machines, use the following link:Troubleshooting Windows Time Service Problemshttp://technet.microsoft.com/en-us/library/bb727060.aspx W32tm Set Ntp Server Setting the "Type" on the PDC of the forest root to NTP solved the problem. I normally use 184.108.40.206.
To find the DC that logged a client on, run the following.
Dec 29, 2006 a new error in event viewer (screenshot) Apr 8, 2007 Error in event viewer... In practice, with eight to sixteen hours between checks, the domain will probably have a variance in excess of several minutes. If you decide to try one of these, your should plan on configuring atleast four timeservers for best performance. W32tm Domhier The two-second target is not configurable.
NTP time synchronization takes place over a period of time and involves the transfer of NTP packets over a network. To be honest though, I find it easier to use regedit to do this. Altering the time service registry, unless directed by Microsoft support, are not required. useful reference What is Network Time ProtocolNetwork Time Protocol (NTP) is the default time synchronization protocol used by the Windows Time Service (WTS) in Windows Server 2003 and Windows XP.
Otherwise, wait for the resync to complete before returning. If the time clocks between a machine and a DC are skewed beyond the 5 minute tolerance, the authentication fails, so Microsoft made sure to make the time service work without Such tolerances are outside the design specification of the W32Time service. Slattery You can get rid of this warning with the following commands: 1) Set a chain of SNTP servers to synchronize with via “net time /setsntp:
You can see the offset between the two DCs is 0.0000651s (seconds), so no sync is required since it is under the 2 minute time sync tolerance.