This problem may be caused by a number of reasons. However, the following are the most common:
The users credentials (the username and password) are not correct.
The user account may not have the right to log on to the computer interactively (the "Log On Locally" right). In some scenarios, the user account requires "Log On Locally" right.
Check the username and the password of the user to make sure that they are correct.
If this is correct, be sure the user has the "log on locally" right granted to it.
To verify user rights, do the following:
1. Open the Local Security Policy tool from the Administrative Tools folder.
2. Click Local Policies, click User Rights Assignment, and then click the Log On Locally user right.
If the user account or group that the user belongs to is not listed, then add it.
See the Internet Information Services 5.0 documentation for more information about authentication.
This documentation can be found at the following URL example:
The Web server (running the Web site) thinks that the HTTP data stream sent by the client (e.g. your Web browser or our Check Up Down robot) was correct, but access to the URL resource requires user authentication 1) which has not yet been provided or 2) which has been provided but failed authorization tests.
This is commonly known as "HTTP Basic Authentication".
The actual authentication request expected from the client is defined in the HTTP protocol as the WWW-Authenticate header field. (Last updated: March 2012).
Generally this error message means you need to log on (enter a valid user ID and password) somewhere first.
If you have just entered these and then immediately see a 401 error, it means that one or both of your user ID and password were invalid for whatever reason (entered incorrectly, user ID suspended etc.).
Fixing 401 errors - general
Each Web Server manages user authentication in its own way.
A security officer (e.g. a Web Master) at the site typically decides which users are allowed to access the URL.
This person then uses Web server software to set up those users and their passwords.
So if you need to access the URL (or you forgot your user ID or password), only the security officer at that site can help you.
Refer any security issues direct to them.
If you think that the URL Web page *should* be accessible to all and sundry on the Internet, then a 401 message indicates a deeper problem.
The first thing you can do is check your URL via a Web browser.
This browser should be running on a computer to which you have never previously identified yourself in any way, and you should avoid authentication (passwords etc.) that you have used previously.
Ideally all this should be done over a completely different Internet connection to any you have used before (e.g. a different ISP dial-up connection). In short, you are trying to get the same behaviour a total stranger would get if they surfed the Internet to the Web page.
If this type of browser check indicates no authority problems, then it is possible that the Web server (or surrounding systems) have been configured to disallow certain patterns of HTTP traffic. In other words, HTTP communication from a well known Web browser is allowed, but automated communication from other systems is rejected with an 401 error code.
This is unusual, but may indicate a very defensive security policy around the Web server.
Feb 28, 2014 |