I think both Troy and Marvin are correct.
It sounds like Juned does not have FW rules in place to allow time sync
to work directly from his DC. Yes, he should use W32Time as Troy
suggests, and should point to an edge device (or other device that has a
time service running on it) as Marvin suggests, IMO.
Klint
Troy Meyer wrote:
How are you setting time? Sorry but I disagree with Marvin, you shouldnt use
net time for 2003 servers; its old and inconsistent. The new way to set time
is with W32Time.
http://support.microsoft.com/kb/816042
that should get your time syncing to the time source with minimal issue. Make
sure you are doing this on your PDC emulator at the top of the forest as that
is where AD time should trickle down from.
-Troy
-----Original Message-----
From: Juned Shaikh [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 18, 2008 9:05 AM
To: NT System Admin Issues
Subject: Domain Controllers time sync software
What is the time-sync software hardware that the list uses? In our environment - for FW reasons the sync with default time sysnc are not working and we are in the process of buying some hardware appliacne with can provide time services.
In the meantime, does anyone has use some software option which can be
installed (safely) on Active directory DC's?
Thanks,
~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
