Mohammed mohammed
asked on
Server timing
Hi
I have 3 domain controller, 2 domain controller are in Head office and 1 is at DR location.
all server which are in DR, are syncing time with DR server but now issue is that my DR domain controller is not syncing with my root domain at HO.
whenever I am using command
net time \\<DC_name_or_IP> /set /y
Its' syncing to my domain and after that i am checking the status with below command:
w32tm /query /status /verbose
referenceID is not showing my root domain.
I have 3 domain controller, 2 domain controller are in Head office and 1 is at DR location.
all server which are in DR, are syncing time with DR server but now issue is that my DR domain controller is not syncing with my root domain at HO.
whenever I am using command
net time \\<DC_name_or_IP> /set /y
Its' syncing to my domain and after that i am checking the status with below command:
w32tm /query /status /verbose
referenceID is not showing my root domain.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Hmmm ... W32time, the timekeeping service in Windows. I experienced enough trouble with that piece of crap when in NTP mode to avoid using it whenever I can.
But - if your machines are VMs, ensure that they don't sync to the host time - I've seen that whenever two timekeeping services fidle with the clock concurrently, they wreak havoc to the system time.
For a mature timekeeping service with well documented behaviour, I'd recommend this:
Use a Windows port of the classic *ix NTP service on your DC VMs, and sync 'em with NTP time sources from pool.ntp.org. Ensure to disable the time sync features of VMware (to timekeeping services on one clock will cause time chaos). The NTP service software is free. Easy to install and configure, works like a charm and is stable as a rock. And it is nicer when it comes to one of the rare cases of troubleshooting.
See my article on NTP basics for the "How To".
The classic NTP service has a low ressource footprint, therefore the NTP functionality could be hooked onto existing machines or VM's like webservers, ftp servers, mailservers or database hosts - even in a DMZ - without visible performance impact.
But - if your machines are VMs, ensure that they don't sync to the host time - I've seen that whenever two timekeeping services fidle with the clock concurrently, they wreak havoc to the system time.
For a mature timekeeping service with well documented behaviour, I'd recommend this:
Use a Windows port of the classic *ix NTP service on your DC VMs, and sync 'em with NTP time sources from pool.ntp.org. Ensure to disable the time sync features of VMware (to timekeeping services on one clock will cause time chaos). The NTP service software is free. Easy to install and configure, works like a charm and is stable as a rock. And it is nicer when it comes to one of the rare cases of troubleshooting.
See my article on NTP basics for the "How To".
The classic NTP service has a low ressource footprint, therefore the NTP functionality could be hooked onto existing machines or VM's like webservers, ftp servers, mailservers or database hosts - even in a DMZ - without visible performance impact.
ASKER
Thank you very much for help.
ASKER