views:

250

answers:

3

I am getting the following error while browsing my asp.net page deployed in IIS:

You are not authorized to view this page
You do not have permission to view this directory or page using the credentials that you supplied. 
--------------------------------------------------------------------------------

Please try the following:

Contact the Web site administrator if you believe you should be able to view this directory or page. 
Click the Refresh button to try again with different credentials. 
HTTP Error 401.1 - Unauthorized: Access is denied due to invalid credentials.
Internet Information Services (IIS)

--------------------------------------------------------------------------------

Technical Information (for support personnel)

Go to Microsoft Product Support Services and perform a title search for the words HTTP and 401. 
Open IIS Help, which is accessible in IIS Manager (inetmgr), and search for topics titled Authentication, Access Control, and About Custom Error Messages.

Is this something regarding the issue with dns settings?

+1  A: 

It's not a DNS issue: if it was, the host could not have been found.

If you are using IIS, the authentication of the site is probably not set correctly.

Gergely Orosz
i am using active directory retrieval into the website ..is that was an issue ?
yea ,, now i am getting page not found error also..when i unticked the windows integrated authentication. is that a dns issue ?
A: 

A 401 error is not DNS related. It means that the account that IIS is running under (or the account being passed to it for authorization and authentication) does not have rights to execute the page. It is more likely a security issue on the folder structure for your application. Verify what account your site is running under, and that it has read rights in Windows to the root folder and subfolders.

Agent_9191
yes it has ... read rights ...now i am getting page not found error also..when i unticked the windows integrated authentication. is that a dns issue ?
Are you able to get to anything on that server? If so, it's not a DNS issue.
Agent_9191
other websites are working fine!!
+1  A: 

A 401 error is likely not a DNS issue itself; it simply means that, for some reason, the user is not authorized to view the page. This could be because IIS cannot view the page, or because web application does not allow the current web user to view the page.

That said, it may be possible for DNS to still be the culprit. If DNS is used as a piece of the authentication system (which, I believe, may be the case with Active Directory), and the server cannot correctly use DNS to do the resolution it needs to authenticate users, then yes, DNS probably cause a 401.

Michael E
so what could be resolution here? if this is cause of active directory?