Hi Josh,

If you have access to IIS Manager on the server, do the following:

1. Select the site from the "Sites" list in the "Connections" pane on the left.
2. Select "Authentication" from the "IIS" section in the "Features" view.
3. Select "Anonymous Authentication" and then select "Edit" in the "Actions" pane on the right.
4. Verify the "Anonymous user identity" has read access to the directory containing your site files.
   1. If "Specific user" is selected, you'll be checking for the user account listed.
   2. If "Application pool identity" is used, you'll more than likely be checking for a user account with the same username as the name of your application pool. For example, if your application pool is named "My Cool Website", the user account will be named "My Cool Website".
      • If this user doesn't exist on the site directory, you'll need to add it. To do so, add the user as you would any other user except you'll need to use "IIS AppPool\My Cool Website" as the username. Windows doesn't list these users so you'll need to type it and you have to use the "IIS AppPool\" prefix. Once you add the user the prefix disappears.
5. Go back to the sites "Features" view and select "Basic Settings" under "Edit Site" in the "Actions" pane on the right.
6. Click the "Connect as…" button and verify "Application user (pass-through authentication)" is selected.

Hope this helps,
Joe D.

Hi Josh,

Well, looking at this again, I see you meant the homepage was the only page doing this. We've had this crop up before and people usually say homepage does it but then we figure out that all pages do it.

You might want to review what I wrote earlier but I don't think it's going to fix the problem in this case.

Default doc is probably your culprit.

Thanks,
Joe D.

Glad its working.

fyi the /Setup/Default.aspx page does not do anything with file system permissions, it is not capable of changing them at all. When files are uploaded from one machine to another though the permissions can be lost sometimes because each file has an "owner" sid and the owner sid from one machine is not recognized on another machine.

never fear to run the setup page though, it can never hurt anything