Hi all. We have several consultants on site that need access to our SQL
server databases. They have accounts in our domain and I would like to use
those accounts in SQL 2005 (actually, as part of a Development group).
Since their machines are not part of our Domain, they cannot use Windows
Authentication to connect. How can I use SQL Server Authentication and
their Domain accounts to allow them to connect to the server?
I have tried using the accounts as Domain\Username in the Login box, but I
always get 'Microsoft SQL Server, Error: 18456' (I can use other non-Domain
accounts to login successfully, so I know the conenctivity is OK).
Any help would be appreciated.
--
Thanks,
TheBurgerMan
at
gmail.com
--TheBurgerMan wrote:
> Hi all. We have several consultants on site that need access to our SQL
> server databases. They have accounts in our domain and I would like to use
> those accounts in SQL 2005 (actually, as part of a Development group).
> Since their machines are not part of our Domain, they cannot use Windows
> Authentication to connect. How can I use SQL Server Authentication and
> their Domain accounts to allow them to connect to the server?
> I have tried using the accounts as Domain\Username in the Login box, but I
> always get 'Microsoft SQL Server, Error: 18456' (I can use other non-Domain
> accounts to login successfully, so I know the conenctivity is OK).
> Any help would be appreciated.
>
When you've tried setting these accounts up as Domain\Username, are you
using your domain name, or theirs? Is your server a member of your domain?|||The Consultant machines are not members of my Domain, but they are using
Domain accounts that I have created. When I created the Consultant
accounts, I added them to the Development Group which has profecient rights
in SQL server to log in and manipulate databases (my account is a member of
this group).
I tried the same test on my laptop! I can login with SQL Server Auth into
an account that I created on the server AND I can login with Windows
Authentication (because my machine is a member of the Domain), but I cannot
login with SQL Server Auth with my Domain account! This is what I want to
do (then I do not have to start creating a pile of seperate accounts in SQL
server as well as AD).
--
Thanks,
TheBurgerMan
at
gmail.com
--
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:OyS%23heUmGHA.5076@.TK2MSFTNGP02.phx.gbl...
> TheBurgerMan wrote:
>> Hi all. We have several consultants on site that need access to our SQL
>> server databases. They have accounts in our domain and I would like to
>> use those accounts in SQL 2005 (actually, as part of a Development
>> group).
>> Since their machines are not part of our Domain, they cannot use Windows
>> Authentication to connect. How can I use SQL Server Authentication and
>> their Domain accounts to allow them to connect to the server?
>> I have tried using the accounts as Domain\Username in the Login box, but
>> I always get 'Microsoft SQL Server, Error: 18456' (I can use other
>> non-Domain accounts to login successfully, so I know the conenctivity is
>> OK).
>> Any help would be appreciated.
> When you've tried setting these accounts up as Domain\Username, are you
> using your domain name, or theirs? Is your server a member of your
> domain?|||You can't do a SQL Server login using a domain account. SQL Server will look for a SQL Server login
with the name of Domain\User, and pass the password you enter. The app need to ask for a Windows
login, and the credentials will be taken from the account system that validated that Windows account
(the local machine, for example).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"TheBurgerMan" <TheBurgerMan@.gmail.com> wrote in message
news:umAcwjUmGHA.1896@.TK2MSFTNGP05.phx.gbl...
> The Consultant machines are not members of my Domain, but they are using Domain accounts that I
> have created. When I created the Consultant accounts, I added them to the Development Group which
> has profecient rights in SQL server to log in and manipulate databases (my account is a member of
> this group).
> I tried the same test on my laptop! I can login with SQL Server Auth into an account that I
> created on the server AND I can login with Windows Authentication (because my machine is a member
> of the Domain), but I cannot login with SQL Server Auth with my Domain account! This is what I
> want to do (then I do not have to start creating a pile of seperate accounts in SQL server as well
> as AD).
> --
> Thanks,
> TheBurgerMan
> at
> gmail.com
> --
> "Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
> news:OyS%23heUmGHA.5076@.TK2MSFTNGP02.phx.gbl...
>> TheBurgerMan wrote:
>> Hi all. We have several consultants on site that need access to our SQL server databases. They
>> have accounts in our domain and I would like to use those accounts in SQL 2005 (actually, as
>> part of a Development group).
>> Since their machines are not part of our Domain, they cannot use Windows Authentication to
>> connect. How can I use SQL Server Authentication and their Domain accounts to allow them to
>> connect to the server?
>> I have tried using the accounts as Domain\Username in the Login box, but I always get 'Microsoft
>> SQL Server, Error: 18456' (I can use other non-Domain accounts to login successfully, so I know
>> the conenctivity is OK).
>> Any help would be appreciated.
>>
>> When you've tried setting these accounts up as Domain\Username, are you using your domain name,
>> or theirs? Is your server a member of your domain?
>|||That seems counter-intuitive given that I can use Domain resources,
authenticating with a Domain username and password, but never be a member of
said Domain!
I only want to use this feature in the SQL Server Management GUI. Is there
a way to pass the Domain credentials using the Windows login (it greys out
the username and password once you select Windows Authentication)?
--
Thanks,
TheBurgerMan
at
gmail.com
--
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23o9fE$UmGHA.5076@.TK2MSFTNGP02.phx.gbl...
> You can't do a SQL Server login using a domain account. SQL Server will
> look for a SQL Server login with the name of Domain\User, and pass the
> password you enter. The app need to ask for a Windows login, and the
> credentials will be taken from the account system that validated that
> Windows account (the local machine, for example).
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "TheBurgerMan" <TheBurgerMan@.gmail.com> wrote in message
> news:umAcwjUmGHA.1896@.TK2MSFTNGP05.phx.gbl...
>> The Consultant machines are not members of my Domain, but they are using
>> Domain accounts that I have created. When I created the Consultant
>> accounts, I added them to the Development Group which has profecient
>> rights in SQL server to log in and manipulate databases (my account is a
>> member of this group).
>> I tried the same test on my laptop! I can login with SQL Server Auth
>> into an account that I created on the server AND I can login with Windows
>> Authentication (because my machine is a member of the Domain), but I
>> cannot login with SQL Server Auth with my Domain account! This is what I
>> want to do (then I do not have to start creating a pile of seperate
>> accounts in SQL server as well as AD).
>> --
>> Thanks,
>> TheBurgerMan
>> at
>> gmail.com
>> --
>> "Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
>> news:OyS%23heUmGHA.5076@.TK2MSFTNGP02.phx.gbl...
>> TheBurgerMan wrote:
>> Hi all. We have several consultants on site that need access to our
>> SQL server databases. They have accounts in our domain and I would
>> like to use those accounts in SQL 2005 (actually, as part of a
>> Development group).
>> Since their machines are not part of our Domain, they cannot use
>> Windows Authentication to connect. How can I use SQL Server
>> Authentication and their Domain accounts to allow them to connect to
>> the server?
>> I have tried using the accounts as Domain\Username in the Login box,
>> but I always get 'Microsoft SQL Server, Error: 18456' (I can use other
>> non-Domain accounts to login successfully, so I know the conenctivity
>> is OK).
>> Any help would be appreciated.
>>
>> When you've tried setting these accounts up as Domain\Username, are you
>> using your domain name, or theirs? Is your server a member of your
>> domain?
>>
>|||Try creating a short-cut using the comman runas runas
/user:ComputerName\administrator ?
Change the question mark to the command to be ran as the user after /user:
Tim S
"TheBurgerMan" <TheBurgerMan@.gmail.com> wrote in message
news:%23frHgMVmGHA.3504@.TK2MSFTNGP04.phx.gbl...
> That seems counter-intuitive given that I can use Domain resources,
> authenticating with a Domain username and password, but never be a member
> of said Domain!
> I only want to use this feature in the SQL Server Management GUI. Is
> there a way to pass the Domain credentials using the Windows login (it
> greys out the username and password once you select Windows
> Authentication)?
> --
> Thanks,
> TheBurgerMan
> at
> gmail.com
> --
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
> in message news:%23o9fE$UmGHA.5076@.TK2MSFTNGP02.phx.gbl...
>> You can't do a SQL Server login using a domain account. SQL Server will
>> look for a SQL Server login with the name of Domain\User, and pass the
>> password you enter. The app need to ask for a Windows login, and the
>> credentials will be taken from the account system that validated that
>> Windows account (the local machine, for example).
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "TheBurgerMan" <TheBurgerMan@.gmail.com> wrote in message
>> news:umAcwjUmGHA.1896@.TK2MSFTNGP05.phx.gbl...
>> The Consultant machines are not members of my Domain, but they are using
>> Domain accounts that I have created. When I created the Consultant
>> accounts, I added them to the Development Group which has profecient
>> rights in SQL server to log in and manipulate databases (my account is a
>> member of this group).
>> I tried the same test on my laptop! I can login with SQL Server Auth
>> into an account that I created on the server AND I can login with
>> Windows Authentication (because my machine is a member of the Domain),
>> but I cannot login with SQL Server Auth with my Domain account! This is
>> what I want to do (then I do not have to start creating a pile of
>> seperate accounts in SQL server as well as AD).
>> --
>> Thanks,
>> TheBurgerMan
>> at
>> gmail.com
>> --
>> "Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
>> news:OyS%23heUmGHA.5076@.TK2MSFTNGP02.phx.gbl...
>> TheBurgerMan wrote:
>> Hi all. We have several consultants on site that need access to our
>> SQL server databases. They have accounts in our domain and I would
>> like to use those accounts in SQL 2005 (actually, as part of a
>> Development group).
>> Since their machines are not part of our Domain, they cannot use
>> Windows Authentication to connect. How can I use SQL Server
>> Authentication and their Domain accounts to allow them to connect to
>> the server?
>> I have tried using the accounts as Domain\Username in the Login box,
>> but I always get 'Microsoft SQL Server, Error: 18456' (I can use other
>> non-Domain accounts to login successfully, so I know the conenctivity
>> is OK).
>> Any help would be appreciated.
>>
>> When you've tried setting these accounts up as Domain\Username, are you
>> using your domain name, or theirs? Is your server a member of your
>> domain?
>>
>sql
Wednesday, March 21, 2012
How to login to SQL 2005 using your Domain credentials in "SQL Server Authentication" mode
Labels:
access,
authentication,
consultants,
credentials,
database,
databases,
domain,
login,
microsoft,
mode,
mysql,
oracle,
server,
sql
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment