What are common browser error messages?
Browsers can send back some strange number error messages and give you a message box that can be confusing. This page attempts to inform you of what those messages mean.
> 404 Not Found The browser could not find the specific document that you requested on the host computer.
To resolve this error, check the Uniform Resource Locator (URL) syntax (some URLs are case sensitive). In addition, the page may have been removed, had its name changed, or have been moved to a new location.
> 403 Forbidden/Access Denied
The Web site you requested requires special access permission (for example a password).
> 503 Service Unavailable
The host computer is too busy. Try viewing the page again after about 30 seconds.
> Bad File Request
The form or the Hypertext Markup Language (HTML) code for an online form has an error.
> Cannot Add Form Submission Result to Bookmark List
The results of a form (such as a WebCrawler search) cannot be saved as a bookmark. A bookmark can only be a document or an address.
> Connection Refused by Host
This is a version of the 403 error. The Web site you requested requires special access permission.
> Failed DNS Lookup
The Web site's URL could not be translated into a valid Internet protocol (IP) address. This error is common on commercial sites because the computers responsible for translating the IP addresses are overloaded. Try again later when there may be less Internet traffic. This can also be caused by a URL syntax error (the URL has incorrect format).
> HTTP Server at Compressed .com:8080 Replies:HTTP/1.0 500 Error from Proxy:
This error is common with proxy servers (a server on a local area network that lets you connect to the Internet without using a modem). The proxy is either down, busy, or cannot interpret the command that was sent to it. You may want to wait for 30 seconds or more then try viewing the page again. If the problem persists, contact the network administrator of that proxy. Whatever is shown instead of .com is usually your Internet service provider.
> File Contains no Data
The browser found the site, but nothing in the specific file. Try adding ":80" (without the quotation marks) to the URL just before the first slash, for example: http://www.jps.net:80/
> Helper Application not Found
You have attempted to download a file that needs a helper program, and your browser cannot find the program. On the browser's preferences or options menu, make sure the correct directory and file name are entered for the helper program. If you do not have a helper program, save the file to disk and obtain the helper program.
> NTTP Server Error
The browser could not find the Usenet newsgroup that you tried to access. Make sure the news server address is correctly listed in your browser's preferences or options menu and try again.
> Not Found
The link no longer exists.
> Site Unavailable
Too many users are trying to access the site, the site is down for maintenance, there is noise on the line, or the site no longer exists. This can also be caused by a user URL syntax error (The web address was typed incorrectly).
> TCP Error Encountered While Sending Request to Server
This error is caused by erroneous data on the line between you and the requested site.
> Too Many Users
The site is busy. You may want to try again after about 30 seconds.
> Unable to Locate Host
The URL did not return anything, the site is unavailable, or the Internet connection was dropped. Check the hardware connections and URL syntax.
> Cannot Connect to Server
This error can occur if you are using Secure Sockets Layer (SSL) security ("https" at the beginning of the URL) when you are connecting to certain Web servers. Try to reach the site by typing http:// instead.
What are common FTP error messages?
Because of the wide variety of FTP programs available, error messages may vary.
> Invalid Host or Unable to Resolve
This is the FTP equivalent of the Web browser's 404 error. The FTP program cannot find the site requested. This can also be caused by a URL syntax error.
> Problem: Your FTP program connects then suddenly stops responding.
If this occurs shortly after you log on, try using a dash (-) as the first character of your password. This turns off the site's informational messages, which may be causing a conflict with the FTP program.
> Problem: Too many consecutive transmit errors
This indicates that line noise has prevented the FTP program from continuing. This could be a hardware problem, the command string sent to your modem may be incorrect, or the modem may not be properly configured.
