We have some users of a .NET application getting HTTP 400 on a web app with
Integrated Windows Security. Switching the setting back to allow anonymous
access fixes the problem.
It seems the problem is with the user account in the windows domain. Is
there a way we can check to see what's wrong, so that we can fix it?
On Fri, 27 May 2005 14:11:05 -0700, Kiet Tran
>We have some users of a .NET application getting HTTP 400 on a web app with
>Integrated Windows Security. Switching the setting back to allow anonymous
>access fixes the problem.
>
>It seems the problem is with the user account in the windows domain. Is
>there a way we can check to see what's wrong, so that we can fix it?
Log files would be a good place to start.
Jeff
Check the httperr.log file...
Cheers
Ken
--
Blog: www.adopenstatic.com/cs/blogs/ken/
Web: www.adopenstatic.com
"Kiet Tran"
news:6293CD67-EE40-4600-8F50-EE046CD1651A@microsoft.com...
: We have some users of a .NET application getting HTTP 400 on a web app
with
: Integrated Windows Security. Switching the setting back to allow
anonymous
: access fixes the problem.
:
: It seems the problem is with the user account in the windows domain. Is
: there a way we can check to see what's wrong, so that we can fix it?