Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
TroggleDorf
Starting Member
2 Posts |
 Posted - 2011-04-26 : 13:18:09
|
| I am running into a problem that maybe some of you guys can help me with. I have a server running SQL 2005, let's call it My2005Server. I am trying to connect to server running SQL 2000, My2000Server, through the SQL Server Management Studio. I am attempting to connect by server name and using Windows Authentication. Unfortunately I am getting the dreaded "Cannot Generate SSPI Context" error message.Further research revealed the following:My2000Server is running Windows 2003 Server as it's OS. It has 2 network adapters, and each adapter has two IP addresses. For example purposes:Adapter 1123.123.123.1123.123.123.2Adapter 2123.123.123.3123.123.123.4Now get this--if I go into My2005Server's SQL Management Studio and attempt to connect to My2000Server by IP address, if I use 123.123.123.1 or 123.123.123.3 with Windows Authentication, I get the "Cannot Generate SSPI Context" error.If I use 123.123.123.2 or 123.123.123.4 with Windows Authentication, I connect with no problems.I *think* all of the DNS settings are correct. If I ping -a My2000Server, it resolves to the FQDN My2000Server.Mydoman.com.Also, when I ping My2000Server, half the time it resolves to 123.123.123.1, and half the time it resolves to 123.123.123.3.So I then checked the ErrorLog on My2000Server to see what IPs the server is listening for, and I found the following entries:2011-03-08 21:20:41.79 server SQL server listening on 123.123.123.1: 1433.2011-03-08 21:20:41.79 server SQL server listening on 123.123.123.2: 1433.2011-03-08 21:20:41.79 server SQL server listening on 123.123.123.3: 1433.2011-03-08 21:20:41.79 server SQL server listening on 123.123.123.4: 1433.2011-03-08 21:20:41.81 server SQL server listening on 127.0.0.1: 1433.I have absolutely no idea what to try next. Does anyone have any suggestions? Ultimately I want to be able to connect to My2000Server from My2005Server by server name using Windows Authentication.Thanks! |
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2011-04-26 : 13:21:53
|
| Did you recently change your Windows password? If so, log off the domain and log on again. If you're connected to any machines via Remote Desktop or Terminal Services, log off of those as well.SSPI context errors are not affected by the network hardware or IP address of the server. |
 |
|
|
TroggleDorf
Starting Member
2 Posts |
Posted - 2011-04-26 : 13:25:51
|
quote:
Originally posted by robvolk
Did you recently change your Windows password? If so, log off the domain and log on again. If you're connected to any machines via Remote Desktop or Terminal Services, log off of those as well.SSPI context errors are not affected by the network hardware or IP address of the server.
Hi!I have logged off and on lots of many times, but still get the error. This error actually has been happening for quite some time. I have always gotten around it by using a SQL account to connect to the SQL 2000 server, but now some of my developers want to use Integrated Security in their apps, so this is not an option. |
|
|
|
jeffw8713
Aged Yak Warrior
819 Posts |
Posted - 2011-04-26 : 16:13:48
|
| Sounds like you might have an invalid SPN defined for the 2000 system. Using the SetSPN.exe utility to find the SPN records associated with that server and/or the service account.Jeff |
|
|
|
|
|
|
|
|
Cannot Generate SSPI Context