Monday, February 07, 2005 6:38 PM
bart
Running a Windows Server 2003 standalone DC (on your laptop) - solution for problems with NTP
A couple of minutes ago I was connecting to my main machine over here using Terminal Services and I noticed a time difference of 20 minutes with the real GTM+1 clock :-(. The problem is actually that in a DC scenario, the servers synchronize their clocks internally on the network, instead of going out to an NTP server somewhere on the internet. Unfortunately w32tm /resync did not help (of course not, since the NTP service wasn't configured for external NTP-synchronization, so I searched the Microsoft KB for more info on how to configure a DC in Windows Server 2003 to sync with the time.windows.com NTP on the internet. More info can be found over here: http://support.microsoft.com/kb/816042/en-us.
Note: w32tm is another cool Windows command that's relatively unknown. It works together with the W32Time service and allows you to configure various parameters, show stats, query the time service of various computers in the domain and to retrieve timezone information. With commands like these you'll definitely score on your party :-).
Del.icio.us |
Digg It |
Technorati |
Blinklist |
Furl |
reddit |
DotNetKicks
Filed under: Personal, Microsoft