Re: AD 2003 - Time Services

From: ptwilliams (ptw2001_at_hotmail.com)
Date: 02/09/05


Date: Wed, 9 Feb 2005 21:18:51 -0000

You shouldn't have run the /setsntp command on anything other than the PDCe.
All other domain members are set, by default, to use Nt5Ds -which means the
domain hierarchy. You'll need to undo this on the other DCs.

I can't remember if /setsntp: <nothing> will reset things (probably not).
So you'll need to drill down to HKLM\ SYSTEM\ CurrentControlSet\ Services\
W32Time\ Parameters and edit the Type REG_SZ to be Nt5Ds (I'm going from
memory here, but I think this is right) and delete the NtpServer REG_SZ
value.

Try something like "windows time" | w32time site:support.microsoft.com in
google. There's an article that covers all registry values.

You can also enable success logging, as by default it only logs errors and
warnings to the event log.

-- 
Paul Williams
http://www.msresource.net/
http://forums.msresource.net/
"CB" <question@tech.net> wrote in message 
news:lsok01tlmfirqg6njmi2eeoiami7k4k2nl@4ax.com...
Hello,
Environment: Win2000/2003 Servers in a mixed-mode 2003 Active
Directory.
DC1 is PDCEmulator FSMO role and configured to obtain time synch
externally from US Navy.
I ran net time /setsntp:dc1 on each of my other domain controllers and
ran net start/stop w32time.
Time synch seems to be OK on the DC's but I am getting a few of these:
Event ID: 50
First event:  02/08/2005  23:25:45
Last event:  02/09/2005  12:48:39
Source: W32Time
Type: Warning
User: -
Log: System
Computer:
Description:
The time service detected a time difference of greater than 5000
milliseconds  for 900 seconds. The time difference might be caused by
synchronization with  low-accuracy time sources or by suboptimal
network conditions. The time service is no longer synchronized and
cannot provide the time to other clients or update  the system clock.
When a valid time stamp is received from a time service  provider, the
time service will correct itself.
15 minutes later however...it sync's up fine.
My member servers  are syncing but I do get these occasionally:
Event ID: 12
First event:  02/09/2005  12:38:42
Last event:  02/09/2005  12:38:42
Source: w32time
Type: Warning
User: -
Log: System
Computer:
Description:
The NTP server
 isn't sync'd, time not set
Question: Is there any way to 'reset' all the time settings on my
DCs/member servers to default...which I would think means to pull it
from the AD hierarchy..?
Using the net time /setsntp: command changes the registry to NTP
instead of NT5DS (which I believe is what I want)
My main concern is that if DC1 goes offline and I specify another DC
as the PDCemulator...I'd like hierarchical time instead of running the
net time command on each server.
Hope this makes sense...appreciate any help.
CB


Relevant Pages

  • Re: AD 2003 - Time Services
    ... the net time /setsntp with blank parameter will remove the ... original added sntp servers. ... You may just run this command or modify the registry as informed by Paul. ... >The time service detected a time difference of greater than 5000 ...
    (microsoft.public.windows.server.active_directory)
  • Time sync. Problem
    ... servers in a NLB cluster for web hosting. ... My one machine keeps on complaining that the time service is not sync'd. ... I've set the following command to run at startup ...
    (microsoft.public.win2000.advanced_server)
  • [2/3] POHMELFS: Documentation.
    ... * Client is able to switch between different servers (if one goes down, ... * Read requests balancing between multiple servers. ... Each transaction contains all information needed to process given command ...
    (Linux-Kernel)
  • [2/3] POHMELFS: documentation.
    ... +POHMELFS: Parallel Optimized Host Message Exchange Layered File System. ... * Read request balancing between multiple servers. ... +command (or set of commands, which is frequently used during data writing: ... +POHMELFS is capable of full data channel encryption and/or strong crypto hashing. ...
    (Linux-Kernel)
  • Re: Dump of user accounts
    ... Both are LDAP servers and both support LDIFDE.exe, ... you can omit the attributes from the ... the command will run using the credentials of the ...
    (microsoft.public.win2000.active_directory)