Hi Michael,

I tried what you've suggested here but we didn't have any luck with this. We use a domain user for each of our application pools, so we granted write permissions for the folder suggested above (and the one under framework64) to the IIS_IUSRS group. Is that how you did it or did you explictly give permission for the actual user rather than the group?

The only way we seem to be able to get it to work properly in our environment is to get the source for the provider and modify it so that the CheckPipelineMode method always returns false. We've done this, because when I'm remote debugging the CheckPinelineMode method all of the properties of the DirectoryEntry are inaccessible with "Access denied" as the content. It's seems pipeline mode check is the only bit giving us grief and we can be 100% sure that we're running in a classic application pool.

Because we don't want to have to use impersonation and run our sites in application pools with domain users, I think modifying the code each time there is a release is the only way we'll be able to get around it - although I'm sure if we ran it as the documentation suggests we wouldn't have any problems.

Cheers Wayne

Is it possible to allow both anonymous access and windows access. I want to allow my anonymous users access to the portal, but then my users on the network windows authentication logged in. It does not have this in the documentation?