Welcome to
Help Desk

Product Updates
Ideas Contact Support

How do I synchronize the Storage Sync Server clock with Domain Controller?


If you love Storage Sync, try Smart Cache, Egnyte's next-gen hybrid technology. Egnyte has been investing heavily in Smart Cache -- it combines the performance and scalability of Storage Sync with intelligent caching technology, single drive letter, global file locking, and much more. Learn more here.


Storage Sync requires the system clock to be synchronized with the Domain Controller's clock (DC) if users are authenticated to the share using their Active Directory credentials. The internal clock for Storage Sync must be set to within 5 minutes of the DC clock. If the clocks are not synchronized, the Kerberos authentication will fail.

Users may also receive the error below which occurs when a drive tries to re-connect to the Storage Sync share. 

"The server's clock is not synchronized with the primary domain controller"



Manually re-sync the clocks

Manually re-syncing the clock can be invoked by running the command below within your Storage Sync VM.

net time set -S ipaddress (Replace ipaddress with the Domain Controller IP) 

Configuring NTP to sync the clocks automatically 

The steps below will allow the Storage Sync clock to always be in sync with an NTP server and the time difference will be adjusted slowly.

  • Make a backup of the /etc/ntp.conf file.

                cp /etc/ntp.conf /etc/ntp.conf.orig

  • Open ntp.conf file using VI and comment predefined ntpservers using # as prefix.
  • Add the desired NTP server address, typically your DC.
  • Add another line similar to the one above if you have multiple NTP servers or wish to use public ones.
  • Come out of the VI editor and Stop the NTP services.

               /etc/init.d/ntpd stop

  • Sync the ELC time with NTP server.

               ntpdate NTP.SERVER.ADDRESS

  • Start the NTP daemon.

               /etc/init.d/ntpd start

To run at boot up, turn on server chkconfig ntpd on

Note: If the time is not in sync, then stop the NTP service again, run ntpdate NTP.SERVER.ADDRESS and then start the NTP service.

Was this article helpful?
0 out of 0 found this helpful

For technical assistance, please contact us.