Error code Network and Dial-up Connections
600 An operation is pending
600 An internal error occurred. Restart your computer to make sure that all recent configuration changes have taken effect.
601 An invalid port handle was detected
601 An internal error occurred. Restart your computer to make sure that all recent configuration changes have taken effect.
602 The specified port is already open
602 The COM port that the network connection attempted to use is already in use by another active network connection or another process (for example, a phone line monitoring program, such as a fax program). Quit the application that is blocking the use of the COM port.
603 The caller's buffer is too small
603 An internal error occurred. Restart your computer to make sure that all recent configuration changes have taken effect.
604 Incorrect information was specified
604 The remote access phonebook file and the current Network and Dial-up Connections configuration are probably inconsistent. If you changed your communications equipment (such as your serial port or modem), make sure you reconfigure Network and Dial-up Connections. See To configure a connection.
605 The port information cannot be set
605 The remote access phonebook file and the current Network and Dial-up Connections configuration are probably inconsistent. If you changed your communications equipment (such as your serial port or modem), make sure you reconfigure Network and Dial-up Connections. See To configure a connection.If the error persists, delete and re-create the connection in Network and Dial-up Connections.
606 The specified port is not connected
606 An internal error occurred. Restart your computer to make sure that all recent configuration changes have taken effect.
607 An invalid event is detected
607 An internal error occurred. Restart your computer to make sure that all recent configuration changes have taken effect.
608 A device was specified that does not exist
608 The remote access phonebook file and the current Network and Dial-up Connections configuration are probably inconsistent. If you changed your communications equipment (such as your serial port or modem), make sure you reconfigure Network and Dial-up Connections. See To configure a connection.If the error persists, delete and re-create the connection in Network and Dial-up Connections.
609 The device type was specified that does not exist
609 The remote access phonebook file and the current Network and Dial-up Connections configuration are probably inconsistent. If you changed your communications equipment (such as your serial port or modem), make sure you reconfigure Network and Dial-up Connections. See To configure a connection.If the error persists, delete and re-create the connection in Network and Dial-up Connections.
610 An invalid buffer was specified
610 An internal error occurred. Restart your computer to make sure that all recent configuration changes have taken effect.
611 A route was specified that is not available
611 Your network configuration is probably incorrect. Restart your computer to make sure that all recent configuration changes have taken effect. If the error persists, consult the Windows 2000 event log for detailed warnings or errors.
612 A route was specified that is not allocated
612 Your network configuration is probably incorrect. Restart your computer to make sure that all recent configuration changes have taken effect. This error may also occur if your computer is running low on resources. If the error persists, consult the Windows 2000 event log for detailed warnings or errors.
613 An invalid compression was specified
613 An internal error occurred. Restart your computer to make sure that all recent configuration changes have taken effect.
614 There were insufficient buffers available
614 An internal error occurred. Restart your computer to make sure that all recent configuration changes have taken effect. If the error persists, consult the Windows 2000 event log for detailed warnings or errors.
615 The specified port was not found
615 The remote access phonebook file and the current Network and Dial-up Connections configuration are probably inconsistent. If you changed your communications equipment (such as your serial port or modem), make sure you reconfigure Network and Dial-up Connections. See To configure a connection.If the error persists, delete and re-create the connections in Network and Dial-up Connections.
616 An asynchronous request is pending
616 An internal error occurred. Restart your computer to make sure that all recent configuration changes have taken effect.
617 The modem is already disconnecting
617 Wait for Network and Dial-up Connections to finish disconnecting.
618 The specified port is not open
618 An internal error occurred. Restart your computer to make sure that all recent configuration changes have taken effect.
619 The specified port is not connected
619 Restart your computer to make sure that all recent configuration changes have taken effect.
620 No endpoints could be determined
620 Your network configuration is probably incorrect. Restart your computer to make sure that all recent configuration changes have taken effect. If the error persists, consult the Windows 2000 event log for detailed warnings or errors.
621 The system could not open the phonebook
621 Network and Dial-up Connections uses the Rasphone.pbk file located in the systemroot \System32\Ras folder. Make sure the file is in this folder, and then restart Network and Dial-up Connections.
622 The system could not load the phonebook
622 Network and Dial-up Connections uses the Rasphone.pbk file located in the systemroot \System32\Ras folder. Make sure the file is in this folder, and then restart Network and Dial-up Connections.
623 The system could not find the phonebook entry for this connection
623 Network and Dial-up Connections located the phone book, but cannot find the specified connection entry. This error should not occur unless another application is using the Network and Dial-up Connections phone book and has specified an incorrect connection entry.
624 The system could not update the phonebook file
624 Network and Dial-up Connections uses the Rasphone.pbk file located in the systemroot \System32\Ras folder. Make sure your disk is not full and that you have permission to change this file.
625 The system found invalid information in the phonebook
625 The phonebook file, Rasphone.pbk, may be corrupt. Delete this file from the systemroot \System32\Ras folder, and then restart Network and Dial-up Connections to create a new one.
626 A string could not be loaded
626 An internal error occurred. Restart your computer to make sure that all recent configuration changes have taken effect. If the error persists, consult the Windows 2000 event log for detailed warnings or errors.
627 A key could not be found
627 One of the Network and Dial-up Connections configuration files probably contains invalid information. If you are using a modem that is not supported by Windows 2000, install a supported modem.
628 The connection was closed
628 If this is a dial-up connection, redial the connection. If you continue to get this message, reduce the modem's initial speed, and turn off the advanced modem features. See To change the maximum modem port speed. If the problem persists, contact your system administrator.If this is a virtual private network (VPN) connection, access may be denied because of a remote access policy or some other authentication issue. See your system administrator.
629 The connection was closed by the remote computer
629 The connection link disconnected for one of the following reasons:
- An unrecoverable phone line error.
- A noisy line.
- Disconnection by the system administrator.
- Failure to negotiate correctly with the modem on the remote access server at the selected speed.
To reestablish the connection, click Redial . You can also enable automatic redialing on the Options tab for the connection. If this error persists, reduce the modem speed for the connection to 9600 bps, and then try to redial. See To change the maximum modem port speed.You can try to connect to another server to determine if the problem is related to the particular remote access server you are calling. Also, you can try connecting to the original server from another phone line.
630 The modem was disconnected due to hardware failure
630 The link disconnected for one of the following reasons:
- An unrecoverable error occurred in your modem (or other communication device).
- An unrecoverable error occurred on your communications port.
- Your modem cable is unplugged.
To diagnose and correct the problem, do the following:
- Make sure your modem is on and your cable is securely attached.
- Make sure your modem is functioning properly. For instructions on testing your modem, see To test a modem.
631 The user disconnected the modem
631 An action on your computer disconnected the line. Redial.
632 An incorrect structure size was detected
632 An internal error occurred. Restart your computer to make sure that all recent configuration changes have taken effect. If the error persists, consult the Windows 2000 event log for detailed warnings or errors.
633 The modem is already in use or is not configured for dialing out
633 If this is a dial-up connection, the COM port that the network connection attempted to use is already in use by another active network connection or another process (for example, a phone line monitoring program, such as a fax program). Quit the application that is blocking the use of the COM port.If this is a virtual private network (VPN) connection, the VPN device that the network connection attempted to use cannot be opened. If the problem persists, see your system administrator.
634 Your computer could not be registered on the remote network
634 The remote access server cannot register the name of your computer on the network. This generally occurs with the NetBIOS protocol, but it may also occur with TCP/IP or IPX protocols. Typically, the error occurs when an address is already in use on the network. Contact your system administrator.
635 There was an unknown error
635 An internal error occurred. Restart your computer to make sure that all recent configuration changes have taken effect. If the error persists, consult the Windows 2000 event log for detailed warnings or errors.
636 The device attached to the port is not the one expected
636 Your hardware configuration and the configuration settings for your connection are probably inconsistent with each other. If you changed your communications equipment (such as a serial port or modem), make sure you reconfigure the connection. See To configure a connection.
637 A string was detected that could not be converted
637 An internal error occurred. Restart your computer to make sure that all recent configuration changes have taken effect.
638 The request has timed out
638 An internal error occurred. Restart your computer to make sure that all recent configuration changes have taken effect.
639 No asynchronous net is available
639 Your NetBIOS network configuration is probably incorrect. Restart your computer to make sure that all recent configuration changes have taken effect. If the error persists, consult the Windows 2000 event log for detailed warnings or errors.If you call for help, record the Fail Code (a NetBIOS error code) and give it to the technical support staff.
640 A error has occurred involving NetBIOS
640 The modem cannot negotiate a connection at the speed that is set. Set the modem to a lower initial speed, and then redial. See To change the maximum modem port speed. Also, try disabling modem compression and software compression. See To configure a modem for a dial-up connection or To disable software compression.If you still cannot make a connection, try adding the NWLink IPX/SPX/NetBIOS Compatible Transport Protocol to the connection. See To add a network component.
641 The server cannot allocate NetBIOS resources needed to support the client
641 Ask your system administrator to increase the resource capacity of the remote access server, or use Services in Computer Management to stop nonessential services on your computer, such as Messenger and Network DDE.
642 One of your computer's NetBIOS names is already registered on the remote network
642 Another computer with the same computer name is already logged on to the remote network. Each computer on the network must be registered with a unique name. Verify the following:
- A computer with the same computer name as yours is not located on the network you are connecting to.
- Your computer is not already physically attached to the network that you are attempting to connect to.
643 A network adapter at the server failed
643 Report this error to your system administrator.
644 You will not receive network message popups
644 Another computer that is already connected to the network is using your messaging name. Messages addressed to you are 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 dial in to the network the next time.This error does not affect messaging through Microsoft Outlook, Microsoft Outlook Express, or Microsoft Exchange.
645 There was an internal authentication error
645 An internal error occurred. Restart your computer to make sure that all recent configuration changes have taken effect.
646 The account is not permitted to log on at this time of day
646 Your account is configured for limited access to the network. If you need to access the network at a different time of day than what is presently configured, ask your system administrator to change the configuration
647 The account is disabled
647 The user account is disabled. This may be due to repeated failed logon attempts or because the system administrator disabled the account for security reasons. Ask your system administrator to enable your account in Local Users and Groups.
648 The password for this account has expired
648 If you connect through Network and Dial-up Connections, you are automatically prompted to change your password. If you connect by using the rasdial command, you can change your password by doing the following:
- Press CTRL+ALT+DEL.
- Click Change Password , and then follow the instructions on the screen.
If you belong to an administrators group and your password expires, another administrator must change your password. You cannot change the password yourself.
649 The account does not have permission to dial in
649 The account does not have permission to dial in for one of the following reasons:
- 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 enable dial-in permission for your user account, or enable dial-in permission in Routing and Remote Access.
- Your account has either expired, been disabled, or is locked out, or your dial-in access has been locked out.
- You are either attempting to connect outside of allowable server logon hours, attempting to connect outside of the times allowed for dial-in access, or the policy that applies to your account may not allow dial-in access.
- A caller ID rule may prevent you from connecting. For example, your account may be required to dial in from a specific number.
- The remote computer may only allow local accounts to connect.
- An authentication protocol may be required that your computer cannot negotiate, or your computer may be attempting to use a protocol that is not authorized by the policy on the remote computer.
If you have an account with dial-in permission on another domain, do the following to use your account on that domain:1. Right-click the connection, and then click Properties .2. On the Options tab, select the Prompt for name and password, certificate, etc. and Include Windows logon domain check boxes.3. On the Security tab, clear the Automatically use my Windows logon name and password (and domain if any) check box, and then click OK .4. Double-click the connection, and then click Dial .5. Specify the appropriate user name, password, and domain.
650 The remote access server is not responding
650 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, or your modem may have failed to negotiate correctly with the modem of the remote access server at the selected speed. For either of these possibilities, lower the initial speed (bps) of the modem, and then redial. See To change the maximum modem port speed.
- Check the Hardware Compatibility List to make sure that your modem is listed. For the most up-to-date list of supported modems, see the Hardware Compatibility List at the Microsoft Web site (http://www.microsoft.com) Your Windows 2000 CD includes a copy of this list ( drive: \Support\hcl.txt) that was accurate as of the date Windows 2000 was released. If your modem is listed, contact the modem manufacturer to see if an updated Modem.inf file is available.
- The modem's serial cable may need replacing.
- The authentication settings for the connection may be incorrect. Contact your system administrator to make sure that your authentication settings meet those required by the remote access server.
- The software compression and modem hardware compression for the remote access server may be enabled at the same time. Generally, the remote access server software compression is enabled and hardware compression is disabled.
651 The modem has reported an error
651 Your modem (or other device) reported an error.If this is a dial-up connection, and you are using a supported external modem, turn off and then restart the modem. Close and restart Network and Dial-up Connections, and then redial. If your modem is not supported by Network and Dial-up Connections, switch to a supported modem. For the most up-to-date list of supported modems, see the Hardware Compatibility List at the Microsoft Web site (http://www.microsoft.com/). Your Windows 2000 CD includes a copy of this list ( drive: \Support\hcl.txt) that was accurate as of the date Windows 2000 was released. Make sure you correctly configured your modem for remote access. To check your configuration, see To configure a connection.If this is a virtual private network (VPN) connection, you may have specified an incorrect TCP/IP address in the connection configuration, or the server that you are trying to reach may not be available. To determine if the server is available, see your system administrator.
652 There was an unrecognized response from the modem
652 Your modem (or other device) returned a message that is not listed in one or more of your script files (Pad.inf, Switch.inf, or filename .scp).If you are using a supported external modem, turn off and restart the modem, and then redial.If the problem persists, try connecting at a lower initial speed. See To change the maximum modem port speed.For the most up-to-date list of supported modems, see the Hardware Compatibility List at the Microsoft Web site (http://www.microsoft.com/). Your Windows 2000 CD includes a copy of this list ( drive: \Support\hcl.txt) that was accurate as of the date Windows 2000 was released.
653 A macro required by the modem was not found in the device .INF file section
653 One of the Network and Dial-up Connections configuration files probably contains information that is not valid.If your modem is not supported by Network and Dial-up Connections, switch to a supported modem. For the most up-to-date list of supported modems, see the Hardware Compatibility List at the Microsoft Web site (http://www.microsoft.com/). Your Windows 2000 CD includes a copy of this list ( drive: \Support\hcl.txt) that was accurate as of the date Windows 2000 was released.
654 A command or response in the device .INF file section refers to an undefined macro
654 One of the Network and Dial-up Connections configuration files probably contains information that is not valid.If your modem is not supported by Network and Dial-up Connections, switch to a supported modem. For the most up-to-date list of supported modems, see the Hardware Compatibility List at the Microsoft Web site (http://www.microsoft.com/). Your Windows 2000 CD includes a copy of this list ( drive: \Support\hcl.txt) that was accurate as of the date Windows 2000 was released.
655 The <MESSAGE> macro was not found in the device .INF file section
655 One of the Network and Dial-up Connections configuration files probably contains information that is not valid.If your modem is not supported by Network and Dial-up Connections, switch to a supported modem. For the most up-to-date list of supported modems, see the Hardware Compatibility List at the Microsoft Web site (http://www.microsoft.com/). Your Windows 2000 CD includes a copy of this list ( drive: \Support\hcl.txt) that was accurate as of the date Windows 2000 was released.
656 The <DEFAULTOFF> macro in the device .INF file section contains an undefined macro
656 One of the Network and Dial-up Connections configuration files probably contains information that is not valid.If your modem is not supported by Network and Dial-up Connections, switch to a supported modem. For the most up-to-date list of supported modems, see the Hardware Compatibility List at the Microsoft Web site (http://www.microsoft.com/). Your Windows 2000 CD includes a copy of this list ( drive: \Support\hcl.txt) that was accurate as of the date Windows 2000 was released.
657 The device .INF file could not be opened
657 One of the Network and Dial-up Connections configuration files probably contains information that is not valid.If your modem is not supported by Network and Dial-up Connections, switch to a supported modem. For the most up-to-date list of supported modems, see the Hardware Compatibility List at the Microsoft Web site (http://www.microsoft.com/). Your Windows 2000 CD includes a copy of this list ( drive: \Support\hcl.txt) that was accurate as of the date Windows 2000 was released.
658 The device name in the device .INF or media .INI file is too long
658 One of the Network and Dial-up Connections configuration files probably contains information that is not valid.If your modem is not supported by Network and Dial-up Connections, switch to a supported modem. For the most up-to-date list of supported modems, see the Hardware Compatibility List at the Microsoft Web site (http://www.microsoft.com/). Your Windows 2000 CD includes a copy of this list ( drive: \Support\hcl.txt) that was accurate as of the date Windows 2000 was released.
659 The media .INI file refers to an unknown device name
659 One of the Network and Dial-up Connections configuration files probably contains information that is not valid.If your modem is not supported by Network and Dial-up Connections, switch to a supported modem. For the most up-to-date list of supported modems, see the Hardware Compatibility List at the Microsoft Web site (http://www.microsoft.com/). Your Windows 2000 CD includes a copy of this list ( drive: \Support\hcl.txt) that was accurate as of the date Windows 2000 was released.
660 The device .INF file contains no responses for the command
660 One of the Network and Dial-up Connections configuration files probably contains information that is not valid.If your modem is not supported by Network and Dial-up Connections, switch to a supported modem. For the most up-to-date list of supported modems, see the Hardware Compatibility List at the Microsoft Web site (http://www.microsoft.com/). Your Windows 2000 CD includes a copy of this list ( drive: \Support\hcl.txt) that was accurate as of the date Windows 2000 was released.
661 The device .INF file is missing a command
661 One of the Network and Dial-up Connections configuration files probably contains information that is not valid.If your modem is not supported by Network and Dial-up Connections, switch to a supported modem. For the most up-to-date list of supported modems, see the Hardware Compatibility List at the Microsoft Web site (http://www.microsoft.com/). Your Windows 2000 CD includes a copy of this list ( drive: \Support\hcl.txt) that was accurate as of the date Windows 2000 was released.
662 there was an attempt to set a macro not listed in the device .INF file section
662 One of the Network and Dial-up Connections configuration files probably contains information that is not valid.If your modem is not supported by Network and Dial-up Connections, switch to a supported modem. For the most up-to-date list of supported modems, see the Hardware Compatibility List at the Microsoft Web site (http://www.microsoft.com/). Your Windows 2000 CD includes a copy of this list ( drive: \Support\hcl.txt) that was accurate as of the date Windows 2000 was released.
663 The media .INI file refers to an unknown device type
663 One of the Network and Dial-up Connections configuration files probably contains information that is not valid.If your modem is not supported by Network and Dial-up Connections, switch to a supported modem. For the most up-to-date list of supported modems, see the Hardware Compatibility List at the Microsoft Web site (http://www.microsoft.com/). Your Windows 2000 CD includes a copy of this list ( drive: \Support\hcl.txt) that was accurate as of the date Windows 2000 was released.
664 The system has run out of memory
664 The system is out of memory. Close some programs, and then redial.
665 The modem is not properly configured
665 If the device is already being used for another connection, hang up that connection.Modify the connection to use another device. See To configure a connection.
666 The modem is not functioning
666 Your modem (or other device) is not responding for one of the following reasons:
- The external modem is turned off.
- The modem is not securely connected to your computer. Make sure the cable is securely fastened to both the modem and the computer.
- The serial cable does meet the specifications required by Network and Dial-up Connections.
- The modem has experienced a hardware problem. Turn off the modem, wait for 20 seconds, and then restart the modem.
667 The system was unable to read the media .INI file
667 One of the Network and Dial-up Connections configuration files probably contains information that is not valid.If your modem is not supported by Network and Dial-up Connections, switch to a supported modem. For the most up-to-date list of supported modems, see the Hardware Compatibility List at the Microsoft Web site (http://www.microsoft.com/). Your Windows 2000 CD includes a copy of this list ( drive: \Support\hcl.txt) that was accurate as of the date Windows 2000 was released.
668 The connection was terminated
668 Redial the connection. If you continue to receive this message, reduce the modem's initial speed and turn off advanced modem features, such as software compression. See To change the maximum modem port speed or To disable software compression. If the problem persists, contact your system administrator.Also, you should confirm that the modem is compatible. For the most up-to-date list of supported modems, see the Hardware Compatibility List at the Microsoft Web site (http://www.microsoft.com/). Your Windows 2000 CD includes a copy of this list ( drive: \Support\hcl.txt) that was accurate as of the date Windows 2000 was released.If you are dialing manually, make sure you are connected before you click Done . You are dialing manually if you selected Operated-Assisted Dialing on the Advanced menu in the Network and Dial-up Connections folder.
669 The usage parameter in the media .INI file is invalid
669 One of the Network and Dial-up Connections configuration files probably contains information that is not valid.If your modem is not supported by Network and Dial-up Connections, switch to a supported modem. For the most up-to-date list of supported modems, see the Hardware Compatibility List at the Microsoft Web site (http://www.microsoft.com/). Your Windows 2000 CD includes a copy of this list ( drive: \Support\hcl.txt) that was accurate as of the date Windows 2000 was released.
670 The system was unable to read the section name from the media .INI file
670 One of the Network and Dial-up Connections configuration files probably contains information that is not valid.If your modem is not supported by Network and Dial-up Connections, switch to a supported modem. For the most up-to-date list of supported modems, see the Hardware Compatibility List at the Microsoft Web site (http://www.microsoft.com/). Your Windows 2000 CD includes a copy of this list ( drive: \Support\hcl.txt) that was accurate as of the date Windows 2000 was released.
671 The system was unable to read the device type from the media .INI file
671 One of the Network and Dial-up Connections configuration files probably contains information that is not valid.If your modem is not supported by Network and Dial-up Connections, switch to a supported modem. For the most up-to-date list of supported modems, see the Hardware Compatibility List at the Microsoft Web site (http://www.microsoft.com/ ). Your Windows 2000 CD includes a copy of this list ( drive: \Support\hcl.txt) that was accurate as of the date Windows 2000 was released.
672 The system was unable to read the device name from the media .INI file
672 One of the Network and Dial-up Connections configuration files probably contains information that is not valid.If your modem is not supported by Network and Dial-up Connections, switch to a supported modem. For the most up-to-date list of supported modems, see the Hardware Compatibility List at the Microsoft Web site (http://www.microsoft.com/). Your Windows 2000 CD includes a copy of this list ( drive: \Support\hcl.txt) that was accurate as of the date Windows 2000 was released.
673 The system was unable to read the usage from the media .INI file
673 One of the Network and Dial-up Connections configuration files probably contains information that is not valid.If your modem is not supported by Network and Dial-up Connections, switch to a supported modem. For the most up-to-date list of supported modems, see the Hardware Compatibility List at the Microsoft Web site (http://www.microsoft.com/). Your Windows 2000 CD includes a copy of this list ( drive: \Support\hcl.txt) that was accurate as of the date Windows 2000 was released.
674 The system was unable to read the maximum connection BPS rate from the media .INI file
674 One of the Network and Dial-up Connections configuration files probably contains information that is not valid.If your modem is not supported by Network and Dial-up Connections, switch to a supported modem. For the most up-to-date list of supported modems, see the Hardware Compatibility List at the Microsoft Web site (http://www.microsoft.com/). Your Windows 2000 CD includes a copy of this list ( drive: \Support\hcl.txt) that was accurate as of the date Windows 2000 was released.
675 The system was unable to read the maximum carrier connection speed from the media .INI file
675 One of the Network and Dial-up Connections configuration files probably contains information that is not valid.If your modem is not supported by Network and Dial-up Connections, switch to a supported modem. For the most up-to-date list of supported modems, see the Hardware Compatibility List at the Microsoft Web site ( http://www.microsoft.com/). Your Windows 2000 CD includes a copy of this list ( drive: \Support\hcl.txt) that was accurate as of the date Windows 2000 was released.
676 The phone line is busy
676 Redial the number. You can automate redialing on the Options tab in the properties of the connection. See Configuring Redial Settings. If this is a virtual private network (VPN) connection, check the host name or IP address of your destination server, and try to connect again. Also, contact your system administrator to verify that the remote server is running.
677 A person answered instead of a modem
677 A modem or other device did not pick up the phone. Check the number and dial again. If this is a virtual private network (VPN) connection, check the host name or IP address of your destination server, and try to connect again.
678 There was no answer
678 A modem or other device did not pick up the phone. Check the number and dial again. If this is a virtual private network (VPN) connection, check the host name or IP address of your destination server, and try to connect again. Also, make sure that the phone line is plugged into the correct socket in the modem.
679 The system could not detect the carrier
679 A modem or other device did not pick up the phone. Many modems return this error if the remote modem does not pick up the phone. Check the number and dial again. If this is a virtual private network (VPN) connection, check the host name or IP address of your destination server, and try to connect again. You can automate redialing on the Options tab in the properties of the connection. See Configuring Redial Settings.
680 There was no dial tone
680 A phone line may be incorrectly connected to your modem or disconnected from your modem. The number may require a prefix, such as 9, to access external lines, or the number may be too long.Make sure that the phone line is plugged into the correct socket in the modem. Also, make sure you added any special access numbers, such as the prefix 9 followed by a comma, to connect to an outside line. For example: 9,555-0100. For more information, see To configure phone number modifiers.Check that there is no stutter tone, which indicates voicemail messages, on your phone line.Many modems cannot dial more than 34 digits. When longer numbers are encountered, these modems split them into two or more strings, of which only the first (incomplete) string is dialed. This occurs with USRobotics and Multitech modems. The only known solution for this problem is to use another brand of modem.For more information, see the Personal Support Center at the Microsoft Web site ( http://www.microsoft.com/).
681 The modem reported a general error
681 One of the Network and Dial-up Connections configuration files probably contains information that is not valid.If your modem is not supported by Network and Dial-up Connections, switch to a supported modem. For the most up-to-date list of supported modems, see the Hardware Compatibility List at the Microsoft Web site (http://www.microsoft.com/). Your Windows 2000 CD includes a copy of this list ( drive: \Support\hcl.txt) that was accurate as of the date Windows 2000 was released.
691 Access was denied because the user name and/or password was invalid on the domain
691 Either your user account is not registered with the domain listed, your password is expired, or you mistyped the information. 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.Carefully retype your user name, password, and domain. If you are unsure of this information, ask your system administrator.
692 There was a hardware failure in the modem
692 Your modem (or other device) is not responding because of the following:
- The modem is either turned off, malfunctioning, or is not securely connected to your computer.To resolve this problem, do the following:
- Reset your modem. For more information, consult your hardware documentation.
- If you are using an external modem, ensure that you are using a proper serial cable, and that it is connected securely. You may want to try replacing the modem cable. Also, if you are using an adapter to connect your external modem to your serial port, ensure that the adapter is wired properly for modem communication. For example, a 9-to-25 pin adapter for a mouse does not work properly with a serial network connection.
- Test the serial port or multiport adapter, and replace it if necessary.
- Ensure that the handshaking options for the modem are configured properly. Consult your hardware documentation for information about different handshaking options available for your modem.
- If your modem is not supported by Network and Dial-up Connections, switch to a supported modem. For the most up-to-date list of supported modems, see the Hardware Compatibility List at the Microsoft Web site (http://www.microsoft.com/). Your Windows 2000 CD includes a copy of this list ( drive: \Support\hcl.txt) that was accurate as of the date Windows 2000 was released.
- Verify that another application, such as HyperTerminal, is not using the communications port. If the port is being used, subsequently starting Network and Dial-up Connections may cause this message to appear.
- For more information, see the Personal Support Center at the Microsoft Web site (http://www.microsoft.com/).
695 The state machines are not started
695 An internal error occurred. Restart your computer to make sure that all recent configuration changes have taken effect.
696 The state machines are already started
696 An internal error occurred. Restart your computer to make sure that all recent configuration changes have taken effect.
697 The response looping did not complete
697 An internal error occurred. Restart your computer to make sure that all recent configuration changes have taken effect.
699 The modem response caused a buffer overflow
699 An internal error occurred. Restart your computer to make sure that all recent configuration changes have taken effect.
700 The expanded command in the device .INF file is too long
700 Commands in script files cannot exceed 256 characters. Break up the command into multiple commands. See Automating the dial-up logon process by using Windows scripting or Automating the dial-up logon process by using Switch.inf scripts.
701 The modem moved to a connection speed not supported by the COM driver
701 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. See To change the maximum modem port speed.
703 The connection needs information from you, but the application does not allow user interaction
703 The server you are attempting to connect to requires user interaction. The rasdial command, or the application you are using that is attempting to dial, does not support user interaction.If possible, try to connect by using an existing connection in the Network and Dial-up Connections folder.If you are using scripting to connect, try using a dial-up connection that is configured with the Terminal feature. The terminal window may enable the user interaction that is required. See To use the Terminal feature to log on to a remote computer.
704 The callback number is invalid
704 The callback number that you specified for the client is not valid.
705 The authorization state is invalid
705 An internal error occurred. Restart your computer to make sure that all recent configuration changes have taken effect. If the error persists, consult the Windows 2000 event log for detailed warnings or errors.
707 There was an error related to the X.25 protocol
707 The X.25 connection returned an error. Ask your X.25 provider to interpret the diagnostic information that is provided.
708 The account has expired
708 Ask your system administrator to reactivate your account.
709 There was an error changing the password on the domain. The password might have been too short or might have matched a previously used password
709 Try changing your password again. If you continue to receive this message, report it to your system administrator.
710 Serial overrun errors were detected while communicating with the modem
710 Lower the modem's initial speed (bits per second), and then redial. See To change the maximum modem port speed.
711 The Remote Access Service Manager could not start. Additional information is provided in the event log
711 The Remote Access Connection Manager service may not be running. Modify the service to start automatically. See To configure how a service is started.Restart your computer to ensure that all recent configuration changes have taken effect. If the error persists, consult the Windows 2000 event log for detailed warnings or errors. See the Personal Support Center at the Microsoft Web site (http://www.microsoft.com/) for more information.Your modem, or modem cable, may be causing a problem. Confirm that your modem is supported. For the most up-to-date list of supported modems, see the Hardware Compatibility List at the Microsoft Web site (http://www.microsoft.com/). Your Windows 2000 CD includes a copy of this list ( drive: \Support\hcl.txt) that was accurate as of the date Windows 2000 was released.Try replacing the modem cable.
712 The two-way port is initializing. Wait a few seconds and redial
712 This error can occur on a connection that is configured to receive calls (biplex connection). It happens when you dial out at the same time the server is initializing the connection for receiving calls. Network and Dial-up Connections redials in a few seconds.
713 No active ISDN lines are available
713 Make sure that your ISDN line is plugged in correctly and that the terminating resistors are installed correctly (see the documentation for your ISDN card), and then redial. If you still receive this error, contact customer service for the ISDN card vendor or your ISDN telephone company.
714 No ISDN channels are available to make the call
714 All of the available ISDN channels are busy. Typically, ISDN provided in the BRI (Basic Rate Interface) level of service offers two channels on which voice or data calls can be made. If both channels are in use, Network and Dial-up Connections is not able to dial out. Hang up one channel and then redial.
715 Too many errors occurred because of poor phone line quality
715 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 are set. See To change the maximum modem port speed and To configure an installed modem.
716 The remote access service IP configuration is unusable
716 There is a problem with the TCP/IP configuration on the remote access server. For example, your connection is requesting a TCP/IP address from the server that is not usable.Contact your system administrator to verify the TCP/IP settings on your server.
717 No IP addresses are available in the static pool of remote access service IP addresses
717 Try to use an IP address that does not cause a conflict on the remote network. If possible, use DHCP to avoid addressing conflicts. See To configure TCP/IP settings.
718 The connection timed out waiting for a valid response from the remote computer
718 A PPP conversation started, but terminated because the remote computer did not respond within an appropriate time. This may be caused by poor line quality or by a problem at the server.
719 The connection was terminated by the remote computer
719 A PPP conversation started, but terminated at the request of the remote computer. An error probably occurred on the server.
720 The connection attempt failed because your computer and the remote computer could not agree on PPP control protocols
720 Either there are no PPP network control protocols configured for your connection, or the corresponding network protocol is not installed. This error may occur when the type of network protocol is changed during the product upgrade process.For information about adding a network protocol, see To add a network component.
721 The remote computer is not responding
721 A PPP conversation was attempted, but the remote computer did not respond. This error occurs when the server does not support PPP, such as a Windows NT 3.51 or earlier remote access server, or a SLIP server.This error may also occur if the server requires logging on by using a terminal window before starting PPP. See To use the Terminal feature to log on to a remote computer. If using a terminal window to log on solves the problem, you can automate the process for future connections. See Automating the dial-up logon process by using Windows scripting.This error can also indicate faulty hardware on your computer, or the remote server.
722 Invalid data was received from the remote computer. This data was ignored
722 A PPP packet was received that is not in a valid format. Your system administrator may need to log PPP events to a file to solve the problem. For more information, see the Personal Support Center at the Microsoft Web site (http://www.microsoft.com/).
723 The phone number, including prefix and suffix, is too long
723 The maximum length of the phone number, including prefix and suffix, is 128 characters.
726 The IPX protocol cannot be used for dial-out on more than one modem at a time
726 Only one connection can be used to dial out by using the IPX protocol.
728 The system cannot find an IP adapter
728 There is a problem with the TCP/IP configuration. Restart your computer to ensure that all recent configuration changes have taken effect.
729 SLIP cannot be used unless the IP protocol is installed
729 Verify that TCP/IP is installed. For more information, see To add a network component.
731 The protocol is not configured
731 Specific information was requested on a PPP control protocol that is not configured. To identify the PPP negotiation problem, ask your system administrator to enable PPP logging by using the Netsh.exe utility.
732 Your computer and the remote computer could not agree on PPP control protocols
732 PPP parameter negotiation did not succeed because the local and remote computers did not agree on a common set of parameters. See your system administrator to verify the configuration of network protocols such as TCP/IP, IPX, or NetBEUI. Also, your system administrator can enable PPP logging by using the Netsh.exe utility, which may help identify the PPP negotiation problem.
733 Your computer and the remote computer could not agree on PPP control protocols
733 The server supports PPP but does not support the network protocol for your connection. Ask your system administrator to configure the connection to use a network protocol that is supported by your server. Also, your system administrator can enable PPP logging by using the Netsh.exe utility, which may help to identify the PPP negotiation problem.
734 The PPP link control protocol was terminated
734 A PPP link control protocol conversation started, but terminated at the request of the remote computer. An error probably occurred on the server. See your system administrator. Also, your system administrator can enable PPP logging by using the Netsh.exe utility, which may help to identify the PPP negotiation problem.
735 The requested address was rejected by the server
735 Your connection is configured to request a specific IP address. Either the server is not configured to permit clients that request specific IP addresses, or the specific IP address may already be in use by another client. If possible, use DHCP to avoid addressing conflicts. See To configure TCP/IP settings.
736 The remote computer terminated the control protocol
736 A PPP network control protocol conversation started, but terminated at the request of the remote computer. An error probably occurred on the server. See your system administrator. Also, your system administrator can enable PPP logging by using the Netsh.exe utility, which may help to identify the PPP negotiation problem.
737 Loopback detected
737 The local and remote computers that are involved in the PPP conversation are the same computer. This usually means that 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. You can configure the connection for a post-connect terminal on the Security tab.
738 The server did not assign an address
738 The server cannot assign an IP address to your computer from the pool of allocated addresses. Ask your system administrator to configure the connection to use a specific IP address on the client that does not cause a conflict on the remote network. Or, if possible, use DHCP to avoid addressing conflicts. See To configure TCP/IP settings.
739 The authentication protocol required by the remote server cannot use the stored password. Redial, entering the password explicitly
739 This error occurs only when making a PPP connection to a non-Microsoft server. The standard PPP authentication protocols, used for interoperating with other servers, require that the password is available in plaintext form, but Windows stores only the encrypted form for security.
740 An invalid dialing rule was detected
740 The TAPI devices configured for Network and Dial-up Connections failed to initialize or are not installed correctly. Restart your computer to make sure that all recent configuration changes have taken effect. If the error persists, consult the event log for detailed warnings or errors.
741 The local computer does not support the required data encryption type
741 The Require data encryption (disconnect if none) check box is selected on the Security tab, but your connection does not have encryption capability. Clear the check box to use unencrypted connections or see your system administrator.This error may also occur if your password is longer than 14 characters, you selected the Require data encryption (disconnect if none) check box on the Security tab, and you selected Require secured password in Validate my identity as follows . Use a password less than 14 characters, clear the Require data encryption (disconnect if none) check box, and click Allow unsecured password in Validate my identity as follows .See To configure a connection.
742 The remote computer does not support the required data encryption type
742 The required level of encryption is not available on the remote computer. One computer is probably using 128-bit encryption technology while the other is using 40-bit or 56-bit encryption. See your system administrator to determine your level of encryption, and to verify that the server is using the same level of encryption.128-bit encryption is available without restriction for North American users of Windows 2000, Windows NT 4.0 with Service Pack 3, and Windows 9 x clients that use dial-up networking 1.2 and higher. You need to order separately the version of each of these products that supports 128-bit encryption. Availability outside of North America is determined by United States Government regulation. For more information, see Data encryption.
743 The remote server requires data encryption
743 The remote access server requires encryption, but your connection is not enabled for encryption. See To configure identity authentication and data encryption settings for a dial-up connection and To configure identity authentication and data encryption settings for a VPN connection.
751 The callback number contains an invalid character. Only the following characters are allowed: 0 to 9, T, P, W, (,), -, @, and space
751 Invalid callback number. Only the characters 0 to 9, T, P, W, (, ), -, @, and space are allowed in the number. Enter the correct numbers and redial.
752 A syntax error was encountered while processing a script.
752 A syntax error was encountered while processing a script. See Automating the dial-up logon process by using Windows scripting, Automating the dial-up logon process by using Switch.inf scripts, or Troubleshooting logon scripts.
753 The connection could not be disconnected because it was created by the multi-protocol router
753 This connection is being used by Routing and Remote Access. Use the Routing and Remote Access service to disconnect the connection. The connection appears in either the list of routing interfaces or the list of remote access clients.
754 The system could not find the multi-link bundle
754 An internal error occurred. Restart your computer to make sure that all recent configuration changes have taken effect.
755 The system cannot perform automated dial because this entry has a custom dialer specified
755 Contact your system administrator.
756 This connection is already being dialed
756 Wait and try again later.
757 Remote access services could not be started automatically. Additional information is provided in the event log
757 An internal error occurred. Restart your computer to make sure that all recent configuration changes have taken effect. If the error persists, consult the Windows 2000 event log for detailed warnings or errors.
758 Internet connection sharing is already enabled on the connection
758 This error may occur if an application enables Internet connection sharing while the properties of the connection are open, and then you try to enable the feature. Close and then reopen the properties of the connection. The Enable Internet connection sharing check box on the Internet connection sharing tab should be selected.
760 An error occurred while routing capabilities were being enabled
760 An internal error occurred while attempting to enable routing. Contact your system administrator.
761 An error occurred while Internet connection sharing was being enabled for the connection
761 An internal error occurred while Internet connection sharing was being enabled. Contact your system administrator.
763 Internet connection sharing cannot be enabled. There are two or more LAN connections in addition to the connection to be shared
763 Close and reopen the properties of the connection. The Enable Internet connection sharing check box on the Internet connection sharing tab should be selected. Select a LAN connection from the list.
764 No smart card reader is installed
764 Install a smart card reader.
765 Internet connection sharing cannot be enabled. A LAN connection is already configured with the IP address required for automatic IP addressing
765 Internet connection sharing configures the LAN connection of the home network or small office network with a static address. There is another network adapter in the system that is configured with the same address. Change the static address of the network adapter before enabling Internet connection sharing.
766 The system could not find any certificate
766 Contact your system administrator. If you are a member of an Active Directory domain and need to request a certificate, see To request a certificate. If you are not a member of an Active Directory domain, or you need to request a certificate from the Internet, see To submit a user certificate request via the Web.
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
767 Remove the additional static IP addresses, or reconfigure the LAN connection for DHCP. See To configure TCP/IP settings.
768 The connection attempt failed because of failure to encrypt data
768 If encryption is not necessary, disable encryption and try again. See To configure identity authentication and data encryption settings for a dial-up connection and To configure identity authentication and data encryption settings for a VPN connection.
769 The specified destination is not reachable
769 Either you specified a destination address that is not valid, or your remote access server is down. Check the destination address and try again.
770 The remote machine rejected the connection attempt
770 The remote computer may be rejecting your connection because of a caller ID rule or another hardware setting.
771 The connection attempt failed because the network is busy
771 Wait and try again later.
772 The remote computer's network hardware is incompatible with the type of call requested
772 See your system administrator.
773 The connection attempt failed because the destination number has changed
773 Enter the correct number and try again.
774 The connection attempt failed because of a temporary failure. Try connecting again
774 Wait and try again later. This error may indicate a timing issue, or a problem with the remote computer.
775 The call was blocked by the remote computer
775 The remote computer may be blocking your connection because of a caller ID rule, a scheduling policy that only allows access during specific times, or another setting.
776 The call could not be connected because the destination has invoked the Do Not Disturb feature
776 See your system administrator.
777 The connection attempt failed because the modem on the remote computer is out of order
777 See your system administrator.
778 It was not possible to verify the identity of the server
778 In the authentication process, the server identifies itself to your computer, and your computer identifies itself to the server. When this error occurs, your computer is not recognizing the server.
779 To dial out using this connection, you must use a smart card
779 Install a smart card. See To install a smart card reader on a computer.
780 An attempted function is not valid for this connection
780 An internal error occurred. Contact your system administrator. You may need to configure the connection for EAP.
781 The encryption attempt failed because no valid certificate was found
781 Request a certificate. If you are a member of an Active Directory domain, see To request a certificate. If you are not a member of an Active Directory domain, or you need to request a certificate from the Internet, see To submit a user certificate request via the Web.
