Keith
Fri Nov 07 16:45:27 CST 2003
>-----Original Message-----
>"Keith" <anonymous@discussions.microsoft.com> wrote in
message news:<0c7501c3a547$f8e19420$a401280a@phx.gbl>...
>> >-----Original Message-----
>> >I have a Windows 2003 server as a Member Server, not a
>> Domain
>> >Controller. I have integrated authentication checked
in
>> IIS. This
>> >seems to work from the clients. However, if the
webpage
>> has a
>> >datasource in its asp page, then I get an error that
says
>> the user
>> >does not have permission to get to the object that the
>> page is trying
>> >to get to (the web page itself is allowed). Doing the
>> same thing from
>> >a domain cotroller (from the client again) yields the
>> data. The IUSR
>> >account is not being used on any of them; it is all
>> purerly supposed
>> >to run on integrated authentication. Does the fact
that
>> my 2003
>> >server is not a domain controller have anything to do
>> with it? It
>> >seems to be. The white papers from Microsoft say that
>> 2003 member
>> >servers can be used for web servers. Thanks.
>> >.
>> >
>>
>> Is the Member server in the same Domain, a trusted, or
>> trusting domain of the Domain controller?
>
>It is a member server in a Windows 2000 mixed domain.
The 2003 Server
>is not a Domain Controller.
>.
>
Integrated Authentication (at least in Win2K) only works
when all the servers involved and the client are
authenticated (or trusted) by the same Domain. If your
client login, web server computer account, or data source
server computer account is in another Domain (and not
Trusting) then Integrated Authentication prompts for
Username and password.
http://msdn.microsoft.com/library/default.asp?
url=/library/en-us/comsrv2k/htm/cs_gs_security_xmky.asp
Just a thought, don't know if it helps.