Clustering question: Why would the sql server name resource fail to maintain the computer account in AD?
- From: "Wilson U" <wilson_u@xxxxxxxxxxx>
- Date: Sat, 23 Dec 2006 15:24:43 -0800
Hello,
We have SQL 2005 installed on Windows 2003 active/passive cluster. A domain
account is used in the cluster setup. The sql server name has the 'Enable
kerberos authentication' checked to register and maintain its record in AD.
It can create the computer object in AD but about every 60 days, the 'Enable
kerberos authentication' needs to be unchecked and rechecked to continue to
allow kerberos authentication.
About 60 days after the registration, we begin to see failures in tasks we
have to connect to the sql server name by unc using kerberos authentication.
The authentication shows up in the sql server as anonymous on the sql
server side as it seems it could not negotiate kerberos authentication with
the calling server. One of the times this went its full course, the
authentication issues spread to all servers using kerberos authentication
and then the computer object is no longer seen in AD until a manual uncheck
and recheck of the 'Enable kerberos authentication' was made.
Any one have any ideas on why this is happening?
Thanks,
Wilson
.
- Follow-Ups:
- Prev by Date: Re: Unable to Apply SP4 to SQL 2000 Cluster (new Node)
- Next by Date: Re: Clustering question: Why would the sql server name resource fail to maintain the computer account in AD?
- Previous by thread: Re: Getting Cluster Metadata
- Next by thread: Re: Clustering question: Why would the sql server name resource fail to maintain the computer account in AD?
- Index(es):
Relevant Pages
|
