SQL : [Microsoft][ODBC Driver SQL]Cannot generate SSPI context

Hi,

I have an SQL error(Cannot generate SSPI Contect) but only on one machine on that customer's site. Every PC have the same OS (Windows XP Pro SP2). The SQL Server is install on Windows Server 2003. The user his able to connect on the database but after a while ... he got this message. Never at the same moment in the application and naver after the same amout of time .....

I checked and test some of the explication that I found on this site... but nothing work...

Thanks in advance for your help !!!!
novologikAsked:
Who is Participating?
 
Chris MangusConnect With a Mentor Database AdministratorCommented:
Yes, that should work, but, you don't need to delete TCP/IP in the CNU on the server.
0
 
digital_thoughtsCommented:
One possibility in the network connection for that machine... have you tried a different network card and/or network connection?
0
 
and235100Commented:
General troubleshooting:
http://support.microsoft.com/kb/811889
0
Hire Technology Freelancers with Gigs

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

 
Chris MangusDatabase AdministratorCommented:
Check the time on the users machine.  If it's way off it will generate this error.

Alternatively, you can set up an alias to the server for that user and force the named pipes protocol as it will avoid the SSPI issue.
0
 
novologikAuthor Commented:

Yes I tried with another network connection and same thing. They use other network software without SQL and everything work good. It's the reason why I'm sure that the network card is working correctly.
I also tried to do some change in my ODBC driver like what is written at http://support.microsoft.com/kb/811889 and nothing change ... I also checked for the specific Key in the registry ... everything is correct. This article is more for windows 2000 and my SQL is running on Windows 2003.

0
 
novologikAuthor Commented:

Hi cmangus,

I tried to set up an alias to the server for that user and force the named pipes protocol and nothing change......I just checked, and the clock is the same on the PC and the server (The login script set the clock on each machine at logon)
0
 
and235100Commented:
What SP is your SQL server?
0
 
Chris MangusDatabase AdministratorCommented:
Named pipes bypasses SSPI altogether.  I'm surprised that didn't help.  Did you set that up in the ODBC administrator or in the Client Network Utility?
0
 
novologikAuthor Commented:

I setup that in the Client Configuration of the Client ODBC Driver.

SP1
0
 
Chris MangusDatabase AdministratorCommented:
Use the SQL Server Client Network Utility.
0
 
novologikAuthor Commented:
How can I access it?
0
 
Chris MangusDatabase AdministratorCommented:
Start > Program Files > Microsoft SQL Server > Client Network Utility
0
 
novologikAuthor Commented:

This is what I already have in Client Network Utility ....(See attach file).... Named pipes (Canaux nommés) is already there ....
Pic1.bmp
0
 
Anthony PerkinsCommented:
Did you notice which protocol was first?  For the workaround to work it should be Named Pipes before TCP/IP.  Or better still remove TCP/IP.
0
 
Jerryuk007Commented:
** FIRST
-- Check that that machine is on the same Network (Domain/WorkGroup) that the other machines and of the Database Server.

-- When logging into windows, didn't you get an error message like "Duplicate Name or IP Address" ?

** Then, if nothing there...
- In Query Analyser, run
Select * from sysprocesses
 and check the connection when this machine has a database connection open (especially the field "net_library").

- Check the Network Protocols for SQL on the database Server and make sure TCP-IP is present.

Hope this helps.

Jerry
0
 
novologikAuthor Commented:
acperkins
I changed that yesterday, I put Named Pipes first .... but I still have the error.... If I remove TCP/IP, this will not affect the other PC connection with the Server?

Jerryuk007
The machine is on the same domaine .... No error at loggon.... The only diffirence between this PC and the others, this one have a fix IP addresss .....(For Remote connection).... TCP-IP is present in Network Protocols for SQL .... I checked in Query Analyser, I have a lot of sys... table but not sysprocesses...

Thanks guys for your help !!!!
0
 
Chris MangusDatabase AdministratorCommented:
Indeed, remove TCP/IP.  Add an Alias to the server with the Client Network Utility and force Named Pipes as the protocol.
0
 
novologikAuthor Commented:
cmangus
I remove TCP/IP (Pic2) and I create an alias (Pic3) ....I'll check if that fix the problem and I'll give back to you today .....

Thanks....
Pic2.bmp
Pic3.bmp
0
 
novologikAuthor Commented:
Did I need to change something on the client PC?
0
 
Chris MangusDatabase AdministratorCommented:
This alias needs to be set up on the client PC, not on the server.
0
 
Anthony PerkinsCommented:
>>Did I need to change something on the client PC?<<
Perhaps that is the problem all along: You have been making these changes on the server which will have no effect on the client PC.
0
 
novologikAuthor Commented:
I remove TCP/IP on the Client Network Utility (Server) and when I try to configure the Client PC in the ODBC Driver..... I put Named Pipes ....Now I have an error to connect on the SQL server....
0
 
novologikAuthor Commented:
Sorry ....My error .....it's good on the client PC.....

Resume:
I delete TCP/IP in Client Network Utility on the server and I create an alias on the client PC and I force to use named pipes ....Everything is correct? It's what you whant me to do?
0
All Courses

From novice to tech pro — start learning today.