Ugh! ASP.NET in "Access to the path denied" problem. 1

[jacktripper]

I've been searching all the forums and trying to fix this all day long. I've tried changing all kinds of permissions, but so far to no avail. Maybe someone else can help?

I have a Web site I built on my local machine, and I can upload files from it to our DEV server through a typical FileUpload control. The location is "\\servername\shared path\uploads" directory. Works great from my computer.

I move the same Web site to the DEV server, and get the infamous ASP.NET is denied access to that path. With all the usual stuff:

ASP.NET is not authorized to access the requested resource. Consider granting access rights to the resource to the ASP.NET request identity. ASP.NET has a base process identity (typically {MACHINE}\ASPNET on IIS 5 or Network Service on IIS 6) that is used if the application is not impersonating. If the application is impersonating via <identity impersonate="true"/>, the identity will be the anonymous user (typically IUSR_MACHINENAME) or the authenticated request user.

Everywhere I have seen, they suggest adding the MACHINENAME\iusr_MACHINENAME and also adding MACHINE\ASPNET as users in the Security tab and Shared permissions with full access rights (my name is also in both). But, I've tried this and still get the same crap.

I even tried deleting the virtual directory, deleting the folders, and rebuilding it all from scratch. Still the same permission denied.

Any other ideas? Windows 2003 Server, by the way.

How can I have access, but the server itself running the web site can't?

 

[ca8msm]

For Windows 2003, use the NETWORK SERVICE account rather than the ASPNET account.

Mark,

Darlington Web Design[tab]|[tab]Experts, Information, Ideas & Knowledge[tab]|[tab]ASP.NET Tips & Tricks

 

[jacktripper]

Holy cow. That worked.

I had tried entering NETWORK SERVICE before, but it said the user could not be found. Until I added the machine name in front of it... Then it popped up.

YAHOO. Thank you so much!