Data Domain: CIFS and NTP Time Synchronization Validation and Configuration
Summary: This article explains how to manage time synchronization on systems integrated with Active Directory (AD). It includes steps to verify time sync configuration, detect potential conflicts between Network Time Protocol (NTP) and AD time control. It also provides commands to disable Common Internet File System (CIFS) time sync and ensure proper time management. It also includes validation steps using logs and system status checks to ensure correct configuration. ...
This article applies to
This article does not apply to
This article is not tied to any specific product.
Not all product versions are identified in this article.
Symptoms
- Unexpected system time changes
- Authentication or Kerberos errors
- Time drifts across domain systems
- Conflicting time updates from NTP and AD
- Log entries showing frequent time adjustments (
ADSyncTimeToDC)
Cause
Both NTP and Active Directory are attempting to control system time, leading to conflicts. When CIFS time sync is enabled alongside NTP on AD-integrated systems, it can result in time drift, authentication issues, and system instability.
Resolution
Follow these steps to identify and resolve time synchronization conflicts on systems integrated with Active Directory:
- Check if the System is Joined to Active Directory:
Run the following command:
cifs troubleshooting domaininfo
Look for the line:
[Authentication provider: lsa-activedirectory-provider]
If this provider is listed, the system is using Active Directory for authentication and may also receive time sync from it. You can get this information from Autosupports.
- Check NTP Status:
Run:
ntp status Example output: Status Enabled Current Clock Time Fri Mar 14 11:04:17.535 2025 Clock Last Synchronized Fri Mar 14 10:53:04.617 2025 Clock Last Synchronized With Time Server 10.92.32.52
If NTP is enabled while the system is joined to AD, this can cause time synchronization conflicts.
- Review Time Sync Logs:
Run the following command to check for time changes triggered by AD:
grep ADSync cifs.log Example output: Mar 4 02:41:26 aurdd5246 lsass: ALWAYS: [24531/...] [lsass] ADSyncTimeToDC: Attempting to change System Time, from [Tue Mar 4 02:41:26 2025 ] to [Fri May 2 20:19:46 2025 ] May 2 20:34:46 aurdd5246 lsass: ALWAYS: [24531/...] [lsass] ADSyncTimeToDC: Attempting to change System Time, from [Fri May 2 20:34:46 2025 ] to [Tue Mar 4 02:56:25 2025 ]
These entries indicate that Active Directory is trying to control the system time, which can conflict with NTP if both are enabled.
- Determine the Resolution Path:
- If AD is configured and NTP is enabled, this is a misconfiguration.
To avoid time conflicts:
Disable NTP and allow Active Directory to manage system time.
- If only one method is active (either NTP or AD), no action is required.
The system is correctly configured.
Affected Products
Data DomainArticle Properties
Article Number: 000305261
Article Type: Solution
Last Modified: 10 Dec 2025
Version: 3
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.