我的w2k3 pdc配置为权威时间服务器.如果我在对等列表中手动指定域中的其他服务器,则它们能够与其同步.如果我尝试从标志’domhier’同步,它将不会重新同步;我收到错误消息
The computer did not resync because no time data was available.
我只能认为它不是在查询pdc.我也尝试设置注册表,如下所示(http://support.microsoft.com/kb/193825).但没有运气(我没有重新启动服务器,我希望我不会,因为它是pdc)
如果您想了解我的配置的更多信息,请告诉我.
编辑1:
我已经将w32time服务配置AnnouceFlags设置为0x05,如www.krr.org/microsoft/authoritative_time_servers.php和其他一些地方所述.
PDC同步到外部时间源(ntp).
我可以从pdc上获取客户端的条形图没问题.
编辑2:
数据包捕获揭示了一些有趣的东西.客户端正在联系正确的服务器,并获得有效的响应,但我仍然收到相同的错误消息.
这是从客户端到服务器的NTP摘录
Flags: 11.. .... = Leap Indicator: alarm condition (clock not synchronized) (3) ..01 1... = Version number: NTP Version 3 (3) .... .011 = Mode: client (3) Peer Clock Stratum: unspecified or unavailable (0) Peer Polling Interval: 10 (1024 sec) Peer Clock Precision: 0.015625 sec Root Delay: 0.0000 sec Root Dispersion: 1.0156 sec Reference Clock ID: NULL Reference Clock Update Time: Sep 1,2010 05:29:39.8170 UTC Originate Time Stamp: NULL Receive Time Stamp: NULL Transmit Time Stamp: Nov 8,2010 01:44:44.1450 UTC Key ID: DC080000
以下是从服务器到客户端的NTP摘录
Flags: 0x1c 00.. .... = Leap Indicator: no warning (0) ..01 1... = Version number: NTP Version 3 (3) .... .100 = Mode: server (4) Peer Clock Stratum: secondary reference (3) Peer Polling Interval: 10 (1024 sec) Peer Clock Precision: 0.00001 sec Root Delay: 0.1484 sec Root Dispersion: 0.1060 sec Reference Clock ID: 192.189.54.17 Reference Clock Update Time: Nov 8,2010 01:18:04.6223 UTC Originate Time Stamp: Nov 8,2010 01:44:44.1450 UTC Receive Time Stamp: Nov 8,2010 01:46:44.1975 UTC Transmit Time Stamp: Nov 8,2010 01:46:44.1975 UTC Key ID: 00000000
编辑3:
dumpc for pdc上的参数
Value Name Value Type Value Data ------------------------------------------------------------------------ ServiceMain REG_SZ SvchostEntry_W32Time ServiceDll REG_EXPAND_SZ C:\WINDOWS\system32\w32time.dll NtpServer REG_SZ bhvmmgt01.domain.com,0x1 Type REG_SZ AllSync
和配置
Value Name Value Type Value Data -------------------------------------------------------------------------- LastClockRate REG_DWORD 156249 MinClockRate REG_DWORD 155860 MaxClockRate REG_DWORD 156640 FrequencyCorrectRate REG_DWORD 4 PollAdjustFactor REG_DWORD 5 LargePhaSEOffset REG_DWORD 50000000 SpikeWatchPeriod REG_DWORD 900 HoldPeriod REG_DWORD 5 LocalClockDispersion REG_DWORD 10 EventLogFlags REG_DWORD 2 PhaseCorrectRate REG_DWORD 7 MinPollInterval REG_DWORD 6 MaxPollInterval REG_DWORD 10 UpdateInterval REG_DWORD 100 MaxNegPhaseCorrection REG_DWORD -1 MaxPosPhaseCorrection REG_DWORD -1 AnnounceFlags REG_DWORD 5 MaxAllowedPhaSEOffset REG_DWORD 300 FileLogSize REG_DWORD 10000000 FileLogName REG_SZ C:\Windows\Temp\w32time.log FileLogEntries REG_SZ 0-300
编辑4:
ReadConfig: Failed. Use default one 'TimeJumpAuditOffset'=0x00007080 DomainHierachy: we are now the domain root. ClockDispln: we're a reliable time service with no time source: LS: 0,TN: 864000000000,WAIT: 86400000
编辑5:
F& ^%ING解决了!好的,我正在阅读有类似问题的人,有些人提到了GPO应用的w32time服务器设置,但是我很早就测试了这个,并且没有通过gpo应用于此服务的设置.其他人说,报告软件可能没有采用一些旧的gpo设置.所以我在注册表中搜索了所有w32time实例.我遇到了一个有趣的密钥,表明服务器上可能运行了一些其他的ntp软件.果然,我查看已安装的软件列表,那里有小F *&%ER.卸载,现在像梦一样工作.
FFFFFFFUUUUUUUUUUUU
在域上的PDC:
w32tm / config / manualpeerlist:“peers”/ syncfromflags:manual / reliable:yes / update
从here获得同行.
在所有服务器和登录脚本中(或者您可以使用组策略):
w32tm / config / syncfromflags:domhier / update
Net Stop w32tm
净启动w32tm
参考:
在PDC上配置w32tm:Microsoft Technet
在计算机上配置w32tm:@L_404_4@