Your Web server thinks that the HTTP data stream sent by the client (e.g. your Web browser or our CheckUpDown robot) was correct, but access to the URL resource requires user authentication which 1) 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.
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.).
401 errors in the HTTP cycle
Any client (e.g. your Web browser or our CheckUpDown robot) goes through the following cycle:
Obtain an IP address from the IP name of your site (your site URL without the leading 'http://'). This lookup (conversion of IP name to IP address) is provided by domain name servers (DNSs). Open an IP socket connection to that IP address. Write an HTTP data stream through that socket. Receive an HTTP data stream back from your Web server in response. This data stream contains status codes whose values are determined by the HTTP protocol. Parse this data stream for status codes and other useful information. This error occurs in the final step above when the client receives an HTTP status code it recognises as '401'.
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 your Web page.
If this type of browser check indicates no authority problems, then it is possible that your 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 your Web server.
Fixing 401 errors - CheckUpDown
When you set up your CheckUpDown account, you may optionally provide two items 2. Web Site User ID and 3. Web Site Password. You should provide these only if your site uses HTTP Basic Authentication. If you provide them, the CheckUpDown robot always uses them. This will result in a 401 error if in fact your site does not use this authentication. Conversely, if you do not provide them and your site does use this authentication, you also get a 401 error.
If however your URL is open to all comers, then an 401 message should not appear. Because it indicates a fundamental authority problem, we can only resolve this by negotiation with the personnel responsible for security on and around your Web site. These discussions unfortunately may take some time, but can often be amicably resolved.
Alternatively or the other way around is :

open the XP hosts file, and do a manual insert there.
The hosts file is located at: C:\WINDOWS\system32\drivers\etcThe entry is: 192.168.0.1 www.routerlogin.net
You might need to flush your DNS records at this point, or simply restart your computer.
And then use the following URL to access the admin page:http://www.routerlogin.net/setup.cgi?next_file=start.htm***Here is another solution to the problem, which is a fairly straight-forward way to disable the annoying wizard.Type in your browser:http://www.routerlogin.com/CA_HiddenPage.htmSelect: Disable Configuration Assistant, and click on Apply.You can re-enable it by navigating to http://192.168.0.1/CA_HiddenPage.htm (where 192.168.0.1 is your router’s IP address)

a. Go to Start and then click Run. b. Type cmd (Windows 2000 or XP) or command (Windows 98 or ME) then click on OK. c. On the command prompt, please type "ipconfig/all" and then press Enter.d. Look for the Default Gateway. This is the IP address of the router. Usually, it is a 192.168.1.1.

Note: In this example, we used 192.168.1.1 as the IP address of the router.

d. There should be replies from the Default Gateway address. Look for ping statistics and you should see a sent: 4 and receive: 4.

3. Optimize browser settings.

a. Please open Internet Explorer and click Tools.b. Select Internet Options then click Connections.c. Click on LAN Settings. Make sure that all boxes are clear and then click OK.d. Click on General Tab. Click on Delete Files, Delete Cookies and Clear History buttons. Then click Apply.e. Click on Security tab.f. Click on Internet and Custom level icons.g. Under the Settings list, scroll down and set the User Authentication to Automatic Login. Then please click on OK.h. Go to Advance tab and click on Restore Defaults or Reset. Please click on OK.

4. Access the web-based utility of the router.

a. Open any web browser like Internet Explorer or Netscape Navigator.b. Connect to the router by typing http://routerlogin.com/basicsetting.htm or http://192.168.1.1 in the address field and click Enter or Return key.c. For security reasons, the router has its own user name and password. When prompted, enter admin for the user name and password for the password, both in lower case letters.

Note: If it does not take password as the password, you might have changed it when you have run the setup CD so please try other passwords. If you cannot remember the password, you need to reset the router and run the NETGEAR Setup CD to reconfigure it.

If it still does not work, please try the following:

5. Reset the router.

a. Please push the reset button at the back of the router and release after 30 seconds. b. Unplug the power adapter for 10 seconds and then plug it back in.

If you still cannot access the routers page, try another computer and connect it on your router. Then repeat the steps.

Here are some troubleshooting steps that I suggest you try:

1. Check physical connections.

a. Connect the modem to the Internet port of the router. The Internet “i” LED on the front of the router should light up. b. Connect the computer to one of the four LAN ports (i.e port 1, 2, 3 or 4) on the back of the router. The corresponding port light where you connected the computer should be lit up.

2. Access the router's web-based utility.

a. Please open any web browser like Internet Explorer or Netscape Navigator. b. Connect to the router by typing http://routerlogin.com/basicsetting.htm or http://192.168.1.1 in the address field and click Enter or Return key. c. A window will prompt for a user name and password. By default, the user name is "admin" and the password is "password".

Note: If you were unable to access the router's web-based utility, you may reset the router to restore the settings to factory default.

To reset the router:

a. Please push the reset button at the back of the router and release after 30 seconds. b. Unplug the power adapter for 10 seconds and then plug it back in.

3. Configure the router.

If your Internet Service Provider is using a cable connection, please follow the steps below:

a. Click on Basic Settings under Setup tab. b. Select No for Does Your Internet Connection Require A Login?. c. Scroll down on the center page and look for the Router MAC Address section. Set it to Use computer MAC address and click on the Apply button.

If your Internet Service Provider is using a DSL connection, please follow the steps below:

a. Click on Basic Settings.b. Select Yes for Does Your Internet Connection Require A Login?.c. Select Other on the Internet Service Provider drop down box.d. Enter your ISP's username (username@ISPdomain) and password. Then, click on Apply.

