It really depends on what you are doing. IUSR_MachineName is the anonymous
account. If you are truly running a process on behest of the anonymous user,
give IUSR_MachineName rights. In traditional ASP, IUSR_MachineName was a bit
more of a king.
In ASP .NET, there are some other accounts created to run behind the scenes
processes. For example, you have an ASPNET machine account. This account is
where much of the code runs (as well as the worker process). Giving this
account access is often more important than IUSR_MachineName.
I won't even mention IWAM_MachineName right now, as it could get a bit too
deep.
NOTE: ASPNET is a User, which is why giving access to Users works.
--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
************************************************
Think Outside the Box!
************************************************
"feng" <an*******@discussions.microsoft.com> wrote in message
news:24*****************************@phx.gbl...
My ASP.Net app need write permission for a folder on the
web server. What confuses me is that I can only make it
work if I give it write permission to the server machine's
Users group. It doesn't work if I give the same permission
to the IUSR_<machine name> user. It's been my
understanding all along that it is the IUSR_<machine name>
running the web server process. Now I am lot. Can someone
explain it to me?
Thanks
feng