Arne,
The permissions ASPNET or it's equivalent will need to run properly on a
windows 2000/IIS 5 box, are detailed here.
http://www.microsoft.com/resources/...aaconaspnetrequiredaccesscontrollistsacls.asp
You are on the right path in your thinking about creating a matching
username/password on both machines. On the SQL Server it has access to the
DB, and on the web server this user has access to as per the definied in the
link above.
Once you're done with this setup, you have two options - which essentially
substitute for the Application pool setup we did for IIS6.
You can put that in your web.config as --
<system.web>
<authorization>
<identity impersonate="true" userName="yourNewUsername"
password="yourStrongPassword" />
</authorization>
</system.web>
Or, you can let IIS impersonate those details in two steps (better way)
Step #1 -- In the properties for your website/virtual dir, go to Directory
Security and click the edit button beside Anonymous access and
authentication control configure the new username and password over there.
Step #2 - Let IIS provide those impersonation details via a trusted
connection by editing your web.config as follows -
<system.web>
<authorization>
<identity impersonate="true" />
</authorization>
</system.web>
A YET another way is to edit the machine.config file and put the pasword in
there to edit the default context. This would be at
<processmode .. userName="ASPNET" password ="YourNewFunkyPassword"/>
This is obviously global and a bit less secure.
- Sahil Malik
http://codebetter.com/blogs/sahil.malik/