cell0042
asked on
Cannot Generate SSPI Context
After installing XP Pro on a couple a machines, I ran into a problem with our users losing connectivity to the SQL Database. All of the Win 2kpro machines work.
I get this @ home also I'll add a further 100 pts to this for the fix. Also with XP Pro.
Can you still connect using SQL Authentication? I thik this is a permissions problem. We had it several years ago...
Paul
Paul
I cant, not sure about cell.
can connect locally though. Cell have you tried connecting locally with trusted connection and/or SQL authentication?
When do you get this message? We used to get it when replicating between two machines. One of the services was using a local account and not a domain (if I remember correctly).
Paul
Paul
I am assuming here that Cell's problem it the same as mine. If not then please stop me cell as I dont want to Hijack your question, I will open a seperate one if it is different. I get it all the time trying to open a connection (EM / QA / ODBC / etc. ). I have 2 machines one is a DC with SQL Server the other is a client with tools. definately on same domain and logged in on a domain account. same domain account is fine using client tools @ the server.
I assume you've looked at the Microsoft KB site and gone thru all these steps?
http://support.microsoft.com/default.aspx?kbid=811889
http://support.microsoft.com/default.aspx?kbid=811889
I've had this happen before and it's usually because the default protocol on the client doesn't support windows authentication...
cell.... are you still participating in this? we havent heard from you since you posted. I am concerned that I dont want to divert the discussion from your problem. If this is the case and my senario is different I will open a new discussion rather than top up your points.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
All. I will try the soggestions on my kit @ home and if one of these solved my problem, Ill give my 100. if not I'll start a further thread now cell has accepted an answer.
Probably a bit late for cell0042, but in the interests of contributing;
I had this error after I changed my password on the DC, while leaving my workstation logged on. Since it would've been disruptive to re-logon I connected with sql authentication and was fine. I didn't try changing the pwd back, but once I did log on to the domain again everything was back to normal.
I had this error after I changed my password on the DC, while leaving my workstation logged on. Since it would've been disruptive to re-logon I connected with sql authentication and was fine. I didn't try changing the pwd back, but once I did log on to the domain again everything was back to normal.
Actually SQL Server has a bug. It seems to happen on 6.5 and 2000. If this error happens, all you need to do is remap the server.
To do so open your ODBC connection manager in the control panel.
Create a new or if you have an existing connectoin to the DB with problems.
When you get the screen that has the <Client Configuration> button, click it.
Here is the trick. In the <Network Libraries>, If <TCP/IP> is checked then check <Named Pipes>.
If <Named Piped> is checked then check <TCP/IP>.
Select ok and it should be fixed.
I've been dealing with this bug for 3 years now and this always fixes it.
To do so open your ODBC connection manager in the control panel.
Create a new or if you have an existing connectoin to the DB with problems.
When you get the screen that has the <Client Configuration> button, click it.
Here is the trick. In the <Network Libraries>, If <TCP/IP> is checked then check <Named Pipes>.
If <Named Piped> is checked then check <TCP/IP>.
Select ok and it should be fixed.
I've been dealing with this bug for 3 years now and this always fixes it.
I know that I was hoping to avoid using Named Pipes. I tried tieman123's fix almost completely and this just ended months of frustration for me. I created a DSN, selected Named Pipes in the Client Configuration screen, BUT I DID NOT SAVE THE DSN. I then re-registered my server through Enterprise Manager and it worked fine. I am so happy now. Hooray.
/Atropa
/Atropa
I encountered such a problem and I managed to solve it according to my case. It is related to the network configuration.
I reconfigured my TCP/IP settings by assigning the IP address of the domain controler to both the DSN server and Default Gateway.
I reconfigured my TCP/IP settings by assigning the IP address of the domain controler to both the DSN server and Default Gateway.
" reconfigured my TCP/IP settings by assigning the IP address of the domain controler to both the DSN server and Default Gateway."
Most people don't have the option of doing that....
Most people don't have the option of doing that....
Reconfigured the settings on which box? SQL? /Atropa
This is something that can come up in a Kerberos authentication network. In my recent case, DNS is not properly configured to give the fully qualified name in response to a ping -a. Without that, Kerberos gets really freaked out and kills the connection.
Handy little document from MS:
http://support.microsoft.com/default.aspx?scid=kb;en-us;811889
Kevin3NF
Handy little document from MS:
http://support.microsoft.com/default.aspx?scid=kb;en-us;811889
Kevin3NF
Why do people keep commenting on closed questions????
I found this question while searching for something else, and figured my input would help the next person that found it. Are you bothered by it for a particular reason? Its not all about the points...