views:

959

answers:

3
A: 

Chances are that whatever your ASP.Net process is running as does not have access to the share.

So chances are you need to set up an IIS6 application pool to run as a domain user and have that domain user have access rights to the file share.

Don't forget to aspnet_regiis -ga {domainuser} so that the domain user can actually run asp.net applications.

Min
+1  A: 

I hope your site use anonymous access. Otherwise you will have a painful experience.

If it is so ( anonymous acess), then: The IUSR is a local user on the production servers and not a domain user. So it don't have access the the share. You will have to change that to a domain user ( in the site configuration and not on the application pool). And make sure that the application pool run on a network service ( this is the default ) and it should work.

Igal Serban
+1  A: 

FYI,

The answer to this solution for me was to setup temporary impersonation with a user account that had access to the share, the folder and the virtual directory.

Here's a link to the code that worked for me:

http://support.microsoft.com/kb/306158#4

Ryan Smith