DUNS ERROR 650, 651, 652
650 - The Remote Access server is not responding.
MSN - Modem not responding (Error 650).
All versions of Windows - if connecting to a WindowsNT server with PPTP. See MS KB Q162847
Error 650 can also occur if the ISP server modem/equipment is not set up properly.
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.
Prodigy (and some other) ISPs: Some ISPs require Client for Microsoft Networks installed and selected as your primary network logon. (Windows: Control Panel->Networking)
AOL on your system? If you have AOL installed on your system, but are not using AOL, the AOL software may interfere with access to any other ISP. Uninstall AOL. (Windows: Control Panel-> Add/Remove Programs)
MSN 2.52 - 2.6 - Can occur is DUNS is installed after MSN 2.52. See MS KB Q192420
Error 651 - Your modem (or other connecting device) has reported an error.
All versions of Windows - This error can occur if there is an error in the .inf file used to install the modem in Windows, or if the modem has been installed with the wrong .inf file. If this is the case, re-install the modem with the correct .inf file. Also see DataRace RediModem Error - MS KB Q122901 Evercom 24E+ Error MS KB Q122414
You can also test logging in with Hyperterminal (see above). Hyperterminal as described above operates independently of the modem's .inf file.
Error 652 - Unrecognized response from the device.
All versions of Windows - This error can occur if there is an error in the .inf file used to install the modem in Windows, or if the modem has been installed with the wrong .inf file. If this is the case, re-install the modem with the correct .inf file.
You can also test logging in with Hyperterminal (see above). Hyperterminal as described above operates independently of the modem's .inf file.
Windows NT 3.5, 3.51 - with certain MegaHertz Modems - See MS KB Q136034
Windows for Workgroups 3.11 - with MultiTech MT2834 Modem - See MS KB Q129426
653 - A macro required by the device was not found in the device .INF file section.
654 - A command or response in the device .INF file section refers to an undefined macro
655 - The
DUNS ERROR 656
656 - The
Check your Connectoid - make sure it is set properly and is set to use your installed modem. Check Modems on Control Panel and compare the name with that shown in the connectoid.
You may have incorrect drivers / .inf file installed for the modem. Check for the latest driver for your modem, remove and re-install.
If the error persists, remove and re-install Windows dial-up networking / remote access service (RAS).
DUNS ERROR 657, 659
657 - The device .INF file could not be opened.
659 - The media .INI file refers to an unknown device name.
Windows NT 4 - if using a script to connect and this error occurs, one or more of the RAS configuration files is missing or damaged. See MS KB Q156681
658 - The device name in the device .INF or media .INI file is too long.
660 - The device .INF file contains no responses for the command.
No comments:
Post a Comment