DUN Error Codes

Error Number	Message	Description
600 Return to Top	An operation is pending	This error should not occur under normal circumstances. Restart you computer to make sure that all recent configuration changes have taken affect. If the error persists, consult the Windows NT event log of detailed warnings or errors
601 Return to Top	The port handle is invalid	This error should not occur under normal circumstances. Restart you computer to make sure that all recent configuration changes have taken affect. If the error persists, consult the Windows NT event log of detailed warnings or errors
602 Return to Top	The port is already open	Another application is using the port. Close the application and redial
603 Return to Top	The buffer is too small.	This error should not occur under normal circumstances. Restart you computer to make sure that all recent configuration changes have taken affect. If the error persists, consult the Windows NT event log of detailed warnings or errors
604 Return to Top	Wrong information specified.	The Remote Access Phone Book file and the current Remote access configuration are probably inconsistent. If you have changed your communications equipment (such as your serial port or modem), be sure to reconfigure Remote access. See Reconfiguring Dial-Up Networking  If the error persists, remove and recreate the affected Phone Book entry or , reinstall the Remote Access Service. The Remote Access Phonebook (rasphone.pbk) Is in the SYSTEM32/RAS subdirectory of your windows NT directory
605 Return to Top	Cannot set port information.	The Remote Access Phone Book file and the current Remote access configuration are probably inconsistent. If you have changed your communications equipment (such as your serial port or modem), be sure to reconfigure Remote access. See Reconfiguring Dial-Up Networking  If the error persists, remove and recreate the affected Phone Book entry or , reinstall the Remote Access Service. The Remote Access Phonebook (rasphone.pbk) Is in the SYSTEM32/RAS subdirectory of your windows NT directory
606 Return to Top	The port is not connected.	This error should not occur under normal circumstances. Restart you computer to make sure that all recent configuration changes have taken affect. If the error persists, consult the Windows NT event log of detailed warnings or errors
607 Return to Top	The event is invalid.	This error should not occur under normal circumstances. Restart you computer to make sure that all recent configuration changes have taken affect. If the error persists, consult the Windows NT event log of detailed warnings or errors
608 Return to Top	The device does not exist	The Remote Access Phone Book file and the current Remote access configuration are probably inconsistent. If you have changed your communications equipment (such as your serial port or modem), be sure to reconfigure Remote access. See Reconfiguring Dial-Up Networking  If the error persists, remove and recreate the affected Phone Book entry or, reinstall the Remote Access Service. The Remote Access Phonebook (rasphone.pbk) Is in the SYSTEM32/RAS subdirectory of your windows NT directory
609 Return to Top	The device does not exist	The Remote Access Phone Book file and the current Remote access configuration are probably inconsistent. If you have changed your communications equipment (such as your serial port or modem), be sure to reconfigure Remote access. See Reconfiguring Dial-Up Networking  If the error persists, remove and recreate the affected Phone Book entry or , reinstall the Remote Access Service. The Remote Access Phonebook (rasphone.pbk) Is in the SYSTEM32/RAS subdirectory of your windows NT directory
610 Return to Top	The buffer is invalid	This error should not occur under normal circumstances. Restart you computer to make sure that all recent configuration changes have taken affect. If the error persists, consult the Windows NT event log of detailed warnings or errors
611 Return to Top	The route is not available	Most likely, your network configuration is wrong. Restart your computer to make sure that all recent configuration changes have taken effect. If error persists, consult the Windows NT event log for detailed warnings or errors. Have customer record the fail code (a NetBIOS) error code
612 Return to Top	The route is not allocated	Most likely, your network configuration is wrong. Restart your computer to make sure that all recent configuration changes have taken effect. If error persists, consult the Windows NT event log for detailed warnings or errors. Have customer record the fail code (a NetBIOS) error code
613 Return to Top	Invalid compression specified	This error should not occur under normal circumstances. Restart you computer to make sure that all recent configuration changes have taken affect. If the error persists, consult the Windows NT event log of detailed warnings or errors
614 Return to Top	Our of butters	This error should not occur under normal circumstances. Restart you computer to make sure that all recent configuration changes have taken affect. If the error persists, consult the Windows NT event log of detailed warnings or errors
615 Return to Top	The port was not found	The Remote Access Phone Book file and the current Remote access configuration are probably inconsistent. If you have changed your communications equipment (such as your serial port or modem), be sure to reconfigure Remote access. See Reconfiguring Dial-Up Networking  If the error persists, remove and recreate the affected Phone Book entry or , reinstall the Remote Access Service. The Remote Access Phonebook (rasphone.pbk) Is in the SYSTEM32/RAS subdirectory of your windows NT directory
616 Return to Top	An asynchronous request is pending	This error should not occur under normal circumstances. Restart you computer to make sure that all recent configuration changes have taken affect. If the error persists, consult the Windows NT event log of detailed warnings or errors
617 Return to Top	The port or device is already disconnecting	Wait for Remote Access to Finnish disconnecting the entry or close the remote access Service
618 Return to Top	The port is open	This error should not occur under normal circumstances. Restart you computer to make sure that all recent configuration changes have taken affect. If the error persists, consult the Windows NT event log of detailed warnings or errors
619 Return to Top	The port is disconnected	This error should not occur under normal circumstances. Restart you computer to make sure that all recent configuration changes have taken affect. If the error persists, consult the Windows NT event log of detailed warnings or errors
620 Return to Top	There are no endpoints	Most likely, your network configuration is wrong. Restart your computer to make sure that all recent configuration changes have taken effect. If error persists, consult the Windows NT event log for detailed warnings or errors. Have customer record the fail code (a NetBIOS) error code
621 Return to Top	Cannot open the phone book file	The Remote Access Service uses the RASPHONE.PBK file in the system32RAS subdirectory of your Windows NT directory. Make sure the file is on this Path, and restart Remote Access
622 Return to Top	Cannot load the phone book file	The Remote Access Service uses the RASPHONE.PBK file in the system32RAS subdirectory of your Windows NT directory. Make sure the file is on this Path, and restart Remote Access
623 Return to Top	Cannot find the phone book entry	Remote Access has located the Phone Book but cannot find the specified entry. This error should not occur unless you are writing to Remote Access APIs, and have specified an incorrect entry name. The Remote Access Service uses the file RASPHONE.PBK, located in the SYSTEM32RAS subdirectory of your Windows NT directory
624 Return to Top	Cannot write the phone book entry	The Remote Access Service uses the RASPHONE.PBK file in the system32RAS subdirectory of your Windows NT directory. Make sure the file is on this Path, and restart Remote Access
625 Return to Top	Invalid information found in the phone book	The Remote Access Service uses the RASPHONE.PBK file in the system32RAS subdirectory of your Windows NT directory. Make sure the file is on this Path, and restart Remote Access
626 Return to Top	Cannot load a string	This error should not occur under normal circumstances. Restart you computer to make sure that all recent configuration changes have taken affect. If the error persists, consult the Windows NT event log of detailed warnings or errors
627 Return to Top	Cannot find key	One of the Remote Access configuration files probably contains invalid information. The easiest way to resolve this problem is to reinstall remote access.  If you are using a modem that is not supported by Remote Access, Switch to a supported modem, or see Overview of Modem Script File for information about modifying the modem script file for your modem
628 Return to Top	The port was disconnected	Redial the entry. If you continue to get this message, reduce the modem’s initial speed, and turn off the advanced modem features. See Setting Modem Features. If the problem persists, contact your system administrator. If you’re dialing manually, make sure you’re connected before you click done
629 Return to Top	The port was disconnected by the remote machine	The link has been disconnected for one of the following reasons:  An unrecoverable phone line error  A noisy line  Disconnection by the system administrator To re-establish the link, redial. You can enable automatic redialing through the User Preference Dialing tab. See Redial settings  If this error persists, lower the modem’s initial speed (bps) setting, and dial again. See Setting Modem Features
630 Return to Top	The port was disconnected due to hardware failure	The link has been disconnected for one of the following reasons:  An unrecoverable phone line error  A noisy line  Disconnection by the system administrator To re-establish the link, redial. You can enable automatic redialing through the User Preference Dialing tab. See Redial settings  If this error persists, lower the modem’s initial speed (bps) setting, and dial again. See Setting Modem Features
631 Return to Top	The port was disconnected by the user	You have disconnected the line through an action on your computer. Redial
632 Return to Top	The structure size is incorrect	This error should not occur under normal circumstances. Restart you computer to make sure that all recent configuration changes have taken affect. If the error persists, consult the Windows NT event log of detailed warnings or errors
633 Return to Top	The port is already in use or is not configured for remote access dial out	If the port is already in use by another connection, hang up the connection on this port, or edit the entry to use another communication port  If the port is not already in use, reconfigure you remote access port for dial out. Ensure that the adapter/modem has been installed and the port has been added using the Control Panel Network option. See Reconfiguring Dialup Networking
634 Return to Top	Cannot register you computer on the remote network	The Remote Access server was unable to register your computer’s name on the network. Contact your system administrator
635 Return to Top	Unknown error	This error should not occur under normal circumstances. Restart you computer to make sure that all recent configuration changes have taken affect. If the error persists, consult the Windows NT event log of detailed warnings or errors
636 Return to Top	The wrong device is attached to the port	Your hardware configuration and the Remote Access setup are probably inconsistent with each other. If you have changed your communications equipment (such as serial port or modem), be sure to reconfigure Remote Access accordingly. See Reconfiguring Dial-Up Networking
637 Return to Top	The string could not be converted	This error should not occur under normal circumstances. Restart you computer to make sure that all recent configuration changes have taken affect. If the error persists, consult the Windows NT event log of detailed warnings or errors
638 Return to Top	The request has timed out	This error should not occur under normal circumstances. Restart you computer to make sure that all recent configuration changes have taken affect. If the error persists, consult the Windows NT event log of detailed warnings or errors
639 Return to Top	No asynchronous net available	Most likely, your network configuration is wrong. Restart your computer to make sure that all recent configuration changes have taken effect. If error persists, consult the Windows NT event log for detailed warnings or errors. Have customer record the fail code (a NetBIOS) error code
640 Return to Top	A NetBIOS error has occurred	Your modem may not have negotiated the connection correctly, or the line may be noisy. Set the modem to a lower initial speed (bps), and make it available to your technical support staff if you call for help
641 Return to Top	The server cannot allocate NetBIOS resources needed to support the client	Ask your system administrator to increase the resource capacity of the Remote Access server, or through the Services Control Panel stop nonessential services on your computer, such as messaging and network DDE
642 Return to Top	One of your NetBIOS names is already registered on the remote network	Networking architecture requires each computer on the network to be registered with a unique name. This rule applies to both the LAN and remote workstation.  To see if your computer has a unique name on the network, do the following:  Make sure your computer name is different from all other computer names on the network To change your computer name, start the Network Control Panel, and select a new computer name. If the name is not your computer name, another computer may have registered a computer name matching your domain name, or you are running a NetBIOS application that has added a conflicting name  If the problem persists after changing the name, contact your system administrator NOTE  Because unique names are required, you cannot have both a Remote Access and a direct connection (such as Ethernet Connector) To the same network. If you are evaluating Remote Access in such a situation, you need to unplug the network connector before attempting to connect through Remote Access
643 Return to Top	A network adapter at the server failed	Report this error to your system administrator.
644 Return to Top	You will not receive network message popups	Another computer already connected to the network is using your messaging name. Messages addressed to you will be sent to that computer. If you want to receive messages at your remote workstation, you must remember to log off your office computer before you next dial in to the network.  Note  This error does not affect messaging through Microsoft Mail.
645 Return to Top	Internal authentication error	This error should not occur under normal circumstances. Restart you computer to make sure that all recent configuration changes have taken affect. If the error persists, consult the Windows NT event log of detailed warnings or errors
646 Return to Top	The account is not permitted to log on at this time of day	Your account has been configured for limited access to the network. If you need to access the network at a different time of day than what's presently configured, ask your system administrator to change the configuration.
647 Return to Top	The account is disabled	Ask your system administrator to enable your account.
648 Return to Top	The password has expired	If you are connecting through the Remote Access Phone Book, you will automatically be prompted to change your password.  If you are connecting through the RASDIAL command, you can change your password by doing the following:  Press CTRL+ALT+DEL. Select Change Password, and follow the instructions on the screen.
649 Return to Top	The account does not have Remote Access permission	You have a valid account on the domain you selected, but your account does not have permission to access the network remotely. Ask your system administrator to give you dial-in permission.  If you have an account with dial-in permission on another domain, do the following to use your account on that domain:  Edit the Phone Book entry and clear the Authenticate using current user name and password check box. Dial. specify the appropriate user name, password, and domain.
650 Return to Top	The Remote Access Server is not responding	One of the following may have caused this error:  The Remote Access server is not running. Contact your system administrator to make sure the server is running.  The line may be too noisy. Lower the modem's initial speed (bps), and dial again. See Setting Modem Features.  Your modem may have failed to negotiate correctly with the Remote Access server's modem at the selected speed. Lower the modem's initial speed (bps), and dial again.
651 Return to Top	Your modem (or other connecting device) had reported an error	One of the Remote Access configuration files probably contains invalid information. The easiest way to resolve this problem is to reinstall remote access.  If you are using a modem that is not supported by Remote Access, Switch to a supported modem, or see Overview of Modem Script File for information about modifying the modem script file for your modem
652 Return to Top	Unrecognized response from the device	One of the Remote Access configuration files probably contains invalid information. The easiest way to resolve this problem is to reinstall remote access.  If you are using a modem that is not supported by Remote Access, Switch to a supported modem, or see Overview of Modem Script File for information about modifying the modem script file for your modem
653 Return to Top	A macro required by the device was not found in the device .INF file section	One of the Remote Access configuration files probably contains invalid information. The easiest way to resolve this problem is to reinstall remote access.  If you are using a modem that is not supported by Remote Access, Switch to a supported modem, or see Overview of Modem Script File for information about modifying the modem script file for your modem
654 Return to Top	A command or response in the device .INF file section refers to an undefined macro	One of the Remote Access configuration files probably contains invalid information. The easiest way to resolve this problem is to reinstall remote access.  If you are using a modem that is not supported by Remote Access, Switch to a supported modem, or see Overview of Modem Script File for information about modifying the modem script file for your modem
655 Return to Top	The macro was not found in the device .INF file section	One of the Remote Access configuration files probably contains invalid information. The easiest way to resolve this problem is to reinstall remote access.  If you are using a modem that is not supported by Remote Access, Switch to a supported modem, or see Overview of Modem Script File for information about modifying the modem script file for your modem
656 Return to Top	The macro in the device .INF file section contains an undefined macro	One of the Remote Access configuration files probably contains invalid information. The easiest way to resolve this problem is to reinstall remote access.  If you are using a modem that is not supported by Remote Access, Switch to a supported modem, or see Overview of Modem Script File for information about modifying the modem script file for your modem
657 Return to Top	The device .INF file could not be opened	One of the Remote Access configuration files probably contains invalid information. The easiest way to resolve this problem is to reinstall remote access.  If you are using a modem that is not supported by Remote Access, Switch to a supported modem, or see Overview of Modem Script File for information about modifying the modem script file for your modem
658 Return to Top	The device name in the device.INF or media.INI file is too long	One of the Remote Access configuration files probably contains invalid information. The easiest way to resolve this problem is to reinstall remote access.  If you are using a modem that is not supported by Remote Access, Switch to a supported modem, or see Overview of Modem Script File for information about modifying the modem script file for your modem
659 Return to Top	The media.INI file refers to an unknown device name	One of the Remote Access configuration files probably contains invalid information. The easiest way to resolve this problem is to reinstall remote access.  If you are using a modem that is not supported by Remote Access, Switch to a supported modem, or see Overview of Modem Script File for information about modifying the modem script file for your modem
660 Return to Top	The device.INF file contains no responses for the command	One of the Remote Access configuration files probably contains invalid information. The easiest way to resolve this problem is to reinstall remote access.  If you are using a modem that is not supported by Remote Access, Switch to a supported modem, or see Overview of Modem Script File for information about modifying the modem script file for your modem
661 Return to Top	The device.INF file is missing a command	One of the Remote Access configuration files probably contains invalid information. The easiest way to resolve this problem is to reinstall remote access.  If you are using a modem that is not supported by Remote Access, Switch to a supported modem, or see Overview of Modem Script File for information about modifying the modem script file for your modem
662 Return to Top	Attempted to set a macro not listed in device.INF file section	One of the Remote Access configuration files probably contains invalid information. The easiest way to resolve this problem is to reinstall remote access.  If you are using a modem that is not supported by Remote Access, Switch to a supported modem, or see Overview of Modem Script File for information about modifying the modem script file for your modem
663 Return to Top	The media.INI file refers to an unknown device type	One of the Remote Access configuration files probably contains invalid information. The easiest way to resolve this problem is to reinstall remote access.  If you are using a modem that is not supported by Remote Access, Switch to a supported modem, or see Overview of Modem Script File for information about modifying the modem script file for your modem
664 Return to Top	Cannot allocate memory	The system has run out of memory. Close some applications, and redial.
665 Return to Top	The port is not configured for Remote Access	665  If the port is already being used for another connection, hang up that connection, or edit this entry to use another communications port.  If the port is not already in use, reconfigure your Remote Access port for dialing out. For instructions, see Reconfiguring Dial-Up Networking.
666 Return to Top	Your modem (or other connecting devices) is not functioning	666  Your modem (or other connecting device) is not responding for one of the following reasons:  The modem has been turned off.  The modem is not securely connected to your computer. Make sure your cable is securely fastened to both the modem and the computer.  The serial cable does not have the correct specifications required by Remote Access. See Cabling Requirements.  The modem has experienced a hardware glitch. Turn off the modem, wait for 20 seconds, and then restart the modem.
667 Return to Top	Cannot read the media.INI file	One of the Remote Access configuration files probably contains invalid information. The easiest way to resolve this problem is to reinstall remote access.  If you are using a modem that is not supported by Remote Access, Switch to a supported modem, or see Overview of Modem Script File for information about modifying the modem script file for your modem
668 Return to Top	The connection dropped	Redial the entry. If you continue to get this message, reduce the modem's initial speed, and turn off the advanced modem features. See Setting Modem Features. If the problem persists, contact your system administrator.  If you're dialing manually, make sure you're connected before you click Done.
669 Return to Top	The usage parameter in the media.INI file is invalid	One of the Remote Access configuration files probably contains invalid information. The easiest way to resolve this problem is to reinstall remote access.  If you are using a modem that is not supported by Remote Access, Switch to a supported modem, or see Overview of Modem Script File for information about modifying the modem script file for your modem
670 Return to Top	Cannot read the section name from the media.INI file	One of the Remote Access configuration files probably contains invalid information. The easiest way to resolve this problem is to reinstall remote access.  If you are using a modem that is not supported by Remote Access, Switch to a supported modem, or see Overview of Modem Script File for information about modifying the modem script file for your modem
671 Return to Top	Cannot read the device type from the media.INI file	One of the Remote Access configuration files probably contains invalid information. The easiest way to resolve this problem is to reinstall remote access.  If you are using a modem that is not supported by Remote Access, Switch to a supported modem, or see Overview of Modem Script File for information about modifying the modem script file for your modem
672 Return to Top	Cannot read the device name from the media.INI file	One of the Remote Access configuration files probably contains invalid information. The easiest way to resolve this problem is to reinstall remote access.  If you are using a modem that is not supported by Remote Access, Switch to a supported modem, or see Overview of Modem Script File for information about modifying the modem script file for your modem
673 Return to Top	Cannot read the usage from the media.INI file	One of the Remote Access configuration files probably contains invalid information. The easiest way to resolve this problem is to reinstall remote access.  If you are using a modem that is not supported by Remote Access, Switch to a supported modem, or see Overview of Modem Script File for information about modifying the modem script file for your modem
674 Return to Top	Cannot read the maximum connection BPS rate from the media.INI file	One of the Remote Access configuration files probably contains invalid information. The easiest way to resolve this problem is to reinstall remote access.  If you are using a modem that is not supported by Remote Access, Switch to a supported modem, or see Overview of Modem Script File for information about modifying the modem script file for your modem
675 Return to Top	Cannot read the maximum carrier BPS rate from the media.INI file	One of the Remote Access configuration files probably contains invalid information. The easiest way to resolve this problem is to reinstall remote access.  If you are using a modem that is not supported by Remote Access, Switch to a supported modem, or see Overview of Modem Script File for information about modifying the modem script file for your modem
676 Return to Top	The line is busy	Redial the number. Automate redialing through the User Preferences Dialing tab. See Redial Settings
677 Return to Top	A person answered instead of a modem	A modem did not pick up the phone. Please check the number and dial again.
678 Return to Top	There is no answer	A modem did not pick up the phone. Please check the number and dial again.
679 Return to Top	Cannot detect carrier	A modem did not pick up the phone. Please check the number and dial again. Automate redialing through the User Preferences  Dialing tab. See Redial Settings  Note  Many modems return this error if the remote modem does not pick up the phone.
680 Return to Top	There is no dial tone	Make sure the phone line is plugged into the correct socket in the modem. Also, make sure you've added any special access numbers, such as the prefix 9 followed by a comma, to connect to an outside line. For example: 9,555-8181
681 Return to Top	General error reported by device	One of the Remote Access configuration files probably contains invalid information. The easiest way to resolve this problem is to reinstall Remote Access.  If you are using a modem that is not supported by Remote Access, switch to a supported modem, or see Overview of Modem Script File for information about modifying the modem script file for your modem.  The Remote Access script files (PAD.INF, MODEM.INF, and SWITCH.INF) are in the SYSTEM32RAS subdirectory of your Windows NT directory.
682 Return to Top	ERROR WRITING SECTIONNAME	This error should not occur under normal circumstances. Restart your computer to make sure that all recent configuration changes have taken effect. If the error persists, consult the Windows NT event log for detailed warnings or errors.
683 Return to Top	ERROR WRITING DEVICETYPE	This error should not occur under normal circumstances. Restart your computer to make sure that all recent configuration changes have taken effect. If the error persists, consult the Windows NT event log for detailed warnings or errors.
684 Return to Top	ERROR WRITING DEVICE NAME	This error should not occur under normal circumstances. Restart your computer to make sure that all recent configuration changes have taken effect. If the error persists, consult the Windows NT event log for detailed warnings or errors.
685 Return to Top	ERROR WRITING MAXCONNECTBPS	This error should not occur under normal circumstances. Restart your computer to make sure that all recent configuration changes have taken effect. If the error persists, consult the Windows NT event log for detailed warnings or errors.
686 Return to Top	ERROR WRITING MAXCARRIERBPS	This error should not occur under normal circumstances. Restart your computer to make sure that all recent configuration changes have taken effect. If the error persists, consult the Windows NT event log for detailed warnings or errors.
687 Return to Top	ERROR WRITING USAGE	This error should not occur under normal circumstances. Restart your computer to make sure that all recent configuration changes have taken effect. If the error persists, consult the Windows NT event log for detailed warnings or errors.
688 Return to Top	ERROR WRITING DEFAULTOFF	This error should not occur under normal circumstances. Restart your computer to make sure that all recent configuration changes have taken effect. If the error persists, consult the Windows NT event log for detailed warnings or errors.
689 Return to Top	ERROR READING DEFAULTOFF	This error should not occur under normal circumstances. Restart your computer to make sure that all recent configuration changes have taken effect. If the error persists, consult the Windows NT event log for detailed warnings or errors.
690 Return to Top	ERROR EMPTY INI FILE	This error should not occur under normal circumstances. Restart your computer to make sure that all recent configuration changes have taken effect. If the error persists, consult the Windows NT event log for detailed warnings or errors.
691 Return to Top	Access denied because username and/or password is invalid on the domain	Type your user name, password, and domain. If you are unsure of this information, ask your system administrator.  If you do not specify a domain, the Remote Access server attempts to verify your user name and password on the domain of which it is a member.
692 Return to Top	Hardware failure in port or attached device	Your modem (or other connecting device) is not responding for one of the following reasons:  The modem has been turned off  The modem is not securely connected to your computer. Make sure your cable is securely fastened to both the modem and the computer.  The serial cable does not have the correct specifications required by Remote Access. See Cabling Requirements.  The modem has experienced a hardware glitch. Turn off the modem, wait for 20 seconds, and then restart it.
693 Return to Top	ERROR NOT BINARY MACRO	One of the Remote Access configuration files probably contains invalid information. The easiest way to resolve this problem is to reinstall Remote Access.  If you are using a modem that is not supported by Remote Access, switch to a supported modem, or see Overview of Modem Script File for information about modifying the modem script file for your modem.  The Remote Access script files (PAD.INF, MODEM.INF, and SWITCH.INF) are in the SYSTEM32RAS subdirectory of your Windows NT directory.
694 Return to Top	ERROR DCB NOT FOUND	This error should not occur under normal circumstances. Restart your computer to make sure that all recent configuration changes have taken effect. If the error persists, consult the Windows NT event log for detailed warnings or errors.
695 Return to Top	ERROR STATE MACHINES NOT STARTED	This error should not occur under normal circumstances. Restart your computer to make sure that all recent configuration changes have taken effect. If the error persists, consult the Windows NT event log for detailed warnings or errors.
696 Return to Top	ERROR STATE MACHINES ALREADY STARTED	This error should not occur under normal circumstances. Restart your computer to make sure that all recent configuration changes have taken effect. If the error persists, consult the Windows NT event log for detailed warnings or errors.
697 Return to Top	ERROR PARTIAL RESPONSE LOOPING	This error should not occur under normal circumstances. Restart your computer to make sure that all recent configuration changes have taken effect. If the error persists, consult the Windows NT event log for detailed warnings or errors.
698 Return to Top	A response keyname in the device.INF file is not in the expected format	One of the Remote Access configuration files probably contains invalid information. The easiest way to resolve this problem is to reinstall Remote Access.  If you are using a modem that is not supported by Remote Access, switch to a supported modem, or see Overview of Modem Script File for information about modifying the modem script file for your modem.  The Remote Access script files (PAD.INF, MODEM.INF, and SWITCH.INF) are in the SYSTEM32RAS subdirectory of your Windows NT directory.
699 Return to Top	The device response caused buffer overflow	This error should not occur under normal circumstances. Restart your computer to make sure that all recent configuration changes have taken effect. If the error persists, consult the Windows NT event log for detailed warnings or errors.
700 Return to Top	The expanded command in the device.INF is too long	The limit for commands in the script file is 256 characters. Break up the command into multiple commands. See Commands.
701 Return to Top	The device moved to a BPS rate not supported by the COM driver	Your modem tried to connect at a speed that the serial port cannot interpret. Reset your initial speed to the next lowest standard bps rate: 38400, 19200, 9600, 2400.
702 Return to Top	Device response received when none expected	One of the Remote Access configuration files probably contains invalid information. The easiest way to resolve this problem is to reinstall Remote Access.  If you are using a modem that is not supported by Remote Access, switch to a supported modem, or see Overview of Modem Script File for information about modifying the modem script file for your modem.  The Remote Access script files (PAD.INF, MODEM.INF, and SWITCH.INF) are in the SYSTEM32RAS subdirectory of your Windows NT directory.
703 Return to Top	ERROR INTERACTIVE MODE	You can connect to entries that require Terminal mode only through the Remote Access Phone Book. This feature is not supported by RASDIAL or the Remote Access APIs.
704 Return to Top	ERROR BAD CALLBACK NUMBER	This error should not occur under normal circumstances. Restart your computer to make sure that all recent configuration changes have taken effect. If the error persists, consult the Windows NT event log for detailed warnings or errors.
705 Return to Top	ERROR INVALID AUTH STATE	This error should not occur under normal circumstances. Restart your computer to make sure that all recent configuration changes have taken effect. If the error persists, consult the Windows NT event log for detailed warnings or errors.
706 Return to Top	ERROR WRITING INITBPS	This error should not occur under normal circumstances. Restart your computer to make sure that all recent configuration changes have taken effect. If the error persists, consult the Windows NT event log for detailed warnings or errors.
707 Return to Top	X.25 diagnostic indication	Your X.25 connection has returned an error. Ask your X.25 provider to interpret the diagnostic information provided.
708 Return to Top	The account has expired	Ask your system administrator to reactivate your account.
709 Return to Top	Error changing password on domain	Try changing your password again. If you still get this message, report it to your system administrator.
710 Return to Top	Serial overrun errors were detected while communicating with your modem	Lower the modem's initial speed (bits per second), and redial. For instructions about lowering the initial speed, see "Setting Modem Features" in online Help.
711 Return to Top	RasMan initialization failure. Check the event log	This error should not occur under normal circumstances. Restart your computer to make sure that all recent configuration changes have taken effect. If the error persists, consult the Windows NT event log for detailed warnings or errors.
712 Return to Top	Biplex port is initialization. Wait a few seconds and redial	This error can occur on a port configured for dialing out and receiving calls (biplex port). It happens when you dial out at the same time the server is initializing the port for receiving calls. Remote Access solves this problem for you by redialing in a few seconds.
713 Return to Top	No active ISDN lines are available	Make sure that your ISDN line is plugged in correctly, make sure that the terminating resistors are installed correctly (see the documentation for your ISDN card), and then redial. If you still get this error, contact your ISDN card vendor Customer Service or your ISDN telephone company.
714 Return to Top	Not enough ISDN channels are available to make the call	All of the available ISDN channels are busy. Hang up one call and redial.
715 Return to Top	Too many errors occurred because of poor phone line quality	Too many asynchronous errors occurred on your phone line during authentication. Try again. If the problem persists, lower your baud rate and disable any modem features that may be set. See "Setting Modem Features" and "Modem Idiosyncrasies" in the Phone Book online help.
716 Return to Top	The Remote Access IP configuration is unusable	This error indicates a problem with the Remote Access TCP/IP configuration. User should reboot to ensure all configuration changes have taken effect.
717 Return to Top	No IP addresses are available in the static pool of Remote Access IP addresses	Try a specific IP address that will not cause a conflict on the remote network.
718 Return to Top	PPP timeout	A PPP conversation was started, but was terminated because the remote computer did not respond within an appropriate time. This can be caused by poor line quality or by a problem at the server.
719 Return to Top	PPP terminated by remote machine	A PPP conversation was started, but was terminated at the request of the remote machine. Most likely an error occurred on the server.
720 Return to Top	No PPP control protocols configured	Either there are no PPP network control protocols configured for the entry or the corresponding network protocol is not installed. This error may occur when the type of network protocols is changed during the product upgrade process. Correct the entry by checking the desired protocols in the PPP section of the Network Protocol Settings phonebook entry dialog box. If you intentionally cleared all protocols to force a downlevel RAS connection, this error indicates the NetBEUI protocol used for down-level connections is not installed.
721 Return to Top	Remote PPP peer is not responding	PPP was attempted but the remote computers did not respond. This error occurs when the server does not support PPP, such as a down-level Remote Access server or a SLIP server.  The NetBEUI protocol must be installed to communicate with down-level Remote Access servers. The SLIP protocol must be selected for the entry and the TCP/IP protocol installed to communicate with SLIP servers. For more information, see Network Protocol Settings.  This error may also occur if the server requires a terminal-style log on before starting PPP. If the server requires a terminal-style log on, you can choose to use a terminal window in the Dial-Up Networking Script tab.  If terminal log on solves the problem, you can automate the terminal login for future connections by activating an After-dialing script by selecting one in the Dial-Up Networking Script tab.
722 Return to Top	The PPP packet is invalid	A PPP packet was received that was not in a valid format.
723 Return to Top	The phone number, including prefix and suffix, is too long	The maximum length of the phone number, including prefix and suffix, is 128 characters.
724 Return to Top	The IPX protocol cannot dial-out on the port because the computer is an IPX router	This is a beta limitation that will be removed for final release.
725 Return to Top	The IPX protocol cannot dial-in on the port because the IPX router is not installed	This indicates an inconsistency in the Remote Access IPX configuration. Reboot to ensure all configuration changes have taken effect.
726 Return to Top	The IPX protocol cannot be used for dial-out on more than one port at a time	Only one port can be used to dial out using the IPX protocol.
727 Return to Top	Cannot access TCPCFG.DLL	The TCPCFG.DLL is a required TCP/IP component. Ensure TCP/IP is installed correctly.
728 Return to Top	Cannot find an IP adapter bound to Remote Access	This error indicates a problem with the Remote Access TCP/IP configuration. Reboot to ensure all configuration changes have taken effect.
729 Return to Top	SLIP cannot be used unless the IP protocol is installed	Install TCP/IP using Control Panel.
730 Return to Top	Computer registration is not complete	A request for information on the status of computer registration was made before the information was available.
731 Return to Top	The protocol is not configured	Specific information was requested on a PPP control protocol that is not configured.
732 Return to Top	The PPP negotiation is not converging	The negotiation of PPP parameters did not succeed because the local and remote computers could not agree on a common set of parameters.
733 Return to Top	The PPP control protocol for this network protocol is not available on the server	The server supports PPP but does not support the client network protocol.
734 Return to Top	The PPP link control protocol terminated	A PPP link control protocol conversation was started, but was terminated at the request of the remote computer. Most likely an error occurred on the server.
735 Return to Top	The requested address was rejected by the server	The client is configured to request a specific IP address. The server is not configured to permit clients requesting specific IP addresses or the specific IP address may already be in use by another client.
736 Return to Top	The remote computer terminated the control protocol	A PPP network control protocol conversation was started, but was terminated at the request of the remote computer. Most likely an error occurred on the server.
737 Return to Top	Loopback detected	The local and remote computers involved in the PPP conversation are the same computer. This usually means a device (for example, a modem) on the link is echoing characters back. Try resetting these devices.  For other vendor's servers, it may indicate that the remote computer is attempting a teletypewriter (TTY) login before connecting. Configure this entry for a post-connect Terminal.
738 Return to Top	The server did not assign an address	The server was unable to assign an IP address to the client from the pool of addresses allocated. Try a specific IP address on the client that will not cause a conflict on the remote network.
739 Return to Top	The remote server cannot use the windows NT encryption password	This error will occur only when making a PPP connection to non-Microsoft Windows NT servers. The standard PPP authentication protocols, used for interoperating with third-party servers, require the password to be available in clear-text form, but Windows NT stores only the encrypted form for security.
740 Return to Top	The TAPI devices configured for Remote Access failed to initialize or were not installed correctly	The TAPI devices configured for Remote Access failed to initialize or were not installed correctly. Remove Remote Access and the TAPI devices then reinstall Remote Access and the TAPI devices.
741 Return to Top	The local computer does not support encryption	The Require Data Encryption check box is selected but the RAS driver does not have encryption capability. Clear the check box to use unencrypted connections.
742 Return to Top	The remote server does not support encryption	The Require Data Encryption check box is selected but the RAS server does not support data encryption. Clear the check box to use unencrypted connections or contact your system administrator.
743 Return to Top	The remote server requires encryption	The remote RAS server requires data encryption check box is selected but the local RAS client does not have encryption capability.
744 Return to Top	Cannot use the IPX net number assigned by the remote server. Checking event log	The IPX network number assigned to the client by the RAS server for the WAN interface is already in use on the client's LAN.  Disconnect the client from the LAN, wait 3 minutes, and try again.
752 Return to Top	A syntax error was encountered while processing a script	The dial-up script associated with a phonebook entry contains a syntax error.  In Dial-Up Networking, edit the phonebook entry. In the Script tab, click Edit scripts.