About MartNet MartNet Technical Support
Home Services Support Members Software Contact
Search Support
MartNet WebMail

MartNet WebAdmin

Dialup Access

Domain Name

MartNet News /
  Status Info

NOC / System Status

Support Topics:
 MartNet WebAdmin
 Virtual Hosting
 Web Site Construction
 Unix / Linux
 Internet Chat
 Game Server Services
 Misc. Stuff
 Policies / Legal

 MartNet WebAdmin
 Virtual Hosting
 Game Server Services
 Misc. FAQ's

 Privacy and Security
 Web Development
 Unix / Linux
 Game Server Services
 Misc. Support Links

MartNet Ad

MartNet Policies
Billing Dept.

Check Domain

Common Browser Errors
Description of common browser error messages and their meanings.

Web Browser Error Messages

Getting an errror message when you're surfing the Web can be frustrating, but it isn't always impossible to overcome. In fact, you can avoid most error messages by using a few simple techniques. Here are some of the most common Internet error messages. Note that the exact wording of the error may vary from browser to browser (or even amongst different versions of the same Browser) :

No DNS Entry Sometimes, you may receive a dialog box saying there's no DNS for the URL you're trying. Check the URL for errors and try again. However, many times Netscape displays this error message mistakenly -- the server may simply be busy, or there's some other error. Try the URL again later. Don't confuse this error with the Failed DNS Lookup error (see below.)

Failed DNS lookup

400 - Bad request This error message indicates that the server can't figure out the URL (Uniform Resource Locator) you requested. The problem often occurs because of incorrect URL syntax. Check the URL for incorrect uppercase or lowercase letters, colons, and slashes. Try typing the URL again. If you still get an error, try to backtrack the URL to the directory the document resides in -- for instance, shorten www.what.com/when/where/who.htm to www.what.com/when/where/. If the error message persists, there may be a problem with the document; contact the site's administrator.

401 - Unauthorized 401 errors usually occur when an Internet site is protected and the server didn't receive the correct encryption ID or password for entry. If you're registered with the site, try your password again if possible. As with URLs, passwords are often case-sensitive, so type the password carefully. You may also get this error from servers that deny access from certain domain types; for example, domain names ending in edu.

403 - Forbidden or Connection refused by host These errors are similar to 401 errors. They usually occur when a server denies access because of your domain, because of security restrictions, or because you don't have a password. These errors also occur when you haven't signed up with a site that requires registration. You can try to register with the site or try your password again. You can also attempt to contact the site's administrator for a password.

404 - Not Found or File Not Found The 404 error often appears as Not Found or simply File Not Found. These errors are very common and occur when the host server can't find the specific HTML (Hypertext Markup Language) document you requested. 404 errors usually stem from a document name change or a document deletion. They can also take place when you've made a syntax error in the document name. Your best bet is to assume you made a mistake when you typed the URL. Backtrack by deleting the portion of the URL that follows the last slash. Then re-access the URL and look for it in the directory you'll receive.

502 - Service Temporarily Overloaded This error indicates that the server is experiencing high-traffic load and can't process the request. You can often access the site by trying to load the site again. If the error persists, try again later.

503 - Service Unavailable This error occurs when your access provider, gateway, or system is down or busy. Your only hope is to wait a minute or two and try again.

Bad file request or Too many users These error messages indicate a problem with HTML coding at the site. The problem may be that your browser doesn't support the form you're trying to access. You can try to bypass this problem by e-mailing the Web site administrator for help.

File contains no data When you get this error, it means that you've accessed the right Web site, but the file you requested is empty. There's a possibility that the site administrator is updating the site, in which case you can try to access the document again later. Helper application not found or Viewer not found These errors occur when your browser doesn't recognize a file. This usually happens when you download a file that needs a specialized viewer; for example, a RealAudio sound file or a compressed file. If you don't have the helper application, your best bet is to save the file to a disk and then try to get the application that will let the browser read the file.

Host unavailableThis error usually occurs when the host server is down. You can try to access the sitea gain by clicking the Reload button.

Host Unknown or Unable To Locate Host These errors often occur for one of three reasons: the host server is down, you lost your Internet connection, or you incorrectly typed the URL. Try clicking the Reload button first. If this doesn't work, look at the URL again. If you still get the error message, check your Internet connection. Network connection was refused by the server or Too many connections - try again later These errors usually indicate that the server is too busy to handle more traffic. You can try the site again by clicking the Reload button, or wait until a later time.

NNTP server error An NNTP server error appears when you try to log on to a USENET newsgroup and can't gain access. This error signals several possible problems. As is often the problem, the host server may be down, or you may have incorrectly typed the URL. It's also possible that the newsgroup you chose isn't available through Citynet. Another possible problem is that you may have incorrectly entered your newsgroup preferences.

Permission deniedThis message occurs when you're trying to upload a file to an FTP site. The message indicates that the site's administrator won't allow the upload, the site is too busy, or that you've used the wrong syntax in the URL. Look at the URL syntax first and type it again. If the error message reappears, you should try again later. If the problem persists, you can try to e-mail the site's Webmaster for help.

Unable to locate the server This error message indicates that the browser can't locate the server or that you incorrectly typed the URL. Look carefully at the server name in the URL and try retyping the URL.

You can't log on as an anonymous user This error message appears when you try to access certain FTP sites. It indicates that the site allows access only to registered members, or that the site allows access to only a limited number of non-members, in which case the site is simply busy. You can try to access the site again later, or if you're a registered member, try entering your user ID and password manually using an FTP software package.

This Web Site is proudly built upon an Open Source foundation:
Assembled with PHP Powered by Debian Linux Fueled by MySQL
Served by Apache

Home | Services | Support | Members | Software | Contact

MartNet - PO Box 42472 Philadelphia, PA 19101
Copyright 1996 - 2015 MartNet Communications LLC. All Rights Reserved.