I got a problem with Windows 7 clients - cannot sync time with Linux NTP server. Windows XP clients sync with the same server without errors.
My Windows 7 clients can get time from public NTP servers through Internet, but not from local servers in the same IP 4 subnet.
From sles11sp2
C:\Windows\system32>w32tm /config /manualpeerlist:192.168.2.99,0x8 /syncfromflags:MANUAL /reliable:yes /update
The command completed successfully.
C:\Windows\system32>net stop w32time
The Windows Time service is stopping.
The Windows Time service was stopped successfully.
C:\Windows\system32>net start w32time
The Windows Time service is starting.
The Windows Time service was started successfully.
C:\Windows\system32>w32tm /resync /rediscover
Sending resync command to local computer
The computer did not resync because only stale time data was available.
From sles10sp3:
C:\Windows\system32>w32tm /config /manualpeerlist:192.168.2.100,0x8 /syncfromflags:MANUAL /reliable:yes /update
The command completed successfully.
C:\Windows\system32>net stop w32time
The Windows Time service is stopping.
The Windows Time service was stopped successfully.
C:\Windows\system32>net start w32time
The Windows Time service is starting.
The Windows Time service was started successfully.
C:\Windows\system32>w32tm /resync /rediscover
Sending resync command to local computer
The computer did not resync because no time data was available.
From public server:
C:\Windows\system32>w32tm /config /manualpeerlist:us.pool.ntp.org,0x8 /syncfromflags:MANUAL /reliable:yes /update
The command completed successfully.
C:\Windows\system32>net stop w32time
The Windows Time service is stopping.
The Windows Time service was stopped successfully.
C:\Windows\system32>net start w32time
The Windows Time service is starting.
The Windows Time service was started successfully.
C:\Windows\system32>w32tm /resync /rediscover
Sending resync command to local computer
The command completed successfully.

August 14th, 2012 3:38am

Hi,
Based on my research, please follow the steps in
Configure a manual time source for a selected client computer to perform the configuration.
If issue persists, please use Network Monitor to troubleshoot the issue.
More reference:
Windows Time Service Tools and Settings
How the Windows Time Service Works
Error message when you run the "w32tm /resync" command to synchronize Windows Server 2003 or Windows SBS to an external time source: "The computer did not resync because no time data was available"
The computer did not resync because no time data was available (w32tm)
Hope this helps.
Jeremy Wu
TechNet Community Support

Hello,
Thank you for a long list of useful links,
I've studied all with the same result in w32tm /resync: The computer did not resync because...
But this looks strange:
C:\Windows\system32>w32tm /monitor /computers:localhost
localhost[[::1]:123]:
ICMP: 0ms delay
NTP: +0.0000000s offset from local clock
RefID: nsbes1.galend.local [192.168.2.100]
Stratum: 2
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.
Also after restarting w32time in System Log I have Time-Service event with Event Id 37:
The time provider NtpClient is currently receiving valid time data from 192.168.2.100,0x8 (ntp.m|0x8|0.0.0.0:123->192.168.2.100:123).

August 19th, 2012 11:52pm

Hello,
What's the result of w32tm /query /source command?
Regards,
DennyPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hello,
Just after sytem startup it looks like:
C:\Windows\system32>w32tm /query /source
The following error occurred: The service has not been started. (0x80070426)
C:\Windows\system32>net start w32time
The Windows Time service is starting.
The Windows Time service was started successfully.
And after few seconds:
C:\Windows\system32>w32tm /query /source
192.168.2.100,0x8
The system log (as it looks in Event Viewer in reverse order):
Information 23.08.2012 07:52:59
Kernel-General 1
None The system time has changed to 2012-08-23T03:52:59.857000000Z from 2012-08-23T03:52:59.857181200Z.
Information 23.08.2012 07:52:59
Time-Service 35
None The time service is now synchronizing the system time with the time source 192.168.2.100,0x8 (ntp.m|0x8|0.0.0.0:123->192.168.2.100:123).
Information 23.08.2012 07:52:59
Kernel-General 1
None The system time has changed to 2012-08-23T03:52:59.857181200Z from 2012-08-23T03:53:10.994140600Z.
Information 23.08.2012 07:52:56
Time-Service 37
None The time provider NtpClient is currently receiving valid time data from 192.168.2.100,0x8 (ntp.m|0x8|0.0.0.0:123->192.168.2.100:123).
Information 23.08.2012 07:52:54
Service Control Manager 7036
None The Windows Time service entered the running state.
Information 23.08.2012 07:52:54
Time-Service 37
None The time provider NtpClient is currently receiving valid time data from 192.168.2.100,0x8 (ntp.m|0x8|0.0.0.0:123->192.168.2.100:123).
Information 23.08.2012 07:52:54
Time-Service 143
None The time service has started advertising as a good time source.
Information 23.08.2012 07:52:54
Time-Service 139
None The time service has started advertising as a time source.

August 22nd, 2012 9:16pm

Hello,
Are the results and events gathered from the NTP server or the win7 client? On the client machine i am afraid that we cannot set it as a reliable time source.
Regards,
DennyPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.