Re: Unable to Generate SSPI Context w/ .Net 2.0 App and Windows 2000 Professional Client
- From: "William Vaughn [MVP]" <billvaNoSPAM@xxxxxxxxx>
- Date: Fri, 6 Jun 2008 09:06:30 -0700
We see this all the time when we do off-domain demos in the field. The best solution (IMHO), is to not use SSPI, but a work-around is to log into the local machine (not the domain) and let the local system authenticate the user.
--
__________________________________________________________________________
William R. Vaughn
President and Founder Beta V Corporation
Author, Mentor, Dad, Grandpa
Microsoft MVP
(425) 556-9205 (Pacific time)
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
____________________________________________________________________________________________
"GSC" <greg.cheek@xxxxxxxxx> wrote in message news:cd7be41c-6b53-4ff3-99cf-d7832fe20fb3@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I have a C# .Net App using Windows trusted security connecting to a
Sql server 2000 (running on a Windows 2000 Server). If I change the
connection parameters to use a SQL Account it works fine, but when I
change it to use NT Security, it fails with Unable to Generate SSPI
Context. The same app works fine on XP Professional machines on the
same network. Also, I have many Delphi applications running on the
same machine using Windows Authentication that work fine; but they are
not .Net apps, just standard Win32 applications.
Any help or suggestions would be greatly appreciated.
Thanks
.
- Follow-Ups:
- References:
- Prev by Date: Re: How do I use sp_configure 'user instances enabled'
- Next by Date: Win2K workstation ODBC cannot find new SQL Server
- Previous by thread: Unable to Generate SSPI Context w/ .Net 2.0 App and Windows 2000 Professional Client
- Next by thread: Re: Unable to Generate SSPI Context w/ .Net 2.0 App and Windows 2000 Professional Client
- Index(es):
Relevant Pages
|