Windows authentication.

Hi Smith,

I guess your application is an ASP.Net application as it uses a webconfig
file? If so, Windows Authentication may not work for you in this case
because when you use the Windows Authentication as the authentication mode
for your SQL Server, (I don't know where you host your web application but I
assume it's going to be hosted by a hosting company) your web application
will try to connect to your SQL Server with a not trusted user account which
will needed to be authenticated by the AD or something. And as it's a not
trusted user, it'll fail.

In such cases you should use SQL Authentication. And your connection string
would be something like "data source=localhost; initial catalog=mydb;
uid=testuser; pwd=****"

Windows Authentication is very useful in domain environments where there is
trust relationship between clients and server and your clients are members
of domain.

--
Ekrem Önsoy


"Smith" wrote in message

> Dear professional.
>
> I would appreciate if anyone can reply me about this. As my understanding
> and microsoft also recommend that always use Windows authentication mode
> for security. Can anybody let me know if I use windows authentication mode
> then how application and database connect each other, is there any buildin
> machine level user or how to mention in my webconfig file to connect to
> database and what if I want to connect my database from client side, which
> userid should I provide to connect as I am using windows authenciation
> mode. In mixed mode we can create couple of uses and use that users to
> connect to sql server (query analyzer). What I have to use in Windows
> authentication mode and Both client and server are not in same Domain or
> may be both are on workgroup.
>
> Please advice.
>
> Thanks
 >> Stay informed about: Windows authentication.