Cannot Generate SSPI context
Posted on 2004-08-26
I'm sure this question comes up here alot, and I searched the solutions but I don't subscribe so I couldn't see the ones that are already there. If this is a repeat question hopefully it will be an easy 500 points for somebody.
As the title states, I am getting the "Cannot Generate SSPI context" errors when I try to connect to a remote SQL Server DB.
I'll start by saying that I have read the MS KB articles, particularly "How to troubleshoot the SSPI context error". I've tried most of the stuff that I understand and think is relevant in that article, so I'm looking for a little more hand-holding here to get this solved and award the 500 points.
I'm running WinXP Pro w/ SQL Server 2000 SP 3a.
My computer is a member of DomainA, and the SQL Server I'm trying to connect to is a member of DomainB. I connect to DomainB using a VPN with windows authentication.
The really frustrating part of all of this is that two weeks ago, I had no problems connecting, then suddenly I started having this problem. I did a system restore to a point where I was able to make the connection without the sspi error, but that buggered up some other stuff I was working on that was creating bigger headaches than the SSPI problem, so I undid the restore, and the sspi problem is back. The only software that I installed in the meantime is from the WindowsUpdate site. No games or apps or anything else, that I can think of.
When I am connected to DomainB via VPN, I can ping the server (call it SQLTarget) by both name and IP address. If I do "ping SQLTarget /a" it resolves to the fully realized name and domain of the SQL Target machine.
I've tried uninstalling and reinstalling SQL2K a number of times, but no luck. The TargetSQL machine is running Win2K Server.
I can provide more info if you have questions, and I'm willing to try things I've already tried again if you suggest that I should, but like I've said I've read the knowledge base articles, and I'm either too dumb to follow the instructions there (there's a good chance this is the case) or I'm having a slightly different problem.
Thanks for your help,