Problem : Windows Time Service some client side computers not syncing
I have a problem with our time server, as far as I can tell the PDC is fine, and it is authenticating with our other domain controllers. I just recently setup an NTP server.
As you can see, all DCs are in sync with the PDC
C:\>w32tm /monitor
syd-dc01.########.com.au *** PDC ***[192.168.1.2:123]:
ICMP: 35ms delay
NTP: +0.0000000s offset from syd-dc01.#############.com
RefID: warrane.connect.com.au [192.189.54.33]
Stratum: 3
syd-dc02.###########.com.a
ICMP: 46ms delay
NTP: -0.0009876s offset from syd-dc01.########.com.au
RefID: syd-dc01.################.
Stratum: 4
melbsvr01.#########.com.au
ICMP: 0ms delay
NTP: +0.0076823s offset from syd-dc01.#########.com.au
RefID: syd-dc01.##########.com.au
Stratum: 4
pthsvr01[192.168.2.200:123
ICMP: 57ms delay
NTP: +0.0279342s offset from syd-dc01.########.com.au
RefID: syd-dc01.##########.com.au
Stratum: 4
Warning:
Reverse name resolution is best effort. It may not be
correct since RefID field in time packets differs across
NTP implementations and may not be using IP addresses.
On a working system I get this below.
C:\>w32tm /query /peers
#Peers: 1
Peer: syd-dc01.#########.com.au
State: Active
Time Remaining: 771.4498468s
Mode: 3 (Client)
Stratum: 3 (secondary reference
PeerPoll Interval: 10 (1024s)
HostPoll Interval: 10 (1024s)
And on the systems that don’t work, I get this
Peer:
State: Pending
Time Remaining: 0.0000000s
Mode: 0 (reserved)
Stratum: 0 (unspecified)
PeerPoll Interval: 0 (unspecified)
HostPoll Interval: 0 (unspecified)
There is no pattern to the areas that work and don’t work so it couldn’t be the Group Policy, some don’t work in Syd and some don’t work in Melb. I’ve noticed that most of the systems that don’t sync are notebooks not sure if it’s a coincidental.
Is there any way to get the workstations to sync with the DC in w32tm commands?
Solution: Windows Time Service some client side computers not syncing
“net time” is a deprecated command and should not be used anymore; it’s a one-off . It relies on NetBIOS and will not use the time service to sync.
Could this be a firewall issue, especially on the client side? The time service requires connects to UDP port 123.
If the event log doesn’t show anything useful, you can try it with the time service log:
How to turn on debug logging in the Windows Time Service http://support.microsoft.c
