The bug exists in Ver 3.1.2.217 at windows 2008 R2(32 and 64). I solve the Bug Using the following method:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpServer\Enabled =1;
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config\AnnounceFlags = 5;
The last Ver 3.1.4.220 does not have the bug.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Those registry settings are for the Windows built in Time service and as such are unrelated to NetTime.
If you were using the Windows built in time client to sync to NetTime, then yes, there were changes with 3.14 to fix compatibility with the Windows Time Client.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Can you provide more information - do you get any error messages shown in the NetTime log file?
Have you made sure that the Windows Time Service is disabled?
The bug exists in Ver 3.1.2.217 at windows 2008 R2(32 and 64). I solve the Bug Using the following method:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpServer\Enabled =1;
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config\AnnounceFlags = 5;
The last Ver 3.1.4.220 does not have the bug.
Those registry settings are for the Windows built in Time service and as such are unrelated to NetTime.
If you were using the Windows built in time client to sync to NetTime, then yes, there were changes with 3.14 to fix compatibility with the Windows Time Client.