• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1325
  • Last Modified:

Cannot generate SSPI context

Hello...  I am a SQL Server machine...it has SQL Server 2005 and 2008 Express...

When trying to use the SQL Server Management Studio to remotely connect to it...I get a "Cannot Generate SSPI Context" error...

I need help...  Thanks...

0
StrongD1
Asked:
StrongD1
  • 3
  • 2
1 Solution
 
chapmandewCommented:
have you changed your pwd recently?
0
 
StrongD1Author Commented:
No... not at all...  this is a small "Lab network" we built to do software development on.  I am a developer, not a SQL Server DBA.... so SQL Server admin stuff is new to me.
0
 
StrongD1Author Commented:
Ok...I was able to get in.  Here is what I did for the record.

After reading a ton on here and a ton on Google about this error, a lot of people were saying it could be the Domain Controller...  My DC is a Windows 2003 Enterprise.... my SQL Server DB is on a Windows 2003 Standard.   So I started poking around the DC and I noticed when the Window firewall is on the SQL Server DB machine took forever to logon to the domain... it would take 5 minutes or so...  when I turned off the firewall on the DC, it would login in 5 seconds....   so I turned off the firewall on the DC and everything works...

Does that make sense to anyone?  That is all I did... I didn't configure anything other turning off the firewall on the DC.

0
Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

 
asadeenCommented:
I had this issue before and resolved it. this is due to SPN issue. follow this to resovle Resolution:
To configure the SQL Server service to create SPNs dynamically, follow these steps:
1.      Click Start, click Run, type Adsiedit.msc, and then click OK.
2.      In the ADSI Edit snap-in, expand Domain [DomainName], expand DC= RootDomainName, expand CN=Users, right-click CN= AccountName, and then click Properties.

Notes
"      DomainName is a placeholder for the name of the domain.
"      RootDomainName is a placeholder for the name of the root domain.
"      AccountName is a placeholder for the account that you specify to start the SQL Server service.
"      If you specify the Local System account to start the SQL Server service, AccountName is a placeholder for the account that you use to log on to Microsoft Windows.
"      If you specify a domain user account to start the SQL Server service, AccountName is a placeholder for the domain user account.

3.      In the CN= AccountName Properties dialog box, click the Security tab.
4.      On the Security tab, click Advanced.
5.      In the Advanced Security Settings dialog box, make sure that SELF is listed under Permission entries.

If SELF is not listed, click Add, and then add SELF.
6.      Under Permission entries, click SELF, and then click Edit.
7.      In the Permission Entry dialog box, click the Properties tab.
8.      On the Properties tab, click This object only in the Apply onto list, and then make sure that the check boxes for the following permissions are selected under Permissions:
"      Read servicePrincipalName
"      Write servicePrincipalName

9.      Click OK three times, and then exit the ADSI Edit snap-in.

0
 
asadeenCommented:
also check the SPN using ldifde.
0
 
StrongD1Author Commented:
Yeah... thanks for the info asadeen:....  that is good to know..

Hopefully we don't run into this problem again...   It seems our domain controllers firewall was causing problems authenicating the SQL Server machine.... I don't think SQL Server machine was even on the domain....  Who know... but thanks for the info.

0
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.

Join & Write a Comment

Featured Post

Cloud Class® Course: Ruby Fundamentals

This course will introduce you to Ruby, as well as teach you about classes, methods, variables, data structures, loops, enumerable methods, and finishing touches.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now