Jan 29, 2010 02:30 PM|katuil|LINK
Sorry, I forgot to post the solution that I found. The issue from what I can remember dealt with NT Auth environment and a SQL Cluster. This issue does not arise when you do not have the SQL Cluster. When a SQL Server is installed into a clustered environment
there's no SPN's created for the virtual servers. In order for NT Auth to function, the SPN's must be present. When SQL Server is installed in a non-cluster environment, the server is physical and when the server joins the domain the SPN is created at that
time. For virtual servers in a clustered environment the SPN's are not created and you have to use setspn.exe to create the SPN's for the server. Be sure that you allow ample time for this to propagate throughout the network, otherwise you will see the same
error. I waited a full 24 hours and then tested and the issue was resolved. This is something that Microsoft does not have documented in this manner. Only how to create a spn but not that they are not created in a cluster environment.