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
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
A manual NTP peer was probably configured on the clients. If that is the case, then
HKEY_LOCAL_MACHINE\SYSTEM\
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.
HKEY_LOCAL_MACHINE\SYSTEM\
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.
ASKER
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
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
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.
Run w32tm /resync /rediscover on the clients you think you are having issues with if they update you are good to go.
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
rant32 is correct on time skew to the source.
if your event logs indicate that time sync is happening the rest will work
w32tm /config /syncfromflags:domhier /update
net stop w32time
net start w32time