DUNS ERROR 680
680 - There is no dial tone.
All versions of Windows -
No dial tone: There are many possible causes of a No Dial Tone Error.
First, try testing the modem's ability to detect dial tone and to dial by using HyperTerminal with the direct to COM port connect method - see Using HyperTerminal. If you give your modem an AT&FX1 command, and then a dial command, dial-tone detection will be disabled; if you still do not get dial tone, the modem may not be installed correctly (especially if it is a PCI or soft-modem); or the cable from the modem to the phone-line jack may be bad or installed in the wrong connector on the modem - try another line cord, and make sure you are plugged in to the LINE - not phone - jack on the modem. Plug a regular phone into the phone jack on the modem and make sure it has dial tone. The modem may also be defective. Many new modems come with an electronic circuit instead of the traditional electro-mechanical relay used to take the modem off-hook. Some of these designs are proving less reliable; often, they will be 'stuck' in the off-hook position, so unplugging, the plugging in the phone cord may give dial-tone. If this is the case, the modem needs repair or replacement.
If the modem will blind dial (x1), but not detect dial-tone otherwise, the problem is likely to be in the proper selection of the Country in Windows->ControlPanel->Telephony or in improper installation of the modem or lack of support for your country in the driver you are using. Check to see if there are updated drivers for your modem.
If the modem dials properly with detection (x3) in HyperTerminal, but does not detect dial tone when using DUNs, the problem may be DUNs (check for upgrade or re-install) or the proper setup and modem selection for the DUNs connectoid. See this page.
682 - ERROR WRITING SECTIONNAME
683 - ERROR WRITING DEVICETYPE
684 - ERROR WRITING DEVICENAME
685 - ERROR WRITING MAXCONNECTBPS
686 - ERROR WRITING MAXCARRIERBPS
687 - ERROR WRITING USAGE
DUNS ERROR 688 & 689
688 - ERROR WRITING DEFAULTOFF
689 - ERROR READING DEFAULTOFF
This error may occur due to a problem in your modem's .inf file. (The name of your modem .inf file can be obtained by examining your Modemlog.) This can be caused by the modem being installed with an incorrect .inf file, or the manufacturer may have a 'bug' in the .inf file.
Re-install the modem with the correct .inf file; or, load the existing .inf file in a text editor (like Notepad), and remove the lines containing
690 - ERROR EMPTY INI FILE
DUNS ERROR 691
691 - Access denied because username and/or password is invalid on the domain.
With all Windows versions - This error can occur if you use a bad username or password; remember in most instances the password is case-sensitive - you will not see the password, so if CAPS LOCK is not the way you expect it, you may have a problem with upper/lower-case. It may also occur if there is a problem with your service provider's access equipment, or on a 'bad' connection where the modem is retraining. Can also occur with incorrect Connectoid settings.
If you get this error the on a new account - you may not be using the correct username and/or password. Verify with your provider exactly what you need for username, and your password.
If this error persists, try dialing in to the server with Hyperterminal connected directly to modem. (Also see - Using Hyperterminal.) Nearly all servers will respond after CONNECT with a login prompt for your user name, and then password. This will allow you to see any error response from the server. If the server accepts your username and password, it should start a PPP session, and you cannot use Hyperterminal to get any further - you may see 'garbage' characters. If this happens, the username and password combination should work with DUNs. If you get an error, contact your service provider and have them try and log in with your account information.
This error may also occur even if you have entered the correct username and password if your Windows networking settings are incorrect. Make sure that 'Log on to Network' is not checked in your DUNS connectoid.
With Windows 98 - if you setup CompuServe from the Online Services Folder - See MS KB Q188120
WindowsXP - Problems caused by incorrect Connectoid settings - also see MS KB Q310431 and Q314445.
DUNS ERROR 692
692 - Hardware failure in port or attached device.
This error can occur if your modem is not properly installed, or for an external modem if the power to the modem is turned off. Verify the modem installation by checking Control Panel->Modems - driver and diagnostic (more info). The error can also be caused by a bad or loose serial cable with external modems.
This error can also occur if you have any service that gives a non-standard dial-tone such as telco-provided voice mail. The error can be avoided by adding commas before the number to dial.
This error can occur with Windows NT 4.0 if HyperTerminal already has the port in use. See this MS KB article.
With Windows 2000 or XP if you have Quicken 2000 installed: The error can be caused by the Quicken Download Manager; Removing the modem and re-installing it may result in the modem working - for a single session. The permanent solution is to remove Quicken 2000, or disable the Quicken Download Manager. This Intuit article explains how to turn off the Quicken Download Manager. The problem is also discussed in this Dell Solutions KB Article. Also see this Delltalk message.
With Windows-2000 and CompuServe or UUNET - see this MS KB article.
With Windows NT or 2000 and 3Com Impact ISDN Modem - you need an updated .inf file. See this MS KB article.
With Windows NT and USR Sportster ISDN Modem - you need updated driver. See this MS KB article.
With Windows NT and IBM MWave Modem when using Logon via DUNs option - an updated IBM driver may solve the problem, or log on first using a local account. See this MS KB article.
With IBM ValuePoint 466DX2 computers - a BIOS update may be required. See this MS KB article.
With Windows XP - See MS KB 314846 (modem malfunction, bad cable, port, or handshaking option problems.)
694 - ERROR DCB NOT FOUND
695 - ERROR STATE MACHINES NOT STARTED
696 - ERROR STATE MACHINES ALREADY STARTED
697 - ERROR PARTIAL RESPONSE LOOPING
698 - A response keyname in the device .INF file is not in the expected format.
699 - The device response caused buffer overflow.
700 - The expanded command in the device .INF file is too long.
701 - The device moved to a BPS rate not supported by the COM driver.
702 - Device response received when none expected.
703 - ERROR INTERACTIVE MODE
704 - ERROR BAD CALLBACK NUMBER
705 - ERROR INVALID AUTH STATE
706 - ERROR WRITING INITBPS
707 - X.25 diagnostic indication.
708 - The account has expired.
709 - Error changing password on domain.
710 - Serial overrun errors were detected while communicating with your modem.
No comments:
Post a Comment