Domain and windows authentication

Hi,
We have a application that uses windows authentication to connect to sql
server. We have a domain and simply just create a login in sql server for
each user in the domain.
We have setup this application in the company that doesn't have domain.
We're not going to change the source of the application to accept sql server
authentication.
Can we still use the windows authentication to allow the users to log in?
Suppose that each user logs in his computer as administrator of that
computer. Can we prefix these administrators with the name of their
computers to create login in sql server and still use windows
authentication?
Any help would be greatly appreciated.
Amin
Microsoft SQL Server support only Domain Authentification, no Machine
Account Authentification (except the local machine of the sql server),
because Workgroups are not trustable.
Hope this helps,
Jens Smeyer
"Amin Sobati" <amins@.morva.net> schrieb im Newsbeitrag
news:%23ahXq45gEHA.1764@.TK2MSFTNGP10.phx.gbl...
> Hi,
> We have a application that uses windows authentication to connect to sql
> server. We have a domain and simply just create a login in sql server for
> each user in the domain.
> We have setup this application in the company that doesn't have domain.
> We're not going to change the source of the application to accept sql
server
> authentication.
> Can we still use the windows authentication to allow the users to log in?
> Suppose that each user logs in his computer as administrator of that
> computer. Can we prefix these administrators with the name of their
> computers to create login in sql server and still use windows
> authentication?
> Any help would be greatly appreciated.
> Amin
>
|||Jens,
Therefore in workgroups there's no other solution except using sql server
authentication?
"Jens Smeyer" <MrIgel[RejectSpam|RemoveBracket]@.gmx.de> wrote in message
news:OCvmQg7gEHA.2764@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> Microsoft SQL Server support only Domain Authentification, no Machine
> Account Authentification (except the local machine of the sql server),
> because Workgroups are not trustable.
> Hope this helps,
> Jens Smeyer
>
> "Amin Sobati" <amins@.morva.net> schrieb im Newsbeitrag
> news:%23ahXq45gEHA.1764@.TK2MSFTNGP10.phx.gbl...
for[vbcol=seagreen]
> server
in?
>
|||You should be able to use NT authentication by doing the following:
1. Create a local account on the SQL Server machine that matches each
individual users local machine account. Make sure the password is the same
for both accounts.
2. Create a login within SQL Server for each of these logins.
3. NT authentication should now work.
This could be difficult to administer becaues each time a user changes his
local opassword the pasword has to be changed at the SQL Server machine as
well.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||Rand,
What if users log into their computer with administrator account?
Necessarily they must use different user names?
Amin
"Rand Boyd [MSFT]" <rboyd@.onlinemicrosoft.com> wrote in message
news:Qxq9sH9gEHA.3340@.cpmsftngxa06.phx.gbl...
> You should be able to use NT authentication by doing the following:
> 1. Create a local account on the SQL Server machine that matches each
> individual users local machine account. Make sure the password is the same
> for both accounts.
> 2. Create a login within SQL Server for each of these logins.
> 3. NT authentication should now work.
> This could be difficult to administer becaues each time a user changes his
> local opassword the pasword has to be changed at the SQL Server machine as
> well.
> Rand
>
> This posting is provided "as is" with no warranties and confers no rights.
>