Re: An issue with SQL 2005 and Kerberos...

Camilo,

One possibility is that you are the victim of a duplicate SPN. Here are a
couple of links discussing that.
http://www.planetmagpie.com/itconsulting/technotes-060205.aspx
http://support.microsoft.com/kb/832109

I am not an expert on this, but I have experienced this problem a couple of
times and had to get a domain admin to fix it.

RLF

"Camilo" <Camilo@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6EF1C1A1-6041-4856-9489-9296D1880B3A@xxxxxxxxxxxxxxxx
I am having trouble getting SQL 2005 to authenticate using Kerberos.
Regardless of what I try the authentication always goes through NTLM.
Following is the situation:

We have a test domain setup with a substantial amount of servers. I know
that Kerberos is properly setup in that domain because many different test
SharePoint deployments under different configurations has been
successfully
setup and it all cases it has been verified that Kerberos is being used as
the authentication mechanism between servers.

However, all the connections from these SharePoint servers to the SQL
Server
2005 servers are authenticating using NTLM. The way I am checking the
authentication mechanism is running the following query and checking the
value displayed in the auth_scheme column:

Use Master
select * from sys.dm_exec_connections

I tried removing IIS from the equation and tested connecting from one SQL
box in the same domain to another one using SQL Server Management Studio.
The
results are the same, the server is authenticating using NTLM.

All the SQL instances I am working with are 1+1 Clusters with two active
instances. They are all installed over Windows 2003 Server and with SQL
2005
SP2 applied. I checked in the cluster administrator tool and Kerberos
seems
to be enabled (the check box is selected in the cluster name resource and
everything is online).

Could someone give me some guidance on how to troubleshoot this problem?

Thanks!


Camilo




.

Relevant Pages

  • Re: Adding 3 nodes to a cluster
    ... So you need to add the nodes to the cluster using the Cluster tool. ... Then extend the existing instance to the new nodes using the installer. ... Senior SQL Infrastructure Consultant ... servers acting as a failover in case one of the servers fails. ...
    (microsoft.public.sqlserver.clustering)
  • Re: Adding 3 nodes to a cluster
    ... First you use the cluster admin tool to add the machines as nodes to the cluster. ... Then you run the SQL installer to install binaries on the newly added nodes and allow the new nodes to host the existing instances. ... >>>I need to add these new servers as seperate instances in the SQL ...
    (microsoft.public.sqlserver.clustering)
  • WIN2K3 SP1, SQL Server / MSDTC Issue
    ... I can get SQL Installed ok and everything works fine until I set ... Setup Network Connections (for internal cluster comms and public network) ... Reboot Servers ...
    (microsoft.public.sqlserver.clustering)
  • RE: New SQL 2005 Cluster Questions
    ... You have only one SQL instance in the cluster. ... So, from what I am seeing is I have no choice but to DC the servers, cluster ... Win2003 Ent and then install SQL 2005 Ent onto this cluster. ...
    (microsoft.public.sqlserver.clustering)
  • Re: Adding 3 nodes to a cluster
    ... I need to add these new servers as seperate instances in the SQL cluster. ...
    (microsoft.public.sqlserver.clustering)