Date and/or Time incorrect? Why is CIFS complaining about Kerberos time issues?

Unlike a real Filer/NearStore the simulator takes it's time and date directly from the hosting Linux machine. The Filer ignores attempts to change the time via it's management interfaces such as the CLI or FilerView.

NetApp strongly suggests that you enable synchronization between your Linux host and a properly configured time source. This should be documented in your Linux manual set or VMware tools documentations if using VMware.

That said for a lot of environments any effects of incorrectly set date/time will not be noticed (e.g. non-Kerberos NFS, CIFS in Workgroup mode). When using CIFS in a Windows 2000/Windows 2003 domain or in any environment that relies on Kerberos it is vital that the date and time are correctly synchronized. Failure to do this will cause much angst.

Additionally remember that you should still ensure that the time zone is set correctly in the simulator, inside Linux, and on your client.