Windows 2003 Domain Controller receiving the wrong time and affecting my Windows 2003 Terminal Server and Windows 2008 Database Server
Posted on 2014-02-01
As of yesterday morning my Windows 2003 Domain Controller is receiving the wrong time and off by several hours which is a big issue because my 2003 Terminal Server and 2008 database server are dependent upon the 2003 DC for the current time. The reason this is a big issue because the 2003 TS Server and 2008 DB Server host my ERP system for my users and if these systems reflect the wrong time it hurts manufacturing times, employee clock in times, and reports.
I believe once I find out what's going on with the 2003 Domain Controller all else will fall into place being that my other servers look to the dc for the correct time. The only thing is my 2003 DC looks for another server at another one of our locations for it's time. I was able to get to the other server and check it's time which was correct.
For the time being I stopped the Windows Time Service and set the clocks to the right time manually but I'm receiving all types of replication, group policies, and dns errors due to me stopping it.
I would also like to know what could have caused this matter because my servers and the systems been fine for years. At the end of the day, I would just like the time to come from my 2003 DC only, instead of my DC looking for another DC for time at our other sites.
Any help with resolving this matter is greatly appreciated.