Running Windows Server 2012 failover cluster on Windows Server 2003 domain

Recently I deployed several SQL Server 2012 failover clusters on top of Windows Server 2012. Not a big news, except they were deployed on Windows Server 2003 domain. If someone is wondering – this is officially supported scenario. Setup of both, Windows and SQL Server clusters, finished without any errors. For a while everything was looking good and then I noticed some errors on some of the clusters. I noticed three type of errors in Windows Eventlog:

Event ID: 4
The kerberos client received a KRB_AP_ERR_MODIFIED error from the server <cluster-file-server$>. The target name used was cifs/cluster-file-server.domain.com.
This indicates that the password used to encrypt the kerberos service ticket is different than that on the target server.

Event ID: 1228
Cluster network name resource ‘Cluster Name’ encountered an error enabling the network name on this node. The reason for the failure was: ‘Unable to obtain a logon token’. The error code was ‘1326’. You may take the network name resource offline and online again to retry.

Event ID: 1196
Cluster network name resource ‘Cluster Name’ failed registration of one or more associated DNS name(s) for the following reason: The handle is invalid. Ensure that the network adapters associated with dependent IP address resources are configured with at least one accessible DNS server.

I also noticed that sometimes I couldn’t access some shared folders using cluster’s Client Access Point name, but only from Windows Server 2003 machines. Messages in Eventlog were somewhat misleading; I checked DNS, delegation in AD objects, CNOs etc., but I couldn’t find the reason. Cluster log did’t help either. After searching the web I came across the MS knowledge base article Can’t access a resource that is hosted on a Windows Server 2012-based failover cluster. Solution is to install at least mentioned Hotfix, but if it is a new cluster I recommend installing the update rollup. Please make sure that after installing Hotfix you follow Post-installation instructions for clusters already experiencing problems.