Problem generating SSPI Context with SQL 2000 and Windows 2000 Server SP3

When I installed SQL Server, I set the user that starts the SQL Server Service to the Local System account and specified that SQL 2000 should use Mixed Mode for authentication.  Under this setup, the SQL Server works fine using both windows authentication and sql server authentication.  

My problem started because I want to switch the service startup user to a domain user.  When I switch the startup user from LocalSystem to a domain account, SQL Server throws an error stating that it "Cannot Generate an SSPI Context".  Therefore I cannot login to the SQL Server using Windows Authentication.  If I use SQL Server authentication everything works normally.  Changing the startup account back to LocalSystem will allow full access to the SQL Server.  

We only have one domain so there are no Cross-domain communitcation issues.  The machines trying to connect to the SQL Server are Windows XP (SP1).  The domain user account I'm trying to use for service startup is a local administrator on the SQL Server and is in the System Administrators role in SQL Server.  

Any help would be appreciated.  
jecliverAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Brendt HessSenior DBACommented:
Check this MS Article:

http://support.microsoft.com/kb/843248

As a test, use this workaround and see if it works:

To work around this problem, manually create a host entry for the IP address in the client computer

If this does not solve the issue, look at:
http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B811889&Product=sql
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
ShogunWadeCommented:
have to given the domain account the approriate windows security settings and rights?
0
Brendt HessSenior DBACommented:
A couple more things to look at:

http://support.microsoft.com/kb/269541  (a possibility)

- or -

http://support.microsoft.com/?id=814401  (I doubt it - your server *is* connected to the domain, isn't it?)

0
jecliverAuthor Commented:
From everything I can see the server is set up to correctly process windows authentication requests.  I'm further convinced of this because when the server is set up with the LocalSystem account starting the SQL Service the SQL Server can generate the sspi context with no problems.

In answer to ShogunWade's question, the user is a local administrator and in the SQL administrator role.  The domain user is also trusted for delegation.  

I'm trying to work through the troubleshooting guide in http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B811889&Product=sql and so far I'm compliant with everything in it.  

I feel like this is some sort of permissions issue because it works when one user starts the service, but not the other, but I can't figure out how.  I don't know how many more permissions I can give the user!  
0
Brendt HessSenior DBACommented:
One more possibility, from

http://www.experts-exchange.com/Databases/Microsoft_SQL_Server/Q_20826061.html

Fully qualify the server name (e.g. Server.DomainName.Com)

It has something to do with the way XP utilizes the IP protocol

--------------------------------------

And one more:

You may receive the following error message because of problems with Windows authentication:

Cannot generate SSPI Context

The following problems may cause authentication and security issues:
•      Problems occur with NTLM authentication or with Kerberos authentication.
•      The domain controller cannot be contacted because of connectivity issues.
•      Problems occur with trust relationships across domains.

0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.