NTP Time Server being held by another server
Posted on 2008-11-13
So here's the deal. We want to take our PDC and make it the authoritative time server for our whole network. Simple enough. Microsoft has a KB on it, and there are a plethora of resources on the net for it. The setup goes fine and everything is set up as it should be.
I go to another server to check and make sure it is pointing to the PDC, and for some reason it is pointing to an older server that was never a domain controller in its existence. This is wierd. We monkey around with the registry on the old server as well as the PDC, but nothing. No matter what workstation or server you are on, if you type "net time" at a command prompt, it will show the time according to the old server.
I tried entering "w32tm /monitor /domain:[domain]" and it showed me both my PDC and the second domain controller and the time offset. Again, wierd.
Does it matter that when I type in "net time" it gives me the old server? Or is there some configuration step we have missed somewhere that tells the network that our PDC is the time keeper? The main thing we are trying to do is make this old server let go of being the master time server, and allow the PDC to take the reigns.
Has anyone ever seen this? Anyone have any ideas? We are open to any solution at this point.