PDC timing services to www.windows.com not accurate.
DoleBludger
>w32tm /stripchart /computer:time.windows.co
m /samples:10 /dataonly
Tracking time.windows.com [207.46.232.182].
Collecting 10 samples.
The current time is 12/16/2009 1:44:11 PM (local time).
13:44:11, error: 0x800705B4
13:44:14, -92.9414991s
13:44:16, -92.9493396s
13:44:18, -92.9585717s
13:44:20, error: 0x800705B4
13:44:23, -92.9586381s
13:44:26, -92.9430413s
13:44:28, -92.9430693s
13:44:30, error: 0x800705B4
13:44:33, -92.9509480s
>net time /querysntp
The current SNTP value is: time.windows.com
I do not know what I have to do to get less error, than 92 sec?
Ace Fekay [MCT]
news:C5130932-DA11-48DE...@microsoft.com...
How did you setup the time source on the PDC Emulator?
Also, curious, are you expecting or trying to get time sync less than 92
seconds? If so, the Windows time service is not that accurate, and you
should expect a 2-3 minute skew. This is something Microsoft even indicates
in a tech article (posted in my blog). If you need something more accurate,
such as for banking transactions or something else where time down to the
second is important, you must use a third party time service.
Read my blog on how to setup the time service on the PDC emulator, how it
works, and limitations. I hope you find it helpful.
Configuring the Windows Time Service for Windows Server
http://msmvps.com/blogs/acefekay/archive/2009/09/18/configuring-the-windows-time-service-for-windows-server.aspx
--
Ace
This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.
Please reply back to the newsgroup or forum for collaboration benefit among
responding engineers, and to help others benefit from your resolution.
Ace Fekay, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA
2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
For urgent issues, please contact Microsoft PSS directly. Please check
http://support.microsoft.com for regional support phone numbers.