Free content for your website or blog
Home About Us Article Writing Most Read Articles Authors Blog Wiki Contact Us
RSS Register Login
Topics
 
Home > Internet >

Top Five Most Common Dial-up Errors

Date Published: 28th September 2009
Bookmark and Share Republish Top Five Most Common Dial-up Errors
Author: Hannah Miller RSS Views: N/A PRINT ASK ABOUT THIS ARTICLE
Here are the top five dial-up errors you are most likely to encounter:

*680--This is a "no dial tone" error. It could mean several things. Either 1, you haven't plugged the phone cord into the back of the computer, 2, your phone line is dead, 3, your phone is off the hook or in use, 4, your phone cord is bad or too long (over 25 feet is not good and could be the problem), 5, your phone cord is plugged into an ethernet port or the "phone" extension next to the correct port (the phone extension is for a cord going to your telephone so you can use both with the same jack), or last of all, 6, there's something wrong with your modem. Luckily, this error is usually easy to fix, you just have to test these areas to see which one is causing the problem. If all else fails, in some rare cases, you must see a technician to repair your computer.


*691--Your username or password is invalid. This means either something is typed incorrectly, there's something wrong with the access number you're using or you account has been terminated, suspended, or withheld. If retyping your un and pw or recreating the connection does not resolve this, call your ISP. You probably just need to pay a bill or try some other troubleshooting tips.

*678--Your modem cannot establish a connection/there is no answer. One of the reason you might get this error is very easy to fix. Just check your access number. If you have invalid characters, and unnecessary (or missing) area code, extra numbers, or incorrect ordering in the "dial" field of your dial-up connection, you will get this error. Another common reason for this error is because there is something wrong with the connection and it needs to be recreated. You may also have a bad access number and need to try another one. Last of all, 678 can be from too much static on the phone line. You ISP can help you adjust modem settings and other tricks to help your modem weed through the static. If there is too much line noise, however, your phone lines may need to be repaired or replaced. If you can hear static on your phone line, call your phone company immediately because your ISP will probably not be able to help you.


*633--The modem is in use. Make sure you aren't already connected with another connection or that nothing else is using the internet connection. The easiest thing to do is restart you computer and the connections will automatically drop. You may need to reinstall your modem if the problem persists.

*692--You modem had a hardware failure. Check your phone and modem options to see what modems are installed and make sure it's the same one your using in your dial-up properties, if so, does it say "not presest" or "COM" and a number? Check the advanced tab in the modem properties and remove any extra initialization commands. You probably need to reinstall or replace the modem. Buying a new modem will probably cost less than the technician repair to fix your modem. In the long run, a new modem will probably be more worthwhile to you anyway.

Written by Hannah Miller, Director of Online Marketing and Customer Service Rep, Copper.net.

Copper.net is a provider of Columbus Ohio DSL and is all-American owned and operated. Call today, 1-800-336-3318 or sign up online. Check out my blog!http://www.copper.net/wire.
Tags: isp, rare cases, hook, weed, dial up connection, area code, dial tone
This article is free for republishing
Source: http://www.articlealley.com/article_1127033_81.html
Bookmark and Share Republish Top Five Most Common Dial-up Errors

Ask a Question About this Article

>> Please send me the possible reason for error code ...
>> I have a werfault.exe - Application error. The ...
>> We can learn a lot from dogs about how to live a good life
>> Visual C ++ runtime error
Powered by