New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows NTP client time sync failed #6480
Comments
Workaround The issue origin seems to be in the DC installation procedure. The install procedure does not fix the filesystem group owner of
Instead the upgrade procedure fixes it with the following action:
Run it manually to fix the bug. |
in
|
Test case 1 Check the new package correctly fixes an existing installation:
Ownership must change from Test case 2 Check the bug is not reproducible in a new installation. |
Tested: VERIFIED The package in testing fixes ownerships on both updated and new DC installations. |
in
|
Windows clients cannot synchronize their clock with a new installation of nethserver-dc (the local AD accounts provider).
Steps to reproduce
w32tm /resync
commandExpected behavior
The client clock gets synchronized.
Actual behavior
The sync command fails.
Components
nethserver-dc-1.8.1-1.ns7.x86_64
Thanks to @syntaxerrormmm @lucagasparini @nrauso
The text was updated successfully, but these errors were encountered: