Windows authentication without a domain?

[martynh]

Probably a simple question....

Suppose a situation where there are just two machines in a workgroup (no Domain controller). One machine runs an application, the other SQL Server 2000. Both machines are running XP. Is it possible for the application on the app server to connect to SQL Server using Windows Authentication where the application uses a different Windows user id to the one that it is running under?

This is a trivial thing for a database running on Linux/Unix since you simply create the necessary database users as Linux/Unix users and pass the user id and password in the connection parameters.

Regards

Martyn

 

[SQLBill]

Nope.

First, Windows Authentication is just that...it uses the login/password that you use to log into Windows. So the login/password for an application wouldn't work (it's an Application login not a Windows login).

Second, for Windows Authentication to work you need a 'trusted' connection. That means both machines have to authenticate the user by way of a 'trusted' authentication method (Domain Controller). Without a domain, you are using LOCAL logins that are only authenticated on their own machine. When you log onto your user machine, that computer has no way to pass the authentication to the SQL Server computer.

-SQLBill