Return Home

Ivy Web Host - Dialup Error Codes We recommend you save this page to the "My Documents" folder for future reference...even if you are offline or unable to connect. To do this Click "File" in the top left corner. Scroll down to and click on "Save As". When the box pops up click on "Save". This page will now be in "My Documents". You may get a warning window...just click OK or Yes to save this page. Below is a listing of Windows Dialup Errors (DUN) and the known fixes. If you get one of these error codes, try the fix before attempting to contact Tech Support. Scroll down and find the Error # you received and read how to fix the error. Error 0 - Connection Successful! 1. Don't "fix" this! ;) (This is the result sent to DUN/RAS when the connection succeeded.) Error 2 - The system cannot find the file specified 1. Reinstall NCP & DUN. Error 5 - Access Denied 1. Make sure the username and password are correct, with nothing in the "domain" field for NT/2k unless the user should have something there. 2. Make sure "accept any authentication including clear text" is dotted. Error 5 - Invalid Procedure Call 1. Reinstall all Dialup and Network components. Error 6 - Stack overflow 1. This is a memory issue, try rebooting the computer. A cold boot might be good in this instance. 2. If a reboot doesn't resolve it, this could be a RAM or Swap file issue. Error 20 - The system cannot find the device specified 1. Make sure the correct modem is selected. 2. Does the modem respond to diagnostics? It may need to be reinstalled. 3. Is RNAAPP loaded into memory after closing the dialer? If so try the RNAAPP fix. 4. Reinstall NCP/DUN/RAS. Error 71 - No more connections allowed 1. Is someone connected as you? Been giving out your password? 2. Were you disconnected all of a sudden before this happens? You could be 'ghosted' on the server. The ISP can usually "bump" the 'ghost' off through radius. Error 380 - Invalid Property Value 1. Make sure autodial is pointing to the correct dialer. 2. Recreate the dialer. Error 600 - An operation is pending 1. Reboot. 2. Make sure that there are no other dialers, fax software, or any other programs that use your modem running. 3. Press Ctrl-Alt-Delete, if you see RNAAPP loaded, then go to the RNAAPP fix page. Error 601 - The port handle is invalid 1. Press the "More Info.." button under Diagnostics while the modem's COM port is selected. If you get Ati# responses then you may just have to reboot, take out a bum init string, or type ATZ as the init. 2. If this does not work, or is not the case try reinstalling the modem. 3. Press Ctrl-Alt-Delete, if you see RNAAPP loaded, then go to the RNAAPP fix page. 4. Doesn't look like the modem is working. Refer to computer manufacturer. Error 602 - The port is already open 1. Reboot. 2. Uninstall and Reinstall the modem. 3. Make sure that no other programs are using your modem. Fax software, Supervoice, etc... 4. Ctrl-Alt-Delete, if you see RNAAPP loaded, then go to the RNAAPP fix page. Error 603 - Caller's buffer is too small 1. In the modem properties make sure that the port speed is not set too low. 2. Open up the "Port Settings" and make sure that FIFO's are on and not set too low. Try playing around with these settings until the error goes away. 3. Try uninstalling and reinstalling the modem. 4. Try uninstalling and reinstalling Dialup Networking and all its associated components. 5. Refer to computer manufacturer. Error 604 - Wrong information specified 1. Retype username and password. 2. Delete and remake the dialer. Error 605 - Cannot set port information 1. Delete and recreate the dialer. 2. Uninstall and reinstall the modem. 3. Uninstall and reinstall Dialup Networking and all of its associated components. 4. Refer to manufacturer. Error 606 - The port is not connected 1. Press the "More Info.." button under Diagnostics while the modem's COM port is selected. If you get Ati# responses then you may just have to reboot, take out a bum init string, or type ATZ as the init. 2. If this does not work, or is not the case try reinstalling the modem. 3. Press Ctrl-Alt-Delete, if you see RNAAPP loaded, then go to the RNAAPP fix page. 4. Doesn't look like the modem is working. Refer to computer manufacturer. Error 607 - The event is invalid 1. This error should not occur when dialing up to the internet. However, if it does take a look at the event log to see if you can figure out what happened. 2. Reboot and check all of the settings for the dialer/network. 3. Reinstall RAS/DUN. Error 608 - The device does not exist 1. Make sure that the correct modem is selected in the dialer. 2. Make sure (by looking at the modem diagnostics) that the correct modem drivers are being used. If not, find and install the correct drivers. 3. Uninstall and reinstall the dialer. 4. If this does not work, or is not the case try reinstalling the modem. 5. If the modem responds to diagnostics, and responds to ATZ in HyperTerminal, try uninstalling and reinstalling Dialup Networking. 6. Doesn't look like the modem is working. Refer to computer manufacturer. Error 609 - The device type does not exist 1. Make sure that the correct modem is selected in the dialer. 2. Make sure (by looking at the modem diagnostics) that the correct modem drivers are being used. If not, find and install the correct drivers. 3. Uninstall and reinstall the dialer. 4. If this does not work, or is not the case try reinstalling the modem. 5. If the modem responds to diagnostics, and responds to ATZ in HyperTerminal, try uninstalling and reinstalling Dialup Networking. 6. Doesn't look like the modem is working. Refer to computer manufacturer. Error 610 - The buffer is invalid 1. In the modem properties make sure that the port speed is not set too low. 2. Open up the "Port Settings" and make sure that FIFO's are on and not set too low. Try playing around with these settings until the error goes away. 3. Try uninstalling and reinstalling the modem. 4. Try uninstalling and reinstalling DUN/RAS and all its associated components. 5. Refer to computer manufacturer. Error 611 - The route is not available 1. Reboot. 2. Make sure that the dialer and network control panel configurations are valid. 3. Rip and reinstall the network components (unless the user is on a LAN, then have them talk to the sysadmin). 4. Refer to manufacturer/sysadmin. Error 612 - The route is not allocated 1. Reboot. 2. Make sure that the dialer and network control panel configurations are valid. 3. Rip and reinstall the network components (unless the user is on a LAN, then have them talk to the sysadmin). 4. Refer to manufacturer/sysadmin. Error 613 - Invalid compression specified 1. Reboot. 2. Try adding &K3 to the extra settings, if this doesn't work, try adding &K0. 3. Try reinstalling the modem. 4. Refer to manufacturer. Error 614 - Out of buffers 1. In the modem properties make sure that the port speed is not set too low. 2. Open up the "Port Settings" and make sure that FIFO's are on and not set too low. Try playing around with these settings until the error goes away. 3. Try uninstalling and reinstalling the modem. 4. Try uninstalling and reinstalling Dialup Networking and all its associated components. 5. Refer to computer manufacturer. More information on error 614 can be found at: http://support.microsoft.com/support/kb/articles/q123/5/97.asp Error 615 - The port was not found 1. Press the "More Info.." button under Diagnostics while the modem's COM port is selected. If you get Ati# responses then you may just have to reboot, take out a bum init string, or type ATZ as the init. 2. If this does not work, or is not the case try reinstalling the modem. 3. Press Ctrl-Alt-Delete, if you see RNAAPP loaded, then go to the RNAAPP fix page. 4. Doesn't look like the modem is working. Refer to computer manufacturer. Error 616 - An asynchronous request is pending 1. Reboot the machine. 2. Check settings (DUN/RAS, Network, etc) 3. Do a full reinstall of dialup related components. 4. If you are running Windows 2000 or NT check the event log for further details on this error. Error 617 - The port or device is already disconnecting 1. Wait for the modem to disconnect. 2. If it is taking too long, close RAS. 3. Still not working? Reboot the computer and it should work. Error 618 - The port is not open 1. Reboot. 2. Make sure that no other programs are using your modem. Fax software, Supervoice, etc... 3. Ctrl-Alt-Delete, if you see RNAAPP loaded, then go to the RNAAPP fix page. Error 619 - The port is disconnected 1. Reboot. 2. Make sure that no other programs are using your modem. Fax software, Supervoice, etc... 3. Ctrl-Alt-Delete, if you see RNAAPP loaded, then go to the RNAAPP fix page. Error 620 - There are no endpoints 1. Check dialer settings. 2. Is the user on a network? If not, check the network control panel and perhaps reinstall the components. 3. If the user is on a network have them contact their sysadmin and make sure that their network is configured to dial out. This is most likely a NetBIOS error. Error 621 - Cannot open the phone book file 1. Recreate connectoid. 2. Uninstall and reinstall DUN/RAS. Error 622 - Cannot load the phone book file 1. Recreate connectoid. 2. Uninstall and reinstall DUN/RAS. Error 623 - Cannot find the phone book entry 1. Delete and recreate connectoid (more like just a create in most cases, because there probably isn't a connectoid). Error 624 - Cannot write the phone book file 1. Make sure that RASPHONE.PBK is located in system32\RAS\. If so, rename the file and run RASPHONE.EXE. If not, then run RASPHONE.EXE. 2. Uninstall and reinstall DUN/RAS. Error 625 - Invalid information found in the phone book 1. Recreate the dialer. 2. Make sure that RASPHONE.PBK is located in system32\RAS\. If so, rename the file and run RASPHONE.EXE. If not, then run RASPHONE.EXE. 3. Uninstall and reinstall DUN/RAS. Error 626 - Cannot load a string 1. Reboot the machine. 2. Check settings (DUN/RAS, Network, etc) 3. Do a full reinstall of dialup related components. 4. If you are running Windows 2000 or NT check the event log for further details on this error. Error 627 - Cannot find key 1. Recreate connectoid. 2. Uninstall and reinstall DUN. Error 628 - The port was disconnected 1. Make a run through and check all of the dialup/network settings. 2. This is most likely a modem/line noise issue. Check for modem driver updates and try init strings from this page. 3. Check into line noise. Error 629 - The port was disconnected by the remote machine 1. Does it ask for the UN/PASS more than once? if so, verify UN/PASS. 2. Check the dialer settings, if ipx/spx is checked and not tcp/ip this would be the cause. In any case the only two things that should be checked are Enable Software Compression and TCP/IP. Also enable DNS. Logon to Network being checked can very well be the culprit. 3. Make sure that the Microsoft VPN Adapter is not selected under connect using. 4. Recreate the dialer. 5. Windows NT? In the Security Tab in Phonebook, make sure that "accept any authentication including clear text" is checked. 6. Check the Network Control Panel settings. 7. Reboot the machine. 8. Modem issue? Use this page for driver updates/init strings.. 9. Try disconnecting any phones, caller ID boxes, answering machines, line splitters from line. Plug modem directly into the line. Try using a different phone cord between modem and phone socket. Check for line noise. More info on Error 629 can be found here: http://members.tripod.com/paltech/error629.htm and here: http://support.microsoft.com/support/kb/articles/q190/5/54.asp Error 630 - The port was disconnected due to hardware failure 1. Is it a Laptop? Try Plugging the PCMCIA Card into a different slot. 2. Is correct modem selected in the connectoid? Select the correct modem. 3. Try rebooting the computer. 4. Does the modem respond to diagnostics? If not, uninstall and reinstall it. 5. If so, by looking at the Ati's does it look like the correct modem is setup? 6. Try uninstalling and reinstalling the modem anyways. 7. Try an init string. Lower the fifo buffers. Is it a NON-winmodem? If so, check required to connect under error control. 8. Update the modem drivers. Try init strings. 9. Check into line noise. 10. Refer to manufacturer. More info on error 630 can be found at: http://www.deja.com/[ST_rn=qs]/qs.xp?QRY=microsoft+error+630&OP=dnquery.xp&ST=QS&DBS=2 and at: http://members.tripod.com/paltech/error630.htm and at: http://support.microsoft.com/support/kb/articles/q190/5/54.asp Error 631 - The port was disconnected by the user 1. Make sure the user is dialing the correct number. Do they need to dial the area code, or a dial prefix? Are they disabling call waiting but do not have call waiting? 2. Most likely they just disconnected themselves. Tell them not to cancel the dialing? Reboot the machine. Error 632 - The structure size is incorrect 1. Reboot the machine. 2. Check settings (DUN/RAS, Network, etc) 3. Do a full reinstall of dialup related components. 4. If you are running Windows 2000 or NT check the event log for further details on this error. Error 633 - The port is already in use or is not configured for Remote Access dialout 1. Click Start, goto find, and click files or folders. 2. Search for telephon.ini. 3. If you find it then rename it to telephon.old or telephon.bad. 4. Click on Start, Run, then type tapiini.exe, press Enter. 5. Reboot. 6. It is also possible that the modem is not setup correctly. Check the modem and possibly Uninstall and reinstall it. 7. Try uninstalling and reinstalling the Dial Up Adapter. 8. Make sure that no other programs are using your modem. Fax software, Supervoice, etc... 9. Ctrl-Alt-Delete, if you see RNAAPP loaded, then go to the RNAAPP fix page. More info on error 633 can be found at: http://www.deja.com/[ST_rn=qs]/qs.xp?QRY=microsoft+error+633&OP=dnquery.xp&ST=QS&DBS=2 Error 634 - The port is already in use or is not configured for Remote Access dialout 1. Your computer name was unable to register on the network. If you are not on a network check your network settings, perhaps change your computer name. Reinstall the network control panel. 2. You are on a network? Contact your network administrator. Error 635 - Unknown error 1. This is an unknown error. There are several different causes for this error. Just check all their settings and make sure they are correct. Check the connectoid, network, and see if they have a problem modem or not. 2. If it is a modem with known issues, try updating the drivers/init strings. 3. Reinstall DUN/RAS and all associated components. 4. Check into line noise. Error 636 - The wrong device is attached to the port 1. The wrong modem is selected in the dialer. Select the correct modem. 2. If this is not the case, try reinstalling the modem. Error 637 - The string could not be converted 1. Reboot the machine. 2. Check settings (DUN/RAS, Network, etc) 3. Do a full reinstall of dialup related components. 4. If you are running Windows 2000 or NT check the event log for further details on this error. Error 638 - The request has timed out 1. Reboot the machine. 2. Check settings (DUN/RAS, Network, etc) 3. Do a full reinstall of dialup related components. 4. If you are running Windows 2000 or NT check the event log for further details on this error. Error 639 - No asynchronous net available 1. Check dialer settings. 2. Is the user on a network? If not, check the network control panel and perhaps reinstall the components. 3. If the user is on a network have them contact their sysadmin and make sure that their network is configured to dial out. This is most likely a NetBIOS error. Error 640 - A NetBIOS error has occurred 1. Check dialer settings. 2. Is the user on a network? If not, check the network control panel and perhaps reinstall the components. 3. If the user is on a network have them contact their sysadmin and make sure that their network is configured to dial out. Error 641 - The server cannot allocate NetBIOS resources needed to support the client 1. Check dialer settings. 2. Is the user on a network? If not, check the network control panel and perhaps reinstall the components. 3. If the user is on a network have them contact their sysadmin and make sure that their network is configured to dial out. Error 642 - One of your NetBIOS names is already registered on the remote network 1. Check dialer settings. 2. Is the user on a network? If not, check the network control panel and perhaps reinstall the components. 3. If the user is on a network have them contact their sysadmin and make sure that their network is configured to dial out and to check into another computer using the same computer name on the network. 4. If the user is the LAN/sysadmin then try changing the computer name. Error 643 - A network adapter at the server failed 1. Check dialer settings and make sure they are dialing the correct number. 2. Is the user on a network? If not, check the network control panel and perhaps reinstall the components. 3. If the user is on a network have them contact their sysadmin and make sure that their network is configured to dial out. Error 644 - You will not receive network message popups 1. Check dialer settings. Make sure the correct number is being dialed. 2. If you are not on a network then check your network settings. 3. If you are on a network, contact your sysadmin. Someone else on the network is using your messaging name and you will not receive message popups. Error 645 - Internal authentication error 1. Check the connectoid, is require encrypted password checked under the Server Types tab? Uncheck it. 2. Uninstall and reinstall the Dial Up adapter. 3. Recreate the Dialer. 4. Check for extra winsock.dll's and wsock32.dll's. 5. Is VPN installed? If they do not use it get rid of it. 6. Try inits. 7. Uninstall and reinstall network. 8. Nuke the pwl files. 9. Try resetting their password on the server side. 10. Full internet Uninstall and reinstall. (DUN, connectoid, pwl files, and network) 11. Is it a laptop? Try moving the PCMCIA card to another slot. More info on error 645 can be found at: http://www.deja.com/[ST_rn=qs]/qs.xp?QRY=microsoft+error+645&OP=dnquery.xp&ST=QS&DBS=2 Error 646 - The account is not permitted to log on at this time of day 1. This happens when the user dials into an NT server. If you are using an NT server, then perhaps you should allow them to login at that time of day. If not, make sure they are dialing the correct phone number. 2. Recreate the connectoid. Perhaps reset their password. Error 647- The account is disabled 1. This happens when the user dials into an NT server. If you are using an NT server, then perhaps you should allow them to login. If not, make sure they are dialing the correct phone number. 2. Recreate the connectoid. Perhaps reset their password. Error 648 - The password has expired 1. This happens when the user dials into an NT server. If you are using an NT server, then perhaps you should allow them to login. If not, make sure they are dialing the correct phone number. 2. Recreate the connectoid. Perhaps reset their password. Error 649 - The account does not have Remote Access permission 1. This happens when the user dials into an NT server. If you are using an NT server, then perhaps you should allow them to login. If not, make sure they are dialing the correct phone number. 2. Recreate the connectoid. Perhaps reset their password. Error 650 - The Remote Access server is not responding 1. This is probably a modem error. In any case, check the connectoid and Network settings. If they look good then... 2. Make sure modem is setup properly, try inits, check for updated drivers. 3. Lower the Fifo buffers. Lower port speed to 57600, making sure the checkbox to 'only connect at this speed' is unchecked. 4.1 Click Start, goto find, and click files or folders. 4.2 Search for telephon.ini. 4.3 If you find it then rename it to telephon.old or telephon.bad. 4.4 Click on Start, Run, then type tapiini.exe, press Enter. 4.5 Reboot. 5. Check into line noise. More info on error 650 can be found at: http://members.tripod.com/paltech/error650.htm and at: http://x22.deja.com/[ST_rn=qs]/qs.xp?QRY=microsoft+error+650&OP=dnquery.xp&ST=QS&DBS=2 and at: http://support.microsoft.com/support/kb/articles/q162/8/47.asp Error 651 - Your modem (or other connecting device) has reported an error 1. If the modem is not dialing and trying to establish a connection then check to make sure that the modem is installed properly and responds to diagnostics. 1a) Make sure that no other programs are using your modem. Fax software, Supervoice, etc... 1b) Ctrl-Alt-Delete, if you see RNAAPP loaded, then go to the RNAAPP fix page. 2. If the modem is dialing and trying to establish a connection then try modem driver updates/init strings after checking all of the user's settings. 3. Do a full internet (DUN, Network, dialers, pwl's, etc..) uninstall and reinstall. 4. Check into line noise. Error 652 - Unrecognized response from the device 1. If the modem is not dialing and trying to establish a connection then check to make sure that the modem is installed properly and responds to diagnostics. 1a) Uninstall and reinstall the modem. 1b) Make sure that no other programs are using your modem. Fax software, Supervoice, etc... 1c) Ctrl-Alt-Delete, if you see RNAAPP loaded, then go to the RNAAPP fix page. 2. If the modem is dialing and trying to establish a connection then try modem driver updates/init strings after checking all of the user's settings. 2a) Make sure that no other programs are using your modem. Fax software, Supervoice, etc... 2b) Ctrl-Alt-Delete, if you see RNAAPP loaded, then go to the RNAAPP fix page. 3. Do a full internet (DUN, Network, dialers, pwl's, etc..) uninstall and reinstall. 4. Check into line noise. Error 653 - A macro required by the device was not found in the device .INF file section 1. Make sure the modem is using correct drivers for the computer's operating system (most likely NT). Try reinstalling the modem. 2. Reinstall RAS/DUN. Error 654 - A command or response in the device .INF file section refers to an undefined macro 1. Make sure that no unneeded scripts are being used. 2. Make sure the modem is using correct drivers for the computer's operating system (most likely NT). Try reinstalling the modem. 3. Reinstall RAS/DUN. Error 655 - The macro was not found in the device .INF file section 1. Make sure the modem is using correct drivers for the computer's operating system (most likely NT). Try reinstalling the modem. 2. Reinstall RAS/DUN. Error 656 - The macro in the device .INF file section contains an undefined macro 1. Make sure the modem is using correct drivers for the computer's operating system (most likely NT). Try reinstalling the modem. 2. Reinstall RAS/DUN. Error 657 - The device .INF file could not be opened 1. Make sure the correct modem is selected in the dialer. 2. Reinstall the modem. 3. Full uninstall and reinstall of DUN/RAS and its associated components. 4. Refer to manufacturer. Most likely a modem software issue. Error 658 - The device name in the device .INF or media .INI file is too long 1. Make sure the correct modem is selected in the dialer. 2. Reinstall the modem. 3. Full uninstall and reinstall of DUN/RAS and its associated components. 4. Refer to manufacturer. Most likely a modem software issue. Error 659 - The media .INI file refers to an unknown device name 1. Make sure the modem is using correct drivers for the computer's operating system (most likely NT). Try reinstalling the modem. 2. Reinstall RAS/DUN. Error 660 - The device .INF file contains no responses for the command 1. Make sure the correct modem is selected in the dialer. 2. Reinstall the modem. 3. Full uninstall and reinstall of DUN/RAS and its associated components. 4. Refer to manufacturer. Most likely a modem software issue. Error 661 - The device .INF file is missing a command 1. Make sure the correct modem is selected in the dialer. 2. Reinstall the modem. 3. Full uninstall and reinstall of DUN/RAS and its associated components. 4. Refer to manufacturer. Most likely a modem software issue. Error 662 - Attempted to set a macro not listed in device .INF file section 1. Make sure the modem is using correct drivers for the computer's operating system (most likely NT). Try reinstalling the modem. 2. Reinstall RAS/DUN. Error 663 - The media .INI file refers to an unknown device type 1. Make sure the correct modem is selected in the dialer. 2. Reinstall the modem. 3. Full uninstall and reinstall of DUN/RAS and its associated components. 4. Refer to manufacturer. Most likely a modem software issue. Error 664 - Cannot allocate memory 1. System resources have run out. Try a reboot. 2. Make sure that the computer has enough RAM to run windows. If so, check the system resources, are the still high? If they are then try a full uninstall and reinstall of DUN/RAS. If they are low, then have user look into a RAM upgrade or getting rid of some of the startup items. Error 665 - The port is not configured for Remote Access 1. Reboot. 2. Make sure that no other programs are using your modem. Fax software, Supervoice, etc... 3. Ctrl-Alt-Delete, if you see RNAAPP loaded, then go to the RNAAPP fix page. Error 666 - Your modem (or other connecting device) is not functioning 1. Check to make sure the correct modem is selected in the dialer. 2. Make sure there are not multiple modems installed. 3. Uninstall and reinstall the modem. 4. Make sure that no other programs are using your modem. Fax software, Supervoice, etc... 5. Ctrl-Alt-Delete, if you see RNAAPP loaded, then go to the RNAAPP fix page. 6. Send to manufacturer? Error 667 - Cannot read the media .INI file 1. Uninstall and reinstall Network, connectoid, and DUN. 2. Check for multiple copies of iexplore.exe, rename any extra copies that you find. 3. Make sure the correct modem is selected in the dialer. 4. Reinstall the modem. 5. Send to manufacturer. Error 668 - The connection dropped 1. Make sure they are typing in the username and password correctly. 2. Make sure dialer and network control panel settings are correct. 3. Recreate dialer. 4. Update modem drivers, try inits and commas, etc... Error 669 - The usage parameter in the media .INI file is invalid 1. Make sure the modem is using correct drivers for the computer's operating system (most likely NT). Try reinstalling the modem. 2. Reinstall RAS/DUN. Error 670 - Cannot read the section name from the media .INI file 1. Make sure the modem is using correct drivers for the computer's operating system (most likely NT). Try reinstalling the modem. 2. Reinstall RAS/DUN. Error 671 - Cannot read the device type from the media .INI file 1. Make sure the modem is using correct drivers for the computer's operating system (most likely NT). Try reinstalling the modem. 2. Reinstall RAS/DUN. Error 672 - Cannot read the device name from the media .INI file 1. Make sure the modem is using correct drivers for the computer's operating system (most likely NT). Try reinstalling the modem. 2. Reinstall RAS/DUN. Error 673 - Cannot read the usage from the media .INI file 1. Make sure the modem is using correct drivers for the computer's operating system (most likely NT). Try reinstalling the modem. 2. Reinstall RAS/DUN. Error 674 - Cannot read the maximum connection BPS rate from the media .INI file 1. Make sure the modem is using correct drivers for the computer's operating system (most likely NT). Try reinstalling the modem. 2. Reinstall RAS/DUN. Error 675 - Cannot read the maximum carrier BPS rate from the media .INI file 1. Make sure the modem is using correct drivers for the computer's operating system (most likely NT). Try reinstalling the modem. 2. Reinstall RAS/DUN. Error 676 - The line is busy 1. Make sure the number they are dialing into is correct. Check dial prefixes, long distance, etc. 2. If they get a modem tone it may be a modem issue. Check for updated drivers and try inits. 3. Try the number, is it busy? Is there a POP problem? 4. Is RNAAPP getting stuck? If so, refer to the RNAAPP! help page. To find type in web search box, "RNAAPP". Error 677 - A person answered instead of a modem 1. Make sure that they are dialing the correct number. This includes if they should or shouldn't dial the area code, a 9, etc... 2. Are they hearing a voice? Not hearing a modem tone? Make sure that the POP isn't having any sort of issues. 3. If they hear a connection sound, try R&Ring the modem, updating drivers, inits, ATZX0(reset and blind dial) as an init, etc... Error 678 - There is no answer 1. Is there a handshake? If not the phone number is probably wrong in some way. Are they trying to turn off call waiting the wrong way for their telco? Do they have call waiting? Do they have pulse but are trying to dial tone? Etc... 2. If there is a handshake check their connectoid and network settings. If all looks good it is probably a handshake error. Make sure the correct modem is selected and setup. 3. Try upgrading the firmware. To get them on the net in the meantime try lowering the fifo buffers, setting the max speed to 57600, and adding an init string. Try an init that will retain v90 first, but if they just want to get on and download their drivers try setting v34. Uninstalling and reinstalling the modem can sometimes help as well. Error 679 - Cannot detect carrier 1. Make sure that they are dialing the correct number. This includes if they should or shouldn't dial the area code, a 9, etc... 2. If they hear a modem tone then try driver upgrades, inits, add &C0 (carrier detect always on), etc... 3. Make sure that no other programs are using your modem. Fax software, Supervoice, etc... 4. Ctrl-Alt-Delete, if you see RNAAPP loaded, then go to the RNAAPP fix page. To find, type in a web search "RNAAPP". 5. Check into line noise. Perhaps do a full internet uninstall and reinstall first to make sure you eliminate any errors that might be on their machine. Error 680 - There is no dial tone 1. Make sure that the modem is installed and the phone line is running to the modem correctly. 2. Is the dialer pointing to the correct modem? 3. Make sure that no other programs are using your modem. Fax software, Supervoice, etc... 4. Ctrl-Alt-Delete, if you see RNAAPP loaded, then go to the RNAAPP fix page. 5. Try uninstalling and reinstalling the modem. Make sure that they can hear a dialtone through the modem (with a handset). Could be a modem problem. If they don't hear a dialtone it could also be a line, jack, or general telco problem. More info on error 680 can be found at: http://php.iupui.edu/~aamjohns/trouble.html#No Dial Tone Error 681 - General error reported by device 1. Make sure the correct modem is selected in the dialer. 2. Reinstall the modem. 3. Full uninstall and reinstall of DUN/RAS and its associated components. 4. Try driver upgrades/inits. Check into line noise. 4. Refer to manufacturer. Most likely a modem issue of some sort. Error 685 - ERROR WRITING MAXCONNECTBPS 1. Uncheck the "Connect only at this speed" box under the port speed box and set the port speed to 38400 if they have a 33.6 or lower, and 57600 if they have a 56k modem. 2. Try a reboot 3. Uninstall and reinstall the modem. Error 690 - ERROR EMPTY INI FILE 1. Make sure the correct modem is selected in the dialer. 2. Reinstall the modem. 3. Full uninstall and reinstall of DUN/RAS and its associated components. 4. Refer to manufacturer. Most likely a modem software issue. Error 691 - Access denied because username and/or password is invalid on the domain 1. Verify the UN and PASS is correct. Correct case, correct spacing, just plain correct, and correct realms if the site requires realms authentication. 2. Make sure that they are supposed to be using realms auth and are using/not using it correctly. 3. If this is Windows NT, make sure that nothing is typed in the DOMAIN field of the username/password/domain box. 4. Make sure that logon to network is not checked in the connectoid properties. 5. Reboot the computer and try again. 6. Delete all of the pwl files and reboot. ****[THE FOLLOWING IS DONE AT YOUR OWN RISK]**** 7. Start -> Run -> REGEDIT, DisablePwdCaching string value in the following registry key: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\ Policies\Network If password caching is disabled, the DisablePwdCaching string value has a value data of 1. To enable password caching, change the value data to "0" (without quotation marks). If the DisablePwdCaching value does not exist, add this value with a data value of 0 to the registry key listed above. The DisablePwdCaching key is case sensitive. More info on error 691 can be found at: http://members.tripod.com/paltech/error691.html Error 692 - Hardware failure in port or attached device 1. Check to make sure the correct modem is selected in the dialer. 2. Make sure there are not multiple modems installed. 3. Uninstall and reinstall the modem. 4. Make sure that no other programs are using your modem. Fax software, Supervoice, etc... 5. Ctrl-Alt-Delete, if you see RNAAPP loaded, then go to the RNAAPP fix page. 6. Send to manufacturer? Error 693 - ERROR NOT BINARY MACRO 1. Make sure the modem is using correct drivers for the computer's operating system (most likely NT). Try reinstalling the modem. 2. Make sure that the files PAD.INF, MODEM.INF, and SWITCH.INF in C:\SYSTEM32\RAS are not marked as read-only and the currently logged on user does have write permissions. 3. Reinstall RAS/DUN. Error 695 - ERROR STATE MACHINES NOT STARTED 1. Uninstall and reinstall dialer, network, and DUN. 2. Send to manufacturer. Error 697 - ERROR PARTIAL RESPONSE LOOPING 1. Reboot the machine. 2. Check settings (DUN/RAS, Network, etc) 3. Do a full reinstall of dialup related components. 4. If you are running Windows 2000 or NT check the event log for further details on this error. Error 698 - A response keyname in the device .INF file is not in the expected format 1. Make sure the modem is using correct drivers for the computer's operating system (most likely NT). Try reinstalling the modem. 2. Make sure that the files PAD.INF, MODEM.INF, and SWITCH.INF in C:\SYSTEM32\RAS are not marked as read-only and the currently logged on user does have write permissions. 3. Reinstall RAS/DUN. Error 699 - The device response caused buffer overflow 1. In the modem properties make sure that the port speed is not set too low. 2. Open up the "Port Settings" and make sure that FIFO's are on and not set too low. Try playing around with these settings until the error goes away. 3. Try uninstalling and reinstalling the modem. 4. Try uninstalling and reinstalling Dialup Networking and all its associated components. 5. Refer to computer manufacturer. Error 700 - The expanded command in the device .INF file is too long 1. Most likely one of the .INF or scripts has a line or command that is greater than 256 characters. This line/command will have to be broken up into multiple commands. Error 701 - The device moved to a BPS rate not supported by the COM driver 1. Odd error. Try lowering the port speed and restricting the connect speed a bit with an init string. Could be a COM port or serial port problem. Error 702 - Device response received when none expected 1. Make sure the modem is using correct drivers for the computer's operating system (most likely NT). Try reinstalling the modem. 2. Make sure that the files PAD.INF, MODEM.INF, and SWITCH.INF in C:\SYSTEM32\RAS are not marked as read-only and the currently logged on user does have write permissions. 3. Reinstall RAS/DUN. Error 703 - ERROR INTERACTIVE MODE 1. A dbcc checkcatalog attempted on a database which has many objects (for example, over 640 tables) may get a 703 error message. Thusly, the memory request failed because more than 64 pages are required to run the query in its present form. The query should be broken up into shorter queries if possible. To fix this execute master..CatalogCheck and key in the following script into a file named NEWCATCK.SQL and execute it: isql /Usa /P /S /e /inewcatck.sql /onewcatck.rpt The script is: create procedure CatalogCheck as /* Check syscolumns <---> sysobjects on "id" */ if exists (select * from syscolumns where id not in (select id from sysobjects)) print "A column exists in syscolumns with no associated object in sysobjects" /* Check syscolumns <---> systypes on "usertype" */ if exists (select * from syscolumns where usertype not in (select usertype from systypes)) print "A column exists in syscolumns with no associated type in systypes" * Check sysobjects <---> syscolumns on "id" for views */ if exists (select * from sysobjects where type in ('v', 'V') and id not in (select id from syscolumns)) print "A view exists in sysobjects with no columns in syscolumns" /* Check sysobjects <---> sysprocedures on "id" for views */ if exists (select * from sysobjects where type in ('v', 'V') and id not in (select id from sysprocedures)) print "A view exists in sysobjects with no entry in sysprocedures" /* Check sysobjects <---> sysprocedures on "id" for procedures */ if exists (select * from sysobjects where type in ('p', 'P') and id not in (select id from sysprocedures)) print "A procedure exists in sysobjects with no entry in sysprocedures" /* Check sysobjects <---> sysprocedures on "id" for rules & defaults */ if exists (select * from sysobjects where type in ('d', 'D', 'r', 'R') and id not in (select id from sysprocedures)) print "A rule and/or default exists in sysobjects with no entry in sysprocedures" /* Check sysobjects <---> syscolumns on "id" for tables */ if exists (select * from sysobjects where type in ('s', 'S', 'u', 'U') and id not in (select id from syscolumns)) print "A table exists in sysobjects with no entry in syscolumns" /* Check sysobjects <---> sysindexes on "id" for tables */ if exists (select * from sysobjects where type in ('s', 'S', 'u', 'U') and id not in (select id from sysindexes)) print "A table exists in sysobjects with no entry in sysindexes" /* Check sysindexes <---> sysobjects on "id" */ if exists (select * from sysindexes where id not in (select id from sysobjects)) print "An entry exists in sysindexes with no entry in sysobjects" /* Check sysindexes <---> syssegments on "segment" */ if exists (select * from sysindexes where segment not in (select segment from syssegments)) print "An entry in sysindexes has a 'segment' value with no entry in syssegments" /* Check sysprocedures <---> sysobjects on "id" */ if exists (select * from sysprocedures where id not in (select id from sysobjects)) print "An entry exists in sysprocedures with no entry in sysobjects" print "Catalog Check complete" go More info on error 703 can be found at: http://support.microsoft.com/support/kb/articles/q88/6/85.asp Error 704 - ERROR BAD CALLBACK NUMBER 1. This happens when the user dials into an NT server. If you are using an NT server, then perhaps you should allow them to login at that time of day. If not, make sure they are dialing the correct phone number. 2. Recreate the connectoid. Error 705 - ERROR INVALID AUTH STATE 1. Reboot the machine. 2. Check settings (DUN/RAS, Network, etc) 3. Make sure that the user is typing in the proper username and password (and make sure nothing is under the Domain section in winNT/2k, unless there is supposed to be) 4. In Win9x/ME make sure that secure pass isn't checked under server types, and in Win2k/NT make sure that accept any auth including clear text is dotted. 5. Do a full reinstall of dialup related components. 6. If you are running Windows 2000 or NT check the event log for further details on this error. Error 707 - X.25 diagnostic indication 1. Clear out the X.25 tab in the windows NT phone book entry's properties. Set it to none. (Unless the user has an X.25 provider, in which case have them contact the provider for diagnostic information.) Error 708 - The account has expired 1. This happens when the user dials into an NT server. If you are using an NT server, then perhaps you should allow them to login at that time of day. If not, make sure they are dialing the correct phone number. 2. Recreate the connectoid. Perhaps reset their password on the server side. Error 709 - Error changing password on domain 1. This happens when the user dials into an NT server. If you are using an NT server, then perhaps you should allow them to login at that time of day. If not, make sure they are dialing the correct phone number. 2. Recreate the connectoid. Perhaps reset their password on the server side. Error 710 - Serial overrun errors were detected while communicating with your modem 1. This is probably a modem error. In any case, check the connectoid and Network settings. If they look good then... 2. Make sure modem is setup properly, try inits, check for updated drivers. 3. Lower the Fifo buffers. Try limiting the connect speed. 4. Check into line noise. Error 711 - RasMan initialization failure. Check the event log 1. Check the event log to see if that actually tells you what the problem is. 2. Reboot. 3. Uninstall and reinstall RAS. Error 712 - Biplex port is initializing. Wait a few seconds and redial 1. Reboot. Wait a few moments. Try again. 2. Uninstall and reinstall the modem. 3. Uninstall and reinstall RAS/DUN. Error 713 - No active ISDN lines are available 1. Are they using ISDN? If so, are they setup properly on both user and server sides? If not, see if they are setup improperly for regular dialup. 2. Check their ISDN line, make sure all devices are hung up and the modem/TA is hooked up properly. 3. Have the telco check the line. Error 714 - Not enough ISDN channels are available to make the call 1. Are they using ISDN? If so, are they setup properly on both user and server sides? If not, see if they are setup improperly for regular dialup. 2. Check their ISDN line, make sure all devices are hung up and the modem/TA is hooked up properly. 3. Have the telco check the line. Error 715 - Too many errors occurred because of poor phone line quality 1. Make sure no devices are connected to the line. Try another piece of phone cord. 2. Try modem driver updates and inits. 3. Get a line noise test done. Error 716 - The Remote Access IP configuration is unusable 1. Make sure that the dialer is configured correctly. If so, recreate the dialer. 2. Check network settings, make sure bindings are correct. 3. Try reinstalling RAS/DUN. Error 717 - No IP addresses are available in the static pool of Remote Access IP addresses 1. This happens when the user dials into an NT server. If you are using an NT server, then perhaps you should allow them to login at that time of day. If not, make sure they are dialing the correct phone number. 2. Recreate the connectoid. Perhaps make sure that they do not have a static IP specified, or if they are supposed to and do, make sure their static IP is not in use. Error 718 - PPP timeout 1. Reboot the machine, verify your Username and Password, and try again. Check for realms, if in NT make sure you have nothing under domain, accept any auth including clear text is checked, and try unchecking Enable PPP LCP extensions. Make sure logon to network isn't checked. Make sure that nothing is typed in the DOMAIN field if this is NT. 2. This is often a POP problem. Try logging onto a different POP. 718 is usually on the ISP's end, but NOT ALWAYS. If there are multiple calls coming into the ISP's callcenter then they could see a problem, but if not, it is probably the user's computer. 3. Nuke the pwl files. 4. Have ISP reset the password. 5. Recreate connectoid. 6. Full uninstall and reinstall of connectoid, network, and DUN/RAS. 7. This can sometimes also be a communications problem caused by heavy line noise or modem problems. Try updating the modem drivers, inits, commas, etc...and have a line noise test performed. More info on error 718 can be found at: http://www.deja.com/[ST_rn=qs]/qs.xp?QRY=microsoft+718&OP=dnquery.xp&ST=QS&DBS=2 Error 719 - PPP terminated by remote machine 1. Reboot the machine, verify your Username and Password, and try again. Check for realms, if in NT make sure you have nothing under domain, accept any auth including clear text is checked, and try unchecking Enable PPP LCP extensions. Make sure logon to network isn't checked. Make sure that nothing is typed in the DOMAIN field if this is NT. 2. This is often a POP problem. Try logging onto a different POP. 718 is usually on the ISP's end, but NOT ALWAYS. If there are multiple calls coming into the ISP's callcenter then they could see a problem, but if not, it is probably the user's computer. 3. Nuke the pwl files. 4. Have ISP reset the password. 5. Recreate connectoid. 6. Full uninstall and reinstall of connectoid, network, and DUN/RAS. 7. This can sometimes also be a communications problem caused by heavy line noise or modem problems. Try updating the modem drivers, inits, commas, etc...and have a line noise test performed. Error 720 - No PPP control protocols configured 1. Uninstall and Reinstall dialer, network, and DUN. 2. If NT: Try installing the Netbios interface service. 3. If NT: Try reinstalling the service pack. 4. Refer to manufacturer. Error 721 - Remote PPP peer is not responding 1. Reboot the machine, verify your Username and Password, and try again. Check for realms, if in NT make sure you have nothing under domain, accept any auth including clear text is checked, and try unchecking Enable PPP LCP extensions. Make sure logon to network isn't checked. Make sure that nothing is typed in the DOMAIN field if this is NT. 2. This is often a POP problem. Try logging onto a different POP. 718 is usually on the ISP's end, but NOT ALWAYS. If there are multiple calls coming into the ISP's callcenter then they could see a problem, but if not, it is probably the user's computer. 3. Nuke the pwl files. 4. Have ISP reset the password. 5. Recreate connectoid. 6. Full uninstall and reinstall of connectoid, network, and DUN/RAS. 7. This can sometimes also be a communications problem caused by heavy line noise or modem problems. Try updating the modem drivers, inits, commas, etc...and have a line noise test performed. Error 722 - The PPP packet is invalid 1. Reboot the machine. 2. If it happens again try reinstalling DUN/RAS. Error 723 - The phone number, including prefix and suffix, is too long 1. Check the phone number. Make sure that it is correct, including area code(if needed or not there if not needed), dialing a 9, call waiting, etc.. 2. Check to see if the dialer is setup to use a calling card. 3. Try recreating the dialer. Error 724 - The IPX protocol cannot dial-out on the port because the computer is an IPX router 1. IPX? You aren't supposed to dial internet service with IPX. Check their settings and make sure they are using TCP/IP, not IPX/SPX. 2. Perhaps they are trying to use VPN? Might want to disable that. Error 725 - The IPX protocol cannot dial-in on the port because the IPX router is not installed 1. IPX? You aren't supposed to dial internet service with IPX. Check their settings and make sure they are using TCP/IP, not IPX/SPX. 2. Perhaps they are trying to use VPN? Might want to disable that. Error 726 - The IPX protocol cannot be used for dial-out on more than one port at a time 1. IPX? You aren't supposed to dial internet service with IPX. Check their settings and make sure they are using TCP/IP, not IPX/SPX. 2. Also, are they trying to dialup more than once? 3. Perhaps they are trying to use VPN? Might want to disable that. Error 727 - Cannot access TCPCFG.DLL 1. Make sure that TCPCFG.DLL is not read only. 2. If you cannot find TCPCFG.DLL or this did not work, try reinstalling RAS/DUN. Error 728 - Cannot find an IP adapter bound to Remote Access 1. Are the TCP/IP to RAS/DUN bindings correct? (it should be bound) 2. Uninstall/reinstall RAS/DUN. Error 729 - SLIP cannot be used unless the IP protocol is installed 1. Make sure that dialer is set to use PPP, that the dialer settings are correct, the network settings are correct, and that TCP/IP is installed in the network control panel. Error 730 - Computer registration is not complete 1. This should not happen when dialing into an ISP. Make sure the phone number is correct. A request for information on the status of computer registration was made before the information was made available, so if the computer is dialing up for registration, reboot and try again. Error 731 - The protocol is not configured 1. Make sure network and dialer settings are correct. 2. Uninstall and reinstall dialer, network, and DUN. 3. Check for modem driver updates and try modem inits. AT&F&C1&D2 as a generic 56k init and ATZ as a non-56k generic init. Error 732 - The PPP negotiation is not converging 1. In NT, make sure accept any auth including clear text is checked. In 95/98 make sure logon to network is not checked and TCP/IP is checked. 2. Check for extra winsock.dll's (one in C:\windows) and extra wsock32.dll's (one in c:\windows\system). 3. Check network settings. 4. Full uninstall and reinstall of connectoid, network, and DUN. Error 733 - The PPP control protocol for this network protocol is not available on the server 1. Make sure PPP is selected in the connectoid. In NT turn off Enable PPP LCP extensions. 2. Make sure TCP/IP is checked. 3. Disable WINS in TCP/IP in network. 4. Uninstall and reinstall TCP/IP in network. Error 734 - The PPP link control protocol terminated 1. Make sure network and dialer settings are correct. 2. In NT: Try turning off PPP LCP extensions. 3. Could be an ISP problem. Check on this. Error 735 - The requested address was rejected by the server 1. Make sure the dialer is not set to specify an IP address. 2. Make sure the network control panel is not requesting a specific ip address. 3. Check TCP/IP in the network control panel, and set WINS to disabled. Also try it as DHCP if it is already disabled. Error 736 - The remote computer terminated the control protocol 1. If this is not a regular occurrence, reboot and dial in again. 2. In NT: Try disabling PPP LCP extensions. 3. Try unchecking "enable software compression" in the dialer. 4. Could be on the ISP's end. Error 737 - Loopback detected 1. Check all of the dialer and network settings. Try removing any init strings from the modem. 2. Try uninstalling and reinstalling the modem. 3. Add E0 to any init string the computer may have been using or just use ATE0. This turns echo off. Basically the computer is echoing commands back to itself and thinks that it is trying to negotiate PPP with itself, so this could fix it. Error 738 - The server did not assign an address 1. Turn off error control and compression in the modem settings. 2. Uncheck enable software compression (and PPP LCP extensions in NT). 3. In TCP/IP in the network control panel, click on WINS and "enable Windows Resolution". 4. Still in TCP/IP make sure that the IP is being attained automatically and (in NT) uncheck enable PPP LCP extensions. Error 739 - The remote server cannot use the Windows NT encrypted passwordbr> 1. In 95/98: Check dialer and make sure that "require encrypted password/use secure auth" is not checked. In NT: check dialer and make sure that "Accept any auth including clear text" is checked. Error 740 - The TAPI devices configured for Remote Access failed to initialize or were not installed correctly 1. TAPI device error. Either the TAPI device was not installed properly or it just failed to initialize. Reinstall RAS and all TAPI devices. Error 741 - The local computer does not support encryption 1. Usually this means that the server is asking for secure password authentication. Usually ISPs do not require this, probably about 99% of them. Make sure that the correct number is being dialed. Could be an ISP issue? 2. In 95/98: Check dialer and make sure that "require encrypted password/use secure auth" is not checked. In NT: check dialer and make sure that "Accept any auth including clear text" is checked. Error 742 - The remote server does not support encryption 1. In 95/98: Check dialer and make sure that "require encrypted password/use secure auth" is not checked. In NT: check dialer and make sure that "Accept any auth including clear text" is checked. Error 743 - The remote server requires encryption 1. Usually this means that the server is asking for secure password authentication. Usually ISPs do not require this, probably about 99% of them. Make sure that the correct number is being dialed. Could be an ISP issue? 2. In 95/98: Check dialer and make sure that "require encrypted password/use secure auth" is not checked. In NT: check dialer and make sure that "Accept any auth including clear text" is checked. Error 744 - Cannot use the IPX net number assigned by the remote server. Check the event log 1. Check network and dialer settings to make sure that it is not using IPX/SPX. If they are using it for a LAN check with the LAN administrator. 2. If they are not on a LAN, remove any occurrences of IPX/SPX and try reinstalling TCP/IP. Error 745 - An essential file is missing 1. Uninstall and reinstall Dial Up Networking. *** USE THE FOLLOWING STEP AT YOUR OWN RISK! *** 2. If it keeps reoccuring...Run regedit and go to the key: HKEY_LOCAL_MACHINE > System > CurrentControlSet > Services > RemoteAccess > Authentication > SMM_Files > PPP. Make sure that "Path"'s value data is RASAPI32.DLL. Close regedit and do a full uninstall and reinstall of DUN/RAS again. More info on error 745 can be found at: http://support.microsoft.com/support/kb/articles/Q174/5/79.asp Error 751 - The callback number contains an invalid character. Only the following characters are allowed: 0 to 9, T, P, W, (,), -, @, and space 1. In Win2k under Network & Dial-Up click on Advanced > Dial-Up Preferences > the Callback tab > and make sure that "No Callback" is selected. 2. If the user is supposed to be using callback make sure they using the correct dialup number/charactes as the error suggests. 3. Recreate the dailer. Error 752 - A syntax error was encountered while processing a script 1. The user is trying to use a script. Remove this script. If they need this script then try finding a syntax error/mistakes in the script. 2. If the script is "needed" because they need to use a terminal window then just check "bring a terminal window up after dialing" in the modem properties. Error 753 - The connection could not be disconnected because it was created by the multi-protocol router 1. The user appears to be already dialed in. Disconnect or reboot. 2. Use the Routing and Remote Access service to disconnect the connection, and make sure that nothing is attempting to dialup automatically with the wrong connection. 3. Recreate the dialer, and delete any unused dialers. Error 754 - The system could not find the multi-link bundle 1. Reboot the machine. 2. Is the user supposed to be using Multilink? If not disable it, if so reinstall the dialup components. 3. Check settings (DUN/RAS, Network, etc) 4. Do a full reinstall of dialup related components. 5. If you are running Windows 2000 or NT check the event log for further details on this error. Error 755 - The system cannot perform automated dial because this entry has a custom dialer specified 1. Close any other programs that dialup, like fax software, trumpet, sprydialer, AOL, etc. 2. Remove any of these programs from the systemif they are unneeded. 3. Recreate the dailer. 4. Reboot the machine. 5. Reinstall dialup/network components. Error 756 - This connection is already being dialed 1. Close any other programs that dialup, like fax software, trumpet, sprydialer, AOL, etc. 2. Remove any of these programs from the systemif they are unneeded. 3. Recreate the dailer. Error 757 - Remote access services could not be started automatically. Additional information is provided in the event log 1. Reboot the machine. 2. Check settings (DUN/RAS, Network, etc) 3. Do a full reinstall of dialup related components. 4. If you are running Windows 2000 or NT check the event log for further details on this error. Error 758 - Internet connection sharing is already enabled on the connection 1. Reboot. In the connection properties check the Enable Internet connection sharing box under the Internet connection sharing tab, make sure to select a LAN connection from the list. 2. Remove Internet Connection Sharing (it is mostly unsupported, if removing it fixes it, it is up to the user or network admin to figure it out). Error 760 - An error occurred while routing capabilities were being enabled 1. Check the dialer settings, making sure that the user isn't set to static IP addressing (less they are supposed to) and that all other settings are ok. 2. Reinstall TCP/IP. 3. Reboot the computer. 4. Reinstall all dialup components. Error 761 - An error occurred while Internet connection sharing was being enabled for the connection 1. Make sure that Internet Connection Sharing is set to LAN. 2. Disable Internet Connection Sharing and contact the Network Admin to get it running properly. Error 763 - Internet connection sharing cannot be enabled. There are two or more LAN connections in addition to the connection to be shared 1. Make sure that Internet Connection Sharing is set to LAN. 2. Disable Internet Connection Sharing and contact the Network Admin to get it running properly. Error 764 - No smart card reader is installed 1. In the connection settings under the Security tab make sure that any auth is allowed. 2. Check the other dialer settings. 3. Recreate the dialer. 4. The user may need a Smart Card Reader as setup by their Network Admin. Error 765 - Internet connection sharing cannot be enabled. A LAN connection is already configured with the IP address required for automatic IP addressing 1. Make sure that Internet Connection Sharing is set to LAN. 2. Disable Internet Connection Sharing and contact the Network Admin to get it running properly. Error 766 - The system could not find any certificate 1. Have the user goto the following website to obtain a valid certificate: http://windows.microsoft.com/windows2000/en/professional/help/sag_cswprocs_reqcert.htm Error 767 - Internet connection sharing cannot be enabled. The LAN connection selected on the private network has more than one IP address configured. Reconfigure the LAN connection with a single IP address before enabling Internet connection sharing 1. Check the dialer settings, making sure that the user isn't set to static IP addressing (less they are supposed to) and that all other settings are ok. 2. Reinstall TCP/IP. 3. Reboot the computer. 4. Reinstall all dialup components. Error 768 - The connection attempt failed because of failure to encrypt data 1. Disable encryption in the connection properties. Error 769 - The specified destination is not reachable 1. Check the dialer settings, making sure that the user isn't set to static IP addressing (less they are supposed to) and that all other settings are ok. 2. Reinstall TCP/IP. 3. Reboot the computer. 4. Reinstall all dialup components. Error 770 - The remote machine rejected the connection attempt 1. This is probably a modem error. In any case, check the connectoid and Network settings. If they look good then... 2. Make sure modem is setup properly, try inits, check for updated drivers. 3. Lower the Fifo buffers. Lower port speed to 57600, making sure the checkbox to 'only connect at this speed' is unchecked. 4.1. Click Start, goto find, and click files or folders. 4.2. Search for telephon.ini. 4.3. If you find it then rename it to telephon.old or telephon.bad. 4.4. Click on Start, Run, then type tapiini.exe, press Enter. 4.5. Reboot. 5. Check into line noise. Error 771 - The connection attempt failed because the network is busy 1. Make sure the user is dialing the correct phone number. Make sure the phone number they are dialing is not having issues. 2. Check the connectoid and Network settings. 3. Make sure modem is setup properly, try inits, check for updated drivers. 4. Lower the Fifo buffers. Lower port speed to 57600, making sure the checkbox to 'only connect at this speed' is unchecked. 5. Check into line noise. Error 772 - The remote computer's network hardware is incompatible with the type of call requested 1. Make sure the dialer is setup properly. It should be an actual dialer and not setup for LAN use. 2. See Network Admin. Error 773 - The connection attempt failed because the destination number has changed 1. Make sure the user is dialing the correct phone number (check area code, etc). Make sure the phone number they are dialing is not having issues. Error 774 - The connection attempt failed because of a temporary failure. Try connecting again 1. Reboot. 2. Check dialer settings. 3. Reinstall dialup components. Error 775 - The call was blocked by the remote computer 1. Make sure the correct number is being dialed (check area code, etc.) 2. Make sure the number is not experiencing an outage. 3. Make sure user is not out of time for the day, etc, if this applies to the ISP. 4. Try disabling call waiting if the location has call waiting. 5. Does the number you are dialing from have voice mail? Voice mail can cause this and you will want to check your voicemail. If this becomes a common problem you may wish to reconsider having Voice mail on the number the computer dials from. Error 776 - The call could not be connected because the destination has invoked the Do Not Disturb feature 1. Make sure the dialer is setup properly. It should be an actual dialer and not setup for LAN use. 2. See Network Admin. Error 777 - The connection attempt failed because the modem on the remote computer is out of order 1. The modem isn't working. If external, powercycle it, if internal, reboot the computer. 2. Make sure the modem is plugged in securely. This includes external cables, and the PCI or ISA slot seating if internal. 3. Make sure the computer is not trying to dial multiple connections, that it has no fax software, etc using the modem. 4. Reinstall the modem. 5. Contact OEM. Error 778 - It was not possible to verify the identity of the server 1. Make sure the user is dialing the correct phone number. Make sure the phone number they are dialing is not having issues. 2. Check the connectoid and Network settings. 3. Make sure there is not an outage on that phone number. 4. Make sure modem is setup properly, try inits, check for updated drivers. 5. Lower the Fifo buffers. Lower port speed to 57600, making sure the checkbox to 'only connect at this speed' is unchecked. 6. Check into line noise. Error 779 - To dial out using this connection, you must use a smart card 1. In the connection settings under the Security tab make sure that any auth is allowed. 2. Check the other dialer settings. 3. Recreate the dialer. 4. The user may need a Smart Card Reader as setup by their Network Admin. Error 780 - An attempted function is not valid for this connection 1. Make sure the dialer is setup properly. It should be an actual dialer and not setup for LAN use. 2. See Network Admin. Error 781 - The encryption attempt failed because no valid certificate was found 1. Have the user goto the following website to obtain a valid certificate: http://windows.microsoft.com/windows2000/en/professional/help/sag_cswprocs_reqcert.htm Errors without fixes: 682 ERROR WRITING SECTIONNAME 683 ERROR WRITING DEVICETYPE 684 ERROR WRITING DEVICENAME 686 ERROR WRITING MAXCARRIERBPS 687 ERROR WRITING USAGE 688 ERROR WRITING DEFAULTOFF 689 ERROR READING DEFAULTOFF 694 ERROR DCB NOT FOUND 696 ERROR STATE MACHINES ALREADY STARTED 706 ERROR WRITING INITBPS 746 An essential file failed to initialize. 747 MAC not found. 748 The system timed out while trying to load an essential file. 749 Invalid phone number. 750 Invalid authentication attempt. 782 Network Address Translation (NAT) is currently installed as a routing protocol, and must be removed before enabling Internet Connection Sharing 783 Internet Connection Sharing cannot be enabled. The LAN connection selected as the private network is either not present, or is disconnected from the network. Please ensure that the LAN adapter is connected before enabling Internet Connection Sharing 784 You cannot dial using this connection at logon time, because it is configured to use a user name different than the one on the smart card. If you want to use it at logon time, you must configure it to use the user name on the smart card 785 You cannot dial using this connection at logon time, because it is not configured to use a smart card. If you want to use it at logon time, you must edit the properties of this connection so that it uses a smart card 786 The L2TP connection attempt failed because there is no valid machine certificate on your computer for security authentication 787 The L2TP connection attempt failed because the security layer could not authenticate the remote computer 788 The L2TP connection attempt failed because the security layer could not negotiate compatible parameters with the remote computer 789 The L2TP connection attempt failed because the security layer encountered a processing error during initial negotiations with the remote computer 790 The L2TP connection attempt failed because certificate validation on the remote computer failed 791 The L2TP connection attempt failed because security policy for the connection was not found 792 The L2TP connection attempt failed because security negotiation timed out 793 The L2TP connection attempt failed because an error occurred while negotiating security 794 The Framed Protocol RADIUS attribute for this user is not PPP 795 The Tunnel Type RADIUS attribute for this user is not correct 796 The Service Type RADIUS attribute for this user is neither Framed nor Callback Framed 797 A connection to the remote computer could not be established because the modem was not found or was busy 798 A certificate could not be found that can be used with this Extensible Authentication Protocol 799 Internet Connection Sharing (ICS) cannot be enabled due to an IP address conflict on the network. ICS requires the host be configured to use 192.168.0.1. Please ensure that no other client on the network is configured to use 192.168.0.1 800 Unable to establish the VPN connection. The VPN server may be un-reachable, or security parameters may not be configured properly for this connection 995 Operation aborted. 1382 Maximum length exceeded. 1793 Account expired. 2250 Network connection does not exist.