Hi,

We have a server in a workgroup that users in our active directory
will need to access.


How can we configure an odbc connection to use a different username
and password (windows not sql) than the one they are currently logged
on on as. (The application we are using only supports windows
authentication not sql)


example : I am logged onto my workstaion a 'Jane', but i Need to use
user id 'janey' to connect to the odbc, and i dont want to have to
log
on to the workstation as janey

On Mar 24, 12:05 pm, zach <neopot...@gmail.com> wrote:
> Hi,
>
> We have a server in a workgroup that users in our active directory
> will need to access.
>
> How can we configure an odbc connection to use a different username
> and password (windows not sql) than the one they are currently logged
> on on as. (The application we are using only supports windows
> authentication not sql)
>
> example : I am logged onto my workstaion a 'Jane', but i Need to use
> user id 'janey' to connect to the odbc, and i dont want to have to
> log
> on to the workstation as janey

Hi, i'm no network admin, but from my experience usually what they do
is create a windows group and assign all the users they want to have
access to that odbc to that group, then you have your dba create a sql
account with that group having minimal permissions needed and set up
the odbc with the group name.

zach (neopotent@gmail.com) writes:
> We have a server in a workgroup that users in our active directory
> will need to access.
>
>
> How can we configure an odbc connection to use a different username
> and password (windows not sql) than the one they are currently logged
> on on as. (The application we are using only supports windows
> authentication not sql)
>
>
> example : I am logged onto my workstaion a 'Jane', but i Need to use
> user id 'janey' to connect to the odbc, and i dont want to have to log
> on to the workstation as janey

You cannot specify a different Windows login when you login with
Windows authentication. The whole point with Windows authentication,
is that you Windows authenticated you to log in. So there is no workaroun,
you must log into Windows as janey. Now, there are probably more than one
way to do this than just logging off and on your workstation. Virtual
machines and remote desktop are two options that comes to mind. There
are probably programs out there that can perform a log-in into Windows
to run another program.

But you will have to ask in Windows forum about that. All I can say that
from the SQL Server side, is that SQL Server does not offer any alternatives
here. You must be logged in as janey.

--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx