Hi murtazak,
The most appropriate troubleshooting method for your problem would be as mentioned by Harry_Redl in his post. But that involves a series of commands to be executed from the systemshell. You may also need to check if any device in between your storage controller and the DC is blocking port 123. Increasing the verbosity of EMS logging facility may be helpful to get some clue. Have you opened a support case with NetApp? They should be able to help you with more troubleshooting and a fix.
Its a known issue with DOT8.x and Windows Operating systems that uses W32time NTP service ( https://kb.netapp.com/support/index?page=content&actp=LIST&id=2015314 ). I am not really a microsoft guy, but as far as I know, OS versions upto windows server2012 uses w32time as the timeserver. Its not a good idea to use a Windows server syncing to its own hardware clock as an NTP source. It becomes worse when your windows runs inside a Virtual Machine. I would not choose that as an option If I were you.
From microsoft's KB article ( https://support.microsoft.com/en-us/kb/939322 )
"We do not guarantee and we do not support the accuracy of the W32Time service between nodes on a network. The W32Time service is not a full-featured NTP solution that meets time-sensitive application needs. The W32Time service is primarily designed to do the following:
- Make the Kerberos version 5 authentication protocol work.
- Provide loose sync time for client computers."
If this post resolved your issue, help others by selecting ACCEPT AS SOLUTION or adding a KUDO. Cannot find the answer you need? No need to open a support case - just CHAT and we’ll handle it for you.
