The following was pulled directly from the BOL section I referenced. It is
pretty clear that a domain account must be used.
SQL Server achieves login security integration with Windows NT 4.0 or
Windows 2000 by using the security attributes of a network user to control
login access. A user's network security attributes are established at
network login time and are validated by a Windows domain controller. When a
network user tries to connect, SQL Server uses Windows-based facilities to
determine the validated network user name. SQL Server then verifies that the
person is who they say they are, and then permits or denies login access
based on that network user name alone, without requiring a separate login
name and password.
[quoted text, click to view] "DrBob" <DrBob@discussions.microsoft.com> wrote in message
news:24057E2A-42AD-4704-B0C6-A8FA44CCFDF1@microsoft.com...
> I understand that - I have a Win2003 network with a domain controller and
> accounts set up in active directory - my question is: must the server
and/or
> the client log on to windows in the domain account or will windows
> authentication work if they log on to a local account?
>
>
> "Scott Morris" wrote:
>
> > Windows authentication requires a network with a domain controller. You
> > might want to give the section titled Authentication Modes in BOL a
look.
> >
> > "DrBob" <DrBob@discussions.microsoft.com> wrote in message
> > news:9C1D4FCE-3AF1-45B6-8242-C830C7B9CE65@microsoft.com...
> > > When using windows authentication mode should should the connection
work
> > if
> > > the server and client are logged on to windows using "this computer",
or
> > must
> > > they log on to windows using a domain account - i can't seem to
connect
> > using
> > > windows authentication, only with a sql account
> >
> >
> >
