 | |
Unable to Generate SSPI Context w/ .Net 2.0 App and Windows 2000Professional Client
microsoft.public.sqlserver.connect microsoft.public.sqlserver.connect
 |
| | Thread Tools | Display Modes |
#21
 
| |||
| |||
|
Re: Unable to Generate SSPI Context w/ .Net 2.0 App and Windows 2000Professional Client -
07-05-2008
, 10:50 AM
|
On Jun 6, 12:06 pm, "William Vaughn [MVP]" <billvaNoS... (AT) betav (DOT) com wrote: 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.ch... (AT) gmail (DOT) com> wrote in message news:cd7be41c-6b53-4ff3-99cf-d7832fe20fb3 (AT) e53g2000hsa (DOT) googlegroups.com.... 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 onthe 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 These PC's are in the same domain, but it only works with a SQL account. *I'm not for sure setup IMHO, just that other machines basically right next to it works fine with intregrated security, but the Windows 2000 machine won't work. Thanks. |
We recently upgraded our SQL server to Windows 2003, SQL server still
stayed as 2000, but now the Windows 2000 Professional PC can connect
using Windows Authentication.
Thanks
#22
| |||
| |||
|
|
On Jun 6, 12:06 pm, "William Vaughn [MVP]" <billvaNoS... (AT) betav (DOT) com wrote: 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.ch... (AT) gmail (DOT) com> wrote in message news:cd7be41c-6b53-4ff3-99cf-d7832fe20fb3 (AT) e53g2000hsa (DOT) googlegroups.com.... 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 onthe 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 These PC's are in the same domain, but it only works with a SQL account. *I'm not for sure setup IMHO, just that other machines basically right next to it works fine with intregrated security, but the Windows 2000 machine won't work. Thanks. |
We recently upgraded our SQL server to Windows 2003, SQL server still
stayed as 2000, but now the Windows 2000 Professional PC can connect
using Windows Authentication.
Thanks
#23
| |||
| |||
|
|
On Jun 6, 12:06 pm, "William Vaughn [MVP]" <billvaNoS... (AT) betav (DOT) com wrote: 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.ch... (AT) gmail (DOT) com> wrote in message news:cd7be41c-6b53-4ff3-99cf-d7832fe20fb3 (AT) e53g2000hsa (DOT) googlegroups.com.... 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 onthe 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 These PC's are in the same domain, but it only works with a SQL account. *I'm not for sure setup IMHO, just that other machines basically right next to it works fine with intregrated security, but the Windows 2000 machine won't work. Thanks. |
We recently upgraded our SQL server to Windows 2003, SQL server still
stayed as 2000, but now the Windows 2000 Professional PC can connect
using Windows Authentication.
Thanks
#24
| |||
| |||
|
|
On Jun 6, 12:06 pm, "William Vaughn [MVP]" <billvaNoS... (AT) betav (DOT) com wrote: 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.ch... (AT) gmail (DOT) com> wrote in message news:cd7be41c-6b53-4ff3-99cf-d7832fe20fb3 (AT) e53g2000hsa (DOT) googlegroups.com.... 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 onthe 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 These PC's are in the same domain, but it only works with a SQL account. *I'm not for sure setup IMHO, just that other machines basically right next to it works fine with intregrated security, but the Windows 2000 machine won't work. Thanks. |
We recently upgraded our SQL server to Windows 2003, SQL server still
stayed as 2000, but now the Windows 2000 Professional PC can connect
using Windows Authentication.
Thanks
#25
| |||
| |||
|
|
On Jun 6, 12:06 pm, "William Vaughn [MVP]" <billvaNoS... (AT) betav (DOT) com wrote: 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.ch... (AT) gmail (DOT) com> wrote in message news:cd7be41c-6b53-4ff3-99cf-d7832fe20fb3 (AT) e53g2000hsa (DOT) googlegroups.com.... 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 onthe 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 These PC's are in the same domain, but it only works with a SQL account. *I'm not for sure setup IMHO, just that other machines basically right next to it works fine with intregrated security, but the Windows 2000 machine won't work. Thanks. |
We recently upgraded our SQL server to Windows 2003, SQL server still
stayed as 2000, but now the Windows 2000 Professional PC can connect
using Windows Authentication.
Thanks
#26
| |||
| |||
|
|
On Jun 6, 12:06 pm, "William Vaughn [MVP]" <billvaNoS... (AT) betav (DOT) com wrote: 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.ch... (AT) gmail (DOT) com> wrote in message news:cd7be41c-6b53-4ff3-99cf-d7832fe20fb3 (AT) e53g2000hsa (DOT) googlegroups.com.... 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 onthe 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 These PC's are in the same domain, but it only works with a SQL account. *I'm not for sure setup IMHO, just that other machines basically right next to it works fine with intregrated security, but the Windows 2000 machine won't work. Thanks. |
We recently upgraded our SQL server to Windows 2003, SQL server still
stayed as 2000, but now the Windows 2000 Professional PC can connect
using Windows Authentication.
Thanks
#27
| |||
| |||
|
|
On Jun 6, 12:06 pm, "William Vaughn [MVP]" <billvaNoS... (AT) betav (DOT) com wrote: 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.ch... (AT) gmail (DOT) com> wrote in message news:cd7be41c-6b53-4ff3-99cf-d7832fe20fb3 (AT) e53g2000hsa (DOT) googlegroups.com.... 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 onthe 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 These PC's are in the same domain, but it only works with a SQL account. *I'm not for sure setup IMHO, just that other machines basically right next to it works fine with intregrated security, but the Windows 2000 machine won't work. Thanks. |
We recently upgraded our SQL server to Windows 2003, SQL server still
stayed as 2000, but now the Windows 2000 Professional PC can connect
using Windows Authentication.
Thanks
#28
| |||
| |||
|
|
On Jun 6, 12:06 pm, "William Vaughn [MVP]" <billvaNoS... (AT) betav (DOT) com wrote: 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.ch... (AT) gmail (DOT) com> wrote in message news:cd7be41c-6b53-4ff3-99cf-d7832fe20fb3 (AT) e53g2000hsa (DOT) googlegroups.com.... 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 onthe 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 These PC's are in the same domain, but it only works with a SQL account. *I'm not for sure setup IMHO, just that other machines basically right next to it works fine with intregrated security, but the Windows 2000 machine won't work. Thanks. |
We recently upgraded our SQL server to Windows 2003, SQL server still
stayed as 2000, but now the Windows 2000 Professional PC can connect
using Windows Authentication.
Thanks
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.