NTP windows 2003 ad

Hi,
   I have had alot of issue with ntp in the domain. I have resolved alot of the issues but i am getting the following behaviour which seems a bit strange to me

i changed the time on the pdc server for a test of everything syncing of it. On some servers this time will change automatic no manual intervention but on others and client machines you have to force sync i.e
w32tm /resync
Once you manual enter this command it will go to the pdc and get the time off the pdc fine but why is not doing in automatically  manual intervention on some servers and on client while on others it is ok???

any suggestions?


Thks,

Eoghan  
BarepAssetsSys AdminAsked:
Who is Participating?
 
Rant32Connect With a Mentor Commented:
Are you forcibly setting the wrong time on the client to test your time synchronization? That doesn't work.

Depending on the configuration of the time service and the time difference, the background clock synchronization will not make time jumps like it does with a manual sync. Instead, the time is skewed slowly until it's close to the source.

Source: How the Windows Time Service Works
http://technet.microsoft.com/en-us/library/cc773013%28WS.10%29.aspx

Instead, look for Information Event ID 35 in the System event viewer to see if clients are receiving time from the domain controller. If you see Info Event 35, your time sync is fine.
0
 
Tomas ValentaIT ManagerCommented:
try on workstations running this:
w32tm /config /syncfromflags:domhier /update
net stop w32time
net start w32time
0
 
Rant32Commented:
A manual NTP peer was probably configured on the clients. If that is the case, then

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters\Type

is set to the value 'NTP' which should be Nt5DS.

To reset Windows 2003 and XP to domain time synchronization, enter this (nothing after the colon):

net time /setsntp:
The command completed successfully.

That also changes the W32Time synchronization type to Nt5DS, which is correct for domain clients. Ideally, only the PDC is set to NTP type with manual NTP peer.

To verify, type

net time /querysntp
This computer is not currently configured to use a specific SNTP server.
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
BarepAssetsSys AdminAuthor Commented:
hi a manual peer was configured i reset this and when i do net time /querysntp get the above no specfic sntp server also i done  the domain hierachy command and restarted the service still the same if i type resync it works but does not work auto

 
0
 
Darius GhassemCommented:
Time will not update automatically at the same time on all systems.

Run w32tm /resync /rediscover on the clients you think you are having issues with if they update you are good to go.
0
 
Greg HejlPrincipal ConsultantCommented:
also with a /nowait option with resync rediscover

rant32 is correct on time skew to the source.

if your event logs indicate that time sync is happening the rest will work
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.