DUNS ERROR 661
661 - The device .INF file is missing a command.
Windows NT version 3.1 - This error can occur in any of the remote access .inf files listed below are edited or created with certain commands not in all uppercase:
Modem.inf
Pad.inf
Switch.inf
In particular, the commands: COMMAND and COMMAND_INIT must appear in all uppercase letters or this error may occur.
See MS KB 107061.
662 - Attempted to set a macro not listed in device .INF file section.
663 - The media .INI file refers to an unknown device type.
664 - Cannot allocate memory.
665 - The port is not configured for Remote Access.
DUNS ERROR 666
666 - Your modem (or other connecting device) is not functioning.
Applies to Windows 95 & 98:
The telephon.ini file in your \%systemroot%\ folder may be corrupted, missing or damaged. Locate and rename the telephon.ini file to telephon.old.
(%systemroot% is normally c:\windows.)
Re-start your computer and then run the tapiini.exe file located in the \windows\system folder.
Additional information on the telephon.ini file: MS KB Article 120221
DUNS ERROR 667, 668
667 - Cannot read the media .INI file.
All Versions of Windows - If you run software that removes a required registry entry, this error may occur. It has been documented to occur installing, then removing Planet Internet software with MSN. See MS KB Q155745
668 - The connection dropped.
Windows NT 3.1 - with Enter Manual Commands - See MS KB Q103499
669 - The usage parameter in the media .INI file is invalid.
670 - Cannot read the section name from the media .INI file.
671 - Cannot read the device type from the media .INI file.
672 - Cannot read the device name from the media .INI file.
673 - Cannot read the usage from the media .INI file.
674 - Cannot read the maximum connection BPS rate from the media .INI file.
675 - Cannot read the maximum carrier BPS rate from the media .INI file.
DUNS ERROR 676
676 - The line is busy.
All versions of Windows - This error can occur if:
· You are dialing the wrong number
· There is a problem at your ISP or in the telephone network
· You have voice-mail or other custom calling feature that produces a stutter dial-tone
· You haven't specified the proper country settings for your modem and the number you are dialing, or your modem doesn't support the country you are in.
· If you include the disable call waiting code in your dialing, and your phone line does not support call waiting; or, if you have call waiting, but your phone company doesn't support the disable call waiting code.
Check the settings for the DUNS Connectoid you are using.
If you have voice-mail or other custom-calling feature that produces stuttered dial-tone, you may be able to eliminate the problem by disabling dial-tone or busy detection: Add x to extra settings to disable busy and dial-tone detection; add x2 to extra settings to disable only busy detection.
If your modem doesn't offer support for your country, disabling dial-tone/busy detection (x in extra settings) might work (only if tone or pulse dialing for selected country is compatible with yours).
Use modem's speaker to listen to connection attempt: Make sure it dials, and make sure you do not hear a busy signal.
Examine Modemlog to see what number is actually being dialed. (If # dialed is not displayed, adding E1 to extra settings may help.)
Try dialing with pulse instead of tone; Try increasing the tone duration. [ s11=120 ]
Windows NT - Error 676 line busy is reported when you should receive a 'No Dial Tone' 680 error. This was first correct in SP6. See MS KB Q239870
Windows 98 - Depending upon the method you use to connect to your ISP, this error may occur even if you have configured automatic re-dial when the line is busy. See MS KB 187215.
677 - A person answered instead of a modem.
DUNS ERROR 678 & 679
678 - There is no answer.
679 - Cannot detect carrier.
All versions of Windows - This error can occur if:
You are dialing the wrong number
There is a problem at your ISP or in the telephone network
Your modem is unable to handshake with remote modem before allotted time
Use modem's speaker to listen to connection attempt: Make sure it dials, and make sure you hear remote modem answer tones.
Dial number with regular phone and make sure you hear remote modem answer tones.
Make sure correct phone # is dialed with DUNS - examine Modemlog. (If # dialed is not displayed, adding E1 to extra settings may help. Note also, you may have your telephony/connection settings such that long-distance digit is unintentionally being added to your phone number.)
No comments:
Post a Comment