The value of DisableCARetryOnInitialConnect must be set to 1 !!!
CARetryOnInitialConnect does block the SMB access on a Windows Server 2012/ 2012 R2 for 60 seconds until returning an error code (share does not exist) if you access a not existing share on a Windows 2012/2012 R2 Server with activated Failover Cluster Feature (FC does not need to be configured!).
Q&A:
Q: Why does SMB 3.0 wait up to 60 Seconds?
A: During the failover of Fileserver the share is not visible during the failover time. Hence Windows can't test in this timespan whether the share does not exists or wether it is temporarily unavailabe due to a failover operation. CA (Continous Availability) is a feature which allows open fail handles from SMB 3.0 clients to survive a failover of an SMB 3.0 destination.
Q: what are the side effects of DisableCARetryOnInitialConnect =1
A: Windows will immediately return with an error message if a share is not existing.
If a share is temporary not available Windows will fail immediately if the share was never accessed before. Windows will block for 60 seconds if the share was already successfully accessed and is currently not available due to a failover operation.
I strongly recommend to activate DisableCARetryOnInitialConnect =1 on all Windows Server 2012 or later and Windows 8 and later computers (not only the cluster nodes), if there is a chance that they will access Windows Server 2012 or later servers where the Windows Failover Cluster feature was activated (does not need to be configured).
regards
Peter