ICMP: type 3 code 4 Errors

Try a different web browser. If you're using IE, try downloading Google Chrome or Firefox and accessing the site from that browser.
Google Chrome: Get fast free web browser
Firefox: Download Firefox Free Web Browser

The Web server (running the Web Site) encountered an unexpected condition that prevented it from fulfilling the request by the client (e.g. your Web browser or our CheckUpDown robot) for access to the requested URL.
This is a 'catch-all' error generated by the Web server. Basically something has gone wrong, but the server can not be more specific about the error condition in its response to the client. In addition to the 500 error notified back to the client, the Web server should generate some kind of internal error log which gives more details of what went wrong. It is up to the operators of the Web server site to locate and analyse these logs.

500 errors in the HTTP cycle

Any client (e.g. your Web browser or our CheckUpDown robot) goes through the following cycle when it communicates with the Web server:

• Obtain an IP address from the IP name of the site (the 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 the 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 that it recognises as '500'. (Last updated: March 2012).

Fixing 500 errors - general

This error can only be resolved by fixes to the Web server software. It is not a client-side problem. It is up to the operators of the Web server site to locate and analyse the logs which should give further information about the error.

Fixing 500 errors - CheckUpDown

Please contact us (email preferred) whenever you encounter 500 errors on your CheckUpDown account. We then have to liaise with your ISP and the vendor of the Web server software so they can trace the exact reason for the error. Correcting the error may require recoding program logic for the Web server software, which could take some time.

The 404 or Not Found error message is a HTTP standard response code indicating that the client was able to communicate with the server, but the server could not find what was requested.

The web site hosting server will typically generate "404 - Not Found" web page, when users attempts to follow a broken or dead link, hence the 404 error is one of the most recognizable errors users can find on the web.

A 404 error should not be confused with "server not found" or similar errors, in which a connection to the destination server could not be made at all. A 404 error indicates that the requested resource may be available again in the future; however, the fact does not guarantee the same content.

Try a new LAN cable between devices. Hard reboot bother router and modem.
The final solution is a factory reset of your router. You can do a factory reset by logging into the router using you browser. Go to the settings and perform a factory reset

If you forgot the router password, you ill have to do a factory reset by locating a small hold on the back of the router and insert the tip of of paper clip for about 10 seconds while the power is on. The router will be reset to out of box status and then you can set-up form scratch.

Check this tip out from Linksys. It is for a G VPN Router but you could use the same steps to troubleshoot. Title: Resolving Blinking Power or Diag LED on a Linksys Wireless-G VPN Router Article ID: 4982 If the Power LED on your Linksys router is blinking, this means the device is not ready. It should go off once the router completes its diagnostic test. If the Power LED won?t go off, it indicates that there?s a possible hardware problem with the router. To resolve this, you will need to perform five steps: Resetting the Router Assigning Static IP to the Computer Pinging the Router Accessing the Router?s Web-based Setup Page Updating the Router?s Firmware For instructions on how to reset the router, follow the steps below. Resetting the Router Hold in the RESET button at the back of the router for 30 seconds. Unplug the power to the router then plug it back in. If after resetting the router and the Power LED is still blinking, try resetting the router again for another 30 seconds. Then proceed with assigning a static IP address on the PC. For instructions, follow the steps below. Assigning a Static IP Address on Your Computer Most of the time, if the power LED on the router is blinking it loses its ability to assign IP addresses to the PCs connected to it, which is why you need to assign the computer a static IP address. After assigning a static IP address on the computer, check if the computer is still communicating to the router by performing a ping test. To ping the router, follow the steps below. Pinging the Router Ping test helps trace the communication between the computer and the router. The computer sends packets to the router and in return the router sends out replies to validate the connection. In this example, our router IP address is 192.168.1.1. NOTE: If you?re using Windows 98 or ME, click here. Windows 2000/XP Step 1: Click Start, then Run. Step 2: When the Run window opens, type ?cmd? in the Open field, then click OK. Step 3: When the MS DOS Prompt appears, type ?ping 192.168.1.1? and press [Enter]. Step 4: Check the ping statistics. You should get Packets: Sent =4, Received =4, Lost = 0 (0% loss). NOTE: If you?re not getting good replies from the router, it means the router is not communicating properly with the computer anymore. You can already consider the device defective. Windows 98/ME Step 1: Click Start, then Run. A window similar to Step 2 will appear. Step 2: When the Run window appears, type ?command? in the Open field, then click OK. Step 3: When the MS DOS Prompt appears, type ?ping 192.168.1.1? and press [Enter]. Step 4: Check the ping statistics. You should get Packets: Sent =4, Received =4, Lost = 0 (0% loss). NOTE: If you?re not getting good replies from the router, it means the router is not communicating properly with the computer anymore. You can already consider the device defective. If you get good responses from the router, access the router?s web-based setup page to see if a firmware update is possible. For instructions, follow the steps below. Accessing the Router?s Web-based Setup Page In order to perform a firmware update, you should be able to access the router?s web-based setup page. Updating the firmware is one way of resolving the blinking power light on the Linksys router. To access the router?s web-based setup page, click here. NOTE: If you?re having difficulties accessing the router?s web-based setup page, the router is considered defective. If you?re able to access the router?s web-based setup page, proceed in updating the firmware upgrade.

1.the installation CD is important and can be obtain through the manufacturer. It has pertinent files that are necessary to communicate with the operating system and the hardware on the PC.
2.Call Belkin and get a replacement CD

make sure the dsl modem is in bridge mode. you do this by connecting directly to the modem then accessing modem configuration page. after doing this connect the way everything was before. now go to router admin page, then setup tab at the top, then choose internet, manual setup. in the place where its says my internet connection is select PPPoE. then put in your dsl username, password and etc. save settings. this should fix the problem

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\etc
The 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.htm
Select: 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)

TOOLS -> ADVANCED RULES -> ADD -> configure below:

- General Tab
---- Rule Description: Allow ICMP Type 3,4
---- Action: Allow this traffic
---- Advanced Settings: All network interface cards
---- Screensaver Mode: Both on and off
---- Record this traffic in "Packet Log" [OPTIONAL]

-Hosts Tab
---- Remote Host: All addresses

- Ports and Protocols Tab
---- Protocol: ICMP
---- Select:
------- Destination Unreachable - 3
------- Source Quench - 4
---- Traffic Direction: Both

- Scheduling Tab
---- Enable Scheduling: UNCHECKED

- Applications Tab
---- [NOT NEEDED]

hope this helps,
trin

k first delete all temp files and cookies and clear history>and change teh dns to global one>i hope that u pinged with the web site have u tried ping with the ip address of teh web site>then here the way to change teh dns to static
start-->control panel-->and network connection-->right click on local area conn-->properties-->and high light the TCP/IP-->and click properties and u can see a dialog box>in that look @ the left side down u can see obtain DNS sufficx>and use the current following DNS select that and the DNS range is
4.2.2.1
4.2.2.2>and apply and ok>and reboot the pc>and check with teh web site iam sure its a dns issue>and rate me solved if its help full thx