March 31, 2008 at 10:49 am
I have a new installation of SQLServer 2005 Express. During install I selected both Windows NT id and SQL Server id login and set the password of the sa account.
After installation I enabled remote connections for TCP/IP only using the Surface Area Configuration tool.
Then I tested the MS OLEDB for SQL Server Provider using Windows NT Integraged security to connect to the master database and I get this error:
"Test connection failed because of an error in initializing provider. Cannot generate SSPI Context."
When I try the same provider and database with the sa account and password the connection succeeds.
I have a application that connects to SQLServer via the Windows NT id so I need this to work.
Any ideas on why this does not work?
One other thing, this is a corporate laptop and there are some security policies set on it. I didn't see any that appeared to be an obvious problem. But if anyone knows of a specific problem that will cause issues with SQL Server please let me know.
Thanks,
Dave
April 1, 2008 at 8:13 am
Hi,
In DSN at the server text column type servername in FQDN format or use IP address as shown below and configure the correct port number.
Ex.)
server.mshome.net
or
10.125.85.3
Regards..Vidhya Sagar
SQL-Articles
April 1, 2008 at 9:16 am
SSPI is a security error with Windows Auth. It can be a number of things. Try these links:
support.microsoft.com/kb/811889
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply