Last post Apr 28, 2014 04:20 AM by marc g
Dec 06, 2007 09:29 AM|claudi|LINK
I got this error after creating the virtual directory and trying to access the webpage through wireless.. I had access before..but somehow I don't have any more
does someone know how to resolve this issue?
Dec 06, 2007 09:56 AMemail@example.com|LINK
Check NTFS permissions on the file/folder.
Dec 06, 2007 10:33 AM|claudi|LINK
Dec 07, 2007 07:24 AM|indigo77|LINK
try to mark the virtual directory as an asp.net application
Dec 07, 2007 07:34 AM|claudi|LINK
May 30, 2009 08:13 PM|itinko|LINK
I tried everything under the sun to get rid of 401.3. It wasn't till I looked at the Security settings of wwwroot and saw that Users had permission to the web folder that I was able to get rid of this error.
May 30, 2009 10:18 PM|tamilcodes|LINK
It just means the current user is not allowed to access.
You may have to allow permissions for ASPNET user and or IUSER ACCOUNT
If you are using xp, right click the userfiles folder select properties, then click on the security tab. Now click add button. In the select users or groups window click advanced button and again click find button. This will find all users to use the system.
In the list find the user ASPNET select it and click OK and again click OK. Now the user is added to the list who can access the folder. It is time to give permission. In the folder properties as ASP.NET user is selected check full control check box below
the ALLOW . This will give the full control to asp.net user.If you create the userfiles or whatever folder in the server ask your hosting provider to set permissions.
Hope this helps.
Feb 06, 2010 03:29 AM|ashish.chotalia|LINK
I just enable Windows Authenitaction on virtual directory and It worked for me,
Hope it helps others..
Access Control Lists
Feb 06, 2010 11:35 AM|AsifQadri|LINK
hi claudi ,
which operating system you are using and version of IIS
follow below instructions you can solve your problems
IIS must first authorize the user to access the file based on ACL's set on that file (usually inherited from parent folder).
In other words, it doesn't matter how you configure your asp.net application because your application code hasn't executed yet at this point.
If you enabled only Windows Integrated security in IIS, then you need to make sure that user has access to Read & Execute the files you wish him to use in your web site. (in the root folder)
If you allow anonymous access then you need to grant the IUSR_<machine> account those same Read & Execute permissions.
But realize that this is just for IIS.
ASP.Net has it's own methods for authentication and authorization.
Based on those settings, you'll also need to apply ACL permissions for the account running the ASP.Net worker process.
By default, this is the "Network Service" account on Win2003. On Win2000 this is the "ASPNet" account.
#you can enable impersonation. In which case, your worker process would execute using the security token of user authenticated through the web browser. However this configuration too comes with caveats, because of deligation issues and that dredded "double
Aug 07, 2013 02:38 PM|be05x5|LINK
Alright after looking around for this forever here is what you do. I would not recommend this on a high risk server simply because I do not know the risks behind it.
Basically you need to give NETWORK SERVICE and IIS_USRS access to the folder from which the app is running.
NETWORK SERVICE is easy to find and do however, the IIS_USRS for me at least doesnt come up if you just type IIS. So I did advanced Search. Selected the Location to be my computer and the IIS_USRS will appear at the bottom. Give read access and see if that
works. Then give more access until it works.
I know that previous users have posted this same information however, I found it a little confusing and didnt realize that these are the 2 users that need access.
Apr 28, 2014 04:19 AM|marc g|LINK
this worked thanks!
Apr 28, 2014 04:20 AM|marc g|LINK
i used IIS_USRS like you said