Hi, I have one client that will occasionally show an incorrect timestamp (last modified) on a clustered volume.
It is always exactly 30 minutes behind. A restart will temporarily fix the issue, but seems to eventually happen again.
The windows clock is correct, as are the timestamps when viewed from another workstation.
Files saved to the local workstation show correct modified date.

any ideas?