event id 50 win32time错误频出解析（多方转载） sign在这里

原创

isee131 2011-04-18 09:52:44 博主文章分类：其他 ©著作权

©著作权归作者所有：来自51CTO博客作者isee131的原创作品，请联系作者获取转载授权，否则将追究法律责任

具体内容对号入座，很详细

http://www.msfn.org/board/topic/67060-problem-synchronizing-time-on-2k3-pdc-with-external-source/

I have Windows 2003 server (SP1) standard edition running on my domain controller. At the moment, all the domain clients synchronize their local times with this PDC with no problems. The time on the domain controller, however, is not accurate. I am trying to get it to synchronize with an external time server: time.nist.gov.

I started off following the instructions in this article:
http://support.microsoft.com/kb/816042
They don't work.

When you run the command: w32tm /resync, you receive the error: "The computer did not resync because no time data was available." A warning is also posted to the event log: "Time Provider NtpClient: This machine is configured to use the domain hierarchy to determine its time source, but it is the PDC emulator..."

Digging on the web, I found only more and more articles either repeating the steps from the Microsoft article or stating similar problems, with no solutions, to mine.

Firstly, let me declare the obvious: port 123 (SNTP) was forwarded to my domain controllers IP, both TCP and UDP, on my ADSL router. (NAT)

I tried my silver-bullet: unregister w32time and start again. I created the following batch script:

net stop w32time

w32tm /unregister
w32tm /register

w32tm /config /manualpeerlist:192.43.244.18 /syncfromflags:MANUAL /reliable:YES

net start w32time

w32tm /config /update

w32tm /resync /rediscover

The first line stops the NT service. You then unregister it and re-register it, recreating all the registry keys with default values, giving you a standard starting point. After that, I configure it, specifying an NTP server's ip address as a peer (this IP is time.nist.gov) and that it should synch from the manual peer list. I also mark this server as a reliable time server. I then start the service again, tell it to update its configuration, just in case, and then resync.

You guessed it, same error in the command line ("no time data was available") and same warning in the system event log! Argh!

I have to ask the question: Does w32time actually work on windows 2003?

Has anyone got any insight into this problem? There must be a solution, I am sure that the vast majority of admins would like their network to have accurate time!

Thanks,
Stephen Martindale

如何在 Windows Server 中配置权威时间服务器http://support.microsoft.com/kb/816042

Problem Events - On the PDC Emulator

http://www.petenetlive.com/KB/Article/0000112.htm

eventid

http://www.eventid.net/display.asp?eventid=24&eventno=3620&source=W32Time&phase=1