December 9, 2007 at 9:05 pm
Hi -
We have some SQL 2005 Servers (Server1 , Server2 , Server 3) . From Server3 SQLMgmt Studio ,I am able to connect to the Server 2 and Server1. But the other way round either server 1 or server 2 are not able to connect Server 3 with their Mgmt Studios. I get an error .."Cannot connect to server3 .Cannot generate SSPI Context".. I am also getting the same error while using queryanalyser to connect to server3 from other servers.
i have created a ODBC connectivity on server 1 and server 2 for server 3 . But still the error was there. Then when i changed in the Client configuration from TCP to Named Pipes in the ODBC Connectivity , I am able to connect without any error.
I dont think its a solution for this problem as i dont want to use ODBC connectivity on all servers and secondly I assume that even applications may face issues as TCP is the standard and not named pipes. DOes anybody have a solution for this Problem?
Thanks In Advance.
Murali
December 9, 2007 at 9:08 pm
It's a security issue with the accounts on Server 3. It could be your SPN isn't correct on that server or there's a timing issue (kerberos is used).
December 10, 2007 at 2:35 am
This is due to Kerberos authentication failure, Please go through the links it might help you 🙂
http://blogs.msdn.com/sql_protocols/archive/2005/10/15/481297.aspx
http://blogs.msdn.com/sql_protocols/archive/2005/10/19/482782.aspx
The major reason is due to the Credential Cache( is used by Kerberos to store authentication information, namely the TGT and session ticked is cached so that can be used during their lifetime.)
The most general workaround is: clean up credential cache by using "klist.exe -purge" or kerbtray.exe or just reboot machine.
See more detail about various cause and solution in http://support.microsoft.com/kb/811889.
"More Green More Oxygen !! Plant a tree today"
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply