我有一个运行Server 2019的域控制器。我还有另外两个区议会。在运行PDC仿真服务器的服务器上,我将其配置为指向海军的时间服务器。
w32tm /config /manualpeerlist:"tick.usno.navy.mil tock.usno.navy.mil ntp2.usno.navy.mil" /syncfromflags:manual /reliable:yes /update
这件事成功地完成了。我重新启动了时间服务:
net stop w32time && net start w32time
过了一会儿,我注意到我的系统在整个领域的时间是错误的。我并不总是在这个领域,所以当我注意到,它比实际时间晚了5分钟。现在已经落后6.5分钟了。
如果我再次重新启动时间服务,然后查询对等点,那么这三种状态都是活动的:
C:\windows\system32>w32tm /query /peers /verbose
#Peers: 3
Peer: ntp2.usno.navy.mil
State: Active
Time Remaining: 54.2426825s
Mode: 1 (Symmetric Active)
Stratum: 0 (unspecified)
PeerPoll Interval: 0 (unspecified)
HostPoll Interval: 6 (64s)
Last Successful Sync Time: (null)
LastSyncError: 0x800705B4 (This operation returned because the timeout period expired. )
LastSyncErrorMsgId: 0x00000000 (Succeeded)
AuthTypeMsgId: 0x0000005A (NoAuth )
Resolve Attempts: 0
ValidDataCounter: 1
Reachability: 2
Peer: tock.usno.navy.mil
State: Active
Time Remaining: 54.2582623s
Mode: 1 (Symmetric Active)
Stratum: 0 (unspecified)
PeerPoll Interval: 0 (unspecified)
HostPoll Interval: 6 (64s)
Last Successful Sync Time: (null)
LastSyncError: 0x800705B4 (This operation returned because the timeout period expired. )
LastSyncErrorMsgId: 0x00000000 (Succeeded)
AuthTypeMsgId: 0x0000005A (NoAuth )
Resolve Attempts: 0
ValidDataCounter: 1
Reachability: 2
Peer: tick.usno.navy.mil
State: Active
Time Remaining: 54.2729373s
Mode: 1 (Symmetric Active)
Stratum: 0 (unspecified)
PeerPoll Interval: 0 (unspecified)
HostPoll Interval: 6 (64s)
Last Successful Sync Time: (null)
LastSyncError: 0x800705B4 (This operation returned because the timeout period expired. )
LastSyncErrorMsgId: 0x00000000 (Succeeded)
AuthTypeMsgId: 0x0000005A (NoAuth )
Resolve Attempts: 0
ValidDataCounter: 1
Reachability: 2
C:\windows\system32>
如果然后运行resync,它会说它没有resync,因为没有可用的时间数据。
如果我对滴答运行条形图,我会得到一个错误。
C:\windows\system32>w32tm /stripchart /computer:tick.usno.navy.mil
Tracking tick.usno.navy.mil [192.5.41.40:123].
The current time is 6/9/2022 11:51:23 AM.
11:51:23, error: 0x800705B4
11:51:26, error: 0x800705B4
11:51:29, error: 0x800705B4
^C
C:\windows\system32>
如果我对正在运行ntp服务的网络交换机运行条形图,并且它从经过身份验证的时间源中获得时间,那么我的时间就结束了:
C:\windows\system32>w32tm /stripchart /computer:*.*.*.1
Tracking *.*.*.1 [*.*.*.1:123].
The current time is 6/9/2022 11:54:00 AM.
11:54:00, d:+00.0016961s o:+396.5884202s [ | @]
11:54:02, d:+00.0015396s o:+396.5886677s [ | @]
11:54:04, d:+00.0017477s o:+396.5889037s [ | @]
^C
C:\windows\system32>
另外,在大约4或5分钟后,我的对等点会切换到挂起的状态:
C:\windows\system32>w32tm /query /peers /verbose
#Peers: 3
Peer: ntp2.usno.navy.mil
State: Pending
Time Remaining: 848.7510630s
Mode: 0 (reserved)
Stratum: 0 (unspecified)
PeerPoll Interval: 0 (unspecified)
HostPoll Interval: 0 (unspecified)
Last Successful Sync Time: (null)
LastSyncError: 0x00000000 (Succeeded)
LastSyncErrorMsgId: 0x00000000 (Succeeded)
AuthTypeMsgId: 0x0000005A (NoAuth )
Resolve Attempts: 1
ValidDataCounter: 0
Reachability: 0
Peer: tick.usno.navy.mil
State: Pending
Time Remaining: 848.7514333s
Mode: 0 (reserved)
Stratum: 0 (unspecified)
PeerPoll Interval: 0 (unspecified)
HostPoll Interval: 0 (unspecified)
Last Successful Sync Time: (null)
LastSyncError: 0x00000000 (Succeeded)
LastSyncErrorMsgId: 0x00000000 (Succeeded)
AuthTypeMsgId: 0x0000005A (NoAuth )
Resolve Attempts: 1
ValidDataCounter: 0
Reachability: 0
Peer: tock.usno.navy.mil
State: Pending
Time Remaining: 848.7518290s
Mode: 0 (reserved)
Stratum: 0 (unspecified)
PeerPoll Interval: 0 (unspecified)
HostPoll Interval: 0 (unspecified)
Last Successful Sync Time: (null)
LastSyncError: 0x00000000 (Succeeded)
LastSyncErrorMsgId: 0x00000000 (Succeeded)
AuthTypeMsgId: 0x0000005A (NoAuth )
Resolve Attempts: 1
ValidDataCounter: 0
Reachability: 0
C:\windows\system32>
将我的对等列表更改为网络交换机,我仍然有所有这些问题。这个系统是一个VM。有一段时间,我将其配置为与主机同步时间,但几个小时前我已经删除了该设置,而且它似乎离正确的时间更远了。我也重新启动了DC,没有改变。
我不知道还有什么办法让它有正确的时间。我还将包括查询状态的结果。我也没有在日志中看到任何错误,当我设置w32tm调试日志时,没有什么会跳出我的视线。
C:\windows\system32>w32tm /query /status
Leap Indicator: 0(no warning)
Stratum: 1 (primary reference - syncd by radio clock)
Precision: -23 (119.209ns per tick)
Root Delay: 0.0000000s
Root Dispersion: 10.0000000s
ReferenceId: 0x4C4F434C (source name: "LOCL")
Last Successful Sync Time: 6/9/2022 11:50:45 AM
Source: Local CMOS Clock
Poll Interval: 6 (64s)
我很感谢你的帮助。
发布于 2022-06-16 13:13:25
我想我的问题是两方面的。首先,我最初遵循的指令是,如果我是一个森林根DC。但是从那以后,我们重新开始,我是一个子域,所以我应该把树根DC作为我的来源。一旦我找到了正确的来源,事情就为我解决了。另一个问题是,我的网络团队在配置NTP时和注意到问题之间的一段时间内阻塞了到海军服务器的NTP通信量。这就是为什么我的DC不断显示本地CMOS作为源。但是,当我尝试Stacker的建议时,即使我没有配置它,源也更改为林根DC。下面的链接是建议本地CMOS源可能由防火墙块引起的文章。https://www.renanrodrigues.com/post/how-to-configure-ntp-server-in-active-directory-step-by-step
发布于 2022-06-14 12:59:10
问题是你的来源不是本地的CMOS,而不是海军。
w32tm.exe /config /syncfromflags:manual /manualpeerlist:131.107.13.100,0x8 /reliable:yes /update
w32tm.exe /config /update
打开组策略管理控制台,创建新的GPO,打开GPO并导航到计算机设置、->管理模板、->系统、Windows时间服务、->时间提供者,双击配置Windows客户端。将状态设置为已启用配置Typeto配置NTPServerto指向时间服务器的IP地址,然后是,0x8,例如: 131.107.13.100,0x8关闭组策略编辑器,关闭组策略管理控制台的安全筛选窗格中的组策略编辑器,为新创建的策略删除经过身份验证的用户,并添加包含PDC模拟器角色的机器,将GPO链接到域ControllersOU
https://serverfault.com/questions/1102908
复制相似问题