4. Configure the wireless settings.

a. Click on the Wireless Settings under Setup. b. Change the SSID to any unique name. c. Scroll down, look for the Security Options settings and select WEP (Wired Equivalent Privacy). d. Set the Authentication type to "Automatic" and the Encryption Strength to "64bit". e. Leave the Passphrase field blank, select Key 1 and enter a 10-digit number.

Note: The 10-digit number you typed in the key 1 will be the password or network key for the wireless connection.

f. Click Apply button to save the changes. g. Go to Router Status under Maintenance tab and check if there is an IP address under Internet port. If it's 0.0.0.0, do a power cycle.

5. Power cycle.

a. Power off the modem, router and computers. b. Turn on the power of the modem first and wait for it to initialize, the lights to stop blinking. c. Power back the router and the computers. Check if it will be able to get online.

If you have wireless computers, you can connect them wireless to the router. Kindly follow the instructions below:

6. Connect wireless computer to the router.

If you are using Windows XP with Service Pack 1, please follow the steps below:

a. Please right click on the Wireless icon on the right lower end portion of your computer. b. Then click on View Available Wireless Networks. c. Click on the Advanced tab. d. Please delete all the preferred networks then click on OK. e. Right click on the Wireless icon again and click on View Available Wireless Network. Please select your network and click on Connect. It will ask you for the network key. f. Please type in the network key and then confirm it. Network key is the password you type on the key 1 of the wireless settings of the router. g. Make sure not to enable IEEE and then click on Connect.

If you are using Windows XP with Service Pack 2, please follow the steps below:

a. Please right click on the Wireless icon on the right lower end portion of your computer. b. Then click on View Available Wireless Networks. c. Click on the Change Advanced Settings. d. Click on the Wireless Networks tab remove all the preferred networks then click on OK. e. Right click on the Wireless icon then click on View Available Wireless Networks. f. Select your network and click on Connect. g. It will ask you for the network key. Type in the network key and confirm it. Then click on Connect. Network key is the password you type on the key 1 of the wireless settings of the router.

If you are using Windows Vista, please follow the steps below:

a. Click Start then select Connect To. b. Connect to a network window will show up. c. Select your wireless network and click Connect. d. It will ask you for a network key. Type in the network key and confirm it. Then click on Connect.

From the above configuration, please check if you can now access the Internet.

Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.

Related Questions:

"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.)."

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:

http://localhost/IISHelp

or

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.

No, but you can just reset the whole router and start from scratch. Hold the reset button on the rear of the router for 60 seconds and your will restore the unit to defaults, at which point you just need to reconfigure all of your configuration settings and password, as well as your wireless access code. Let me know if you require any additional assistance.

401 is a server error, it means that the page that you are trying to view is not located on the server. Verify that you have the correct spelling, filename completely, extension (.html, .htm, .php, etc) and that you are in the correct directory in case the file that you are trying to view is not in the root/www directory.

Your Web server thinks that the HTTP data stream sent by the client (e.g. your Web browser or our CheckUpDown robot) was correct, but access to the URL resource requires user authentication which 1) 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.
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.).
401 errors in the HTTP cycle
Any client (e.g. your Web browser or our CheckUpDown robot) goes through the following cycle:
Obtain an IP address from the IP name of your site (your site URL without the leading 'http://'). This lookup (conversion of IP name to IP address) is provided by domain name servers (DNSs). Open an IP socket connection to that IP address. Write an HTTP data stream through that socket. Receive an HTTP data stream back from your Web server in response. This data stream contains status codes whose values are determined by the HTTP protocol. Parse this data stream for status codes and other useful information. This error occurs in the final step above when the client receives an HTTP status code it recognises as '401'.
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 your Web page.
If this type of browser check indicates no authority problems, then it is possible that your 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 your Web server.
Fixing 401 errors - CheckUpDown
When you set up your CheckUpDown account, you may optionally provide two items 2. Web Site User ID and 3. Web Site Password. You should provide these only if your site uses HTTP Basic Authentication. If you provide them, the CheckUpDown robot always uses them. This will result in a 401 error if in fact your site does not use this authentication. Conversely, if you do not provide them and your site does use this authentication, you also get a 401 error.
If however your URL is open to all comers, then an 401 message should not appear. Because it indicates a fundamental authority problem, we can only resolve this by negotiation with the personnel responsible for security on and around your Web site. These discussions unfortunately may take some time, but can often be amicably resolved.
Alternatively or the other way around is :

open the XP hosts file, and do a manual insert there.
The hosts file is located at: C:\WINDOWS\system32\drivers\etcThe entry is: 192.168.0.1 www.routerlogin.net
You might need to flush your DNS records at this point, or simply restart your computer.
And then use the following URL to access the admin page:http://www.routerlogin.net/setup.cgi?next_file=start.htm***Here is another solution to the problem, which is a fairly straight-forward way to disable the annoying wizard.Type in your browser:http://www.routerlogin.com/CA_HiddenPage.htmSelect: Disable Configuration Assistant, and click on Apply.You can re-enable it by navigating to http://192.168.0.1/CA_HiddenPage.htm (where 192.168.0.1 is your router’s IP address)

hi im jules_09.
sc 401 means transfer roller leak error.a transfer current leaksignal is detected.posible causes is 1.transfer power pack is defective 2.poor connection between the transfer terminal and the trnsfer power pack
sc 419 mean quenching lamperor.1 quenching lamp defective 2.poor conection between power pack and quenching lamp.
check all component but pay attetion to the current leak at the transfer because there both connected at the power pack