PLEASE HELP! IM SO ANNOYED! Time server cannot synchronize

[MelodicBrush]

I feel like i've tried everything, can't get this bloody thing to sync, someone please help, tried multiple addresses including time.windows.com, it wont do it

[James_C]

Same here. It is not a simple as it should be, especially with virtual domain controllers etc.

Sorry i cant help but I feel your pain.

[6Foot2]

We have a Parent-Child domain: A while ago the parent and the child domain times were drifting and I couldn't find out why. I decided to use an NetTime on our child domain and the problem has not come back.

 

Link: NetTime - Network Time Synchronization Tool

 

http://i.snag.gy/HnlX0.jpg

 

HTH.

[sted]

iirc there is some command you have to run on a dc to make it get its time from a time server but i cant remember what it is. FOund one yesterday thats about 10 mins fast so slowly knocking it back

[VeryPC_Tom_M]

I don't know if it's any help, but I wrote this batch file a while ago:

 

 @echo off
net stop w32time
w32tm /unregister
w32tm /register
net start w32time
w32tm /config /syncfromflags:manual /manualpeerlist:64.90.182.55
w32tm /config /update
w32tm /resync

 

64.90.182.55 is the IP address for the NIST Internet Time server in New York, which I tend to trust more than 'MS' time..

[Achandler]

Its quite simple really, once you have your head round it.

 

Firstly if you have any virtual servers (especially controllers), make sure the time sync between the host and the virtual machine is off.

Then set your main DC to sync with a known good source, there are many available.

Next force a sync on all your DCs one by one, then on each server (check the time source on each server, this should always be a DC).

The usually problem is a virtual machine (DC) getting the info from a physical host (that gets its time from the virtual DC) and so time goes wrong.

[sjatkn]

I think I used this site Configure a time server for Active Directory domain controllers | TechRepublic which are similar those given by @VeryPC_Tom_M. For the time server I use uk.pool.ntp.org rather than one server and so far I have not had any time related issues.

[James_C]

Its quite simple really, once you have your head round it.

 

Firstly if you have any virtual servers (especially controllers), make sure the time sync between the host and the virtual machine is off.

Then set your main DC to sync with a known good source, there are many available.

Next force a sync on all your DCs one by one, then on each server (check the time source on each server, this should always be a DC).

The usually problem is a virtual machine (DC) getting the info from a physical host (that gets its time from the virtual DC) and so time goes wrong.

 

Yeah.. I hear what you are saying but my issues remain. I am running Hyper-V virtual domain controllers. And so far this is the best source of information I have found and I am going to give it another go sometime this week, as mine are only very slowly drifiting out of time. Time Synchronization in Hyper-V - Ben Armstrong - Site Home - MSDN Blogs

 

But i do have a feeling that it may have something to do with a firewall or my HW firewall (netbox blue) which may be stopping my DC from getting time from an external source. As i did find something that was saying that it was attempting to contact the source but was unable to find it.

 

Hope this helps someone. Will advise if I find anything new.

Regards

James