Ideally, if the time difference between the storage system and the DC is greater than 5 minutes, only then a CIFS authentication failure will occur.
I would suggest, instead of using 'DC' as time-server, use external NTP server. External NTP server enables the storage array to automatically synchronize the controller's clocks with an external host . The controller periodically queries the configured NTP server, and then uses the results to update its internal time-of-day clock.
Why do we have to keep adjusting time on Storage to Sync it to AD? This is happening on daily basis. The environment has two NTP set. A time skew of just two minutes makes our shares inaccessible!
I must mention that we have two ADs which we use as NTP Servers. Strangely, we keep adjusting time on our storage every other day! What could be the problem?
Ideally, if the time difference between the storage system and the DC is greater than 5 minutes, only then a CIFS authentication failure will occur.
I would suggest, instead of using 'DC' as time-server, use external NTP server. External NTP server enables the storage array to automatically synchronize the controller's clocks with an external host . The controller periodically queries the configured NTP server, and then uses the results to update its internal time-of-day clock.
