Discussion:
Cannot generate SSPI context
(too old to reply)
Anatoli
2006-08-17 02:30:01 UTC
Permalink
Hi,

Im having trouble connecting to the SQL2005 default instance installed on
one of my sql servers within my domain. I have a second SQL2005 server that I
can connect to just fine. Both are in the same OU.

This particular server, I can connect to AS2005, but not to SQL2005. I keep
getting the 'Cannot generate SSPI context. (.Net SqlClient Data Provider)'
error. I've not changed anything in terms of settings on my PC, nor have any
settings been changed on the SQL server, though I was able to connect to
SQL2005 for this server last week. Something obviously has changed, but I
have no idea where to look. One of the other SysAdmins has no problems
connecting to the database.

I'm hoping this is just something simple to fix.

regards,

Anatoli
Anatoli
2006-08-17 02:42:01 UTC
Permalink
All the below is happening while I'm attempting to connect remotely from my
XP SP2 pc using SSMS.

Further to this, I've found that I can connect to the server in question
remotely using the SA account. I can also, connect to SQL2005 locally with my
network account from within an RDP session.
Post by Anatoli
Hi,
Im having trouble connecting to the SQL2005 default instance installed on
one of my sql servers within my domain. I have a second SQL2005 server that I
can connect to just fine. Both are in the same OU.
This particular server, I can connect to AS2005, but not to SQL2005. I keep
getting the 'Cannot generate SSPI context. (.Net SqlClient Data Provider)'
error. I've not changed anything in terms of settings on my PC, nor have any
settings been changed on the SQL server, though I was able to connect to
SQL2005 for this server last week. Something obviously has changed, but I
have no idea where to look. One of the other SysAdmins has no problems
connecting to the database.
I'm hoping this is just something simple to fix.
regards,
Anatoli
MarkusB
2006-08-17 11:05:05 UTC
Permalink
Anatoli,

check these links.
http://support.microsoft.com/kb/811889/

http://msdn2.microsoft.com/en-us/library/ms191153.aspx
http://msdn2.microsoft.com/en-us/library/ms189585.aspx

Hope this helps

Markus
Anatoli
2006-08-17 18:32:32 UTC
Permalink
Markus,

Thanks for your reply. From what I can tell, this problem is specific to my
domain account. That is that I can connect remotely to the SQL server using
the SA account, but I can't connect using my domain account. I tried using
another PC from which one of other admins was able to easily connect to
SQL2005. I don't use a roaming profile, and this was the first time I logged
onto that PC and still I got the same error. Again, when I logged in locally
to the SQL server I didn't have any problems SSMS connecting.

So from what I can tell, there aren't any setting issues on the SQL server
side nor are there any issues from my PC side as I'm able to connect to other
instances of SQL 2005 with my domain account.

Are there any settings associated with the login to cause such an error?
Post by MarkusB
Anatoli,
check these links.
http://support.microsoft.com/kb/811889/
http://msdn2.microsoft.com/en-us/library/ms191153.aspx
http://msdn2.microsoft.com/en-us/library/ms189585.aspx
Hope this helps
Markus
Anatoli
2006-08-18 07:44:02 UTC
Permalink
Turned out to be how the system guys upgraded the server to W2K3, SQL and AS
2005. They blew away the old sql server and installed W2K3, SQL/AS 2005, but
never removed the computer object out of AD. Used the SETSPN.exe utility
determine that there was more than one SPN for that particular server.

regards,
Post by Anatoli
Markus,
Thanks for your reply. From what I can tell, this problem is specific to my
domain account. That is that I can connect remotely to the SQL server using
the SA account, but I can't connect using my domain account. I tried using
another PC from which one of other admins was able to easily connect to
SQL2005. I don't use a roaming profile, and this was the first time I logged
onto that PC and still I got the same error. Again, when I logged in locally
to the SQL server I didn't have any problems SSMS connecting.
So from what I can tell, there aren't any setting issues on the SQL server
side nor are there any issues from my PC side as I'm able to connect to other
instances of SQL 2005 with my domain account.
Are there any settings associated with the login to cause such an error?
Post by MarkusB
Anatoli,
check these links.
http://support.microsoft.com/kb/811889/
http://msdn2.microsoft.com/en-us/library/ms191153.aspx
http://msdn2.microsoft.com/en-us/library/ms189585.aspx
Hope this helps
Markus
Loading...