Re: SQLConnect domain user

As far as the application is concerned, that is the 'correct' way to do it. There may be some kludges that would allow otherwise -but I would hope not since it would create a security issue.

--
Arnie Rowland*
"To be successful, your heart must accompany your knowledge."



"Adrian Dev" <adrian.owen@xxxxxxxxxxxxxxxxxx> wrote in message news:uGqKbRvnGHA.4784@xxxxxxxxxxxxxxxxxxxxxxx
Thanks Arnie I shall to do that.

But is the only way to use a domain user, through integrated security?

thanks

"Arnie Rowland" <arnie@xxxxxxxx> wrote in me
ssage news:usDSG8unGHA.3772@xxxxxxxxxxxxxxxxxxxxxxx
In the ADO connection strng: Do NOT pass in the username/password. Use: Integrated Security=SSPI instead of uid/pwd.

Using osql, use -E instead of uid/pwd.

--
Arnie Rowland*
"To be successful, your heart must accompany your knowledge."



"Adrian Dev" <adrian.owen@xxxxxxxxxxxxxxxxxx> wrote in message news:%23kxuPfunGHA.4604@xxxxxxxxxxxxxxxxxxxxxxx
Hi,


I have database, I created a db_owner and linked it to an AD Domain user.

But I cannot connect from my C# program. It fails to login every time.

I've tried with connectstring:

.. uid=MyDOM\MyUser.. and .. uid=MyDOM\\MyUser..

everytime the connection fails.


Also,

How can you test that the domain user works, osql doest seem to support it?


thanks in Advance, Adrian

Relevant Pages

  • Re: SQLConnect domain user
    ... Using osql, ... "To be successful, your heart must accompany your knowledge." ... I created a db_owner and linked it to an AD Domain user. ... everytime the connection fails. ...
    (microsoft.public.sqlserver.connect)
  • SQLConnect domain user
    ... I created a db_owner and linked it to an AD Domain user. ... It fails to login every time. ... everytime the connection fails. ...
    (microsoft.public.sqlserver.connect)
Loading