I know this looked like it was turning towards a time syncronization issue, but I found an interesting correlation with a problem I'm currently having. Very similiar in nature, except that the minor error I'm receiving is "Server not found in Kerberos database".
Now, the only time this occurs is when one of the data movers is attempting to communicate with our domain controllers which are both w2k8-64bit and virtualized servers. I'm digging deeper into this and was wondering if there was ever a solution found for this thread. The forum post says there's been no answer in the last two years and I'm curious if the problem just went away, or if you just learned to live with it
I'm sorry if we weren't clear enough. The "clock skew" messages only occur if the Data Mover time is more than 5 minutes off of the Domain Controller time to which you are trying to authenticate, so somebody's clock is off. This is usually an error with the Celerra. But sometimes it can be an issue with that particular Domain Controller.
The "server not found" messages are a little tougher to decode; there is more than one issue which can cause such a message. If you haven't done so already, open a Service Request to clear that up.