I have created an application pool in IIS 6.0 and configured it to use a
domain account. The application pool starts up ok. I have also added the
domain account to IIS_WPG group and granted it change process token and
adjust memory quotas for a process identity.

When I turn on integrated windows authentication on apps under this pool, i
get a pop-up instead of getting authenticated. resetting the app pool to the
default pool (running as network service) resolves the authentication
problem.

What am I doing wrong?

Thanks,
Gursharan

[ Post a follow-up to this message ]

Is this machine also in a domain?   If so, you forgot to read the following
documentation associated with Custom Application Pool Identity.

http://www.microsoft.com/resources/...rkridentity.asp

--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Gursharan Singh" <v-guruje@microsoft.com> wrote in message
news:%23STbr11bEHA.716@TK2MSFTNGP11.phx.gbl...
I have created an application pool in IIS 6.0 and configured it to use a
domain account. The application pool starts up ok. I have also added the
domain account to IIS_WPG group and granted it change process token and
adjust memory quotas for a process identity.

When I turn on integrated windows authentication on apps under this pool, i
get a pop-up instead of getting authenticated. resetting the app pool to the
default pool (running as network service) resolves the authentication
problem.

What am I doing wrong?

Thanks,
Gursharan

[ Post a follow-up to this message ]