Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Applies To: Windows 7
This article lists the Error Codes that you may receive when you try to make a dial-up connection or a VPN connection on a computer that is running Windows® 7.
Error Codes
The following list contains the Error Codes that you may receive when you try to make a dial-up connection or a VPN connection:
| Error | Description |
|---|---|
600 |
An operation is pending. |
601 |
An invalid port handle was detected. |
602 |
The specified port is already open. |
603 |
The caller's buffer is too small. |
604 |
Incorrect information was specified. |
606 |
The specified port is not connected. |
608 |
A device was specified that does not exist. |
609 |
A device type was specified that does not exist. |
610 |
An invalid buffer was specified. |
612 |
A route was specified that is not allocated. |
615 |
The specified port was not found. |
616 |
An asynchronous request is pending. |
617 |
The modem (or other connecting device) is already disconnecting. |
618 |
The specified port is not open. |
619 |
A connection to the remote computer could not be established, so the port used for this connection was closed. |
621 |
The system could not open the phone book file. |
622 |
The system could not load the phone book file. |
623 |
The system could not find the phone book entry for this connection. |
624 |
The system could not update the phone book file. |
625 |
The system found invalid information in the phone book file. |
627 |
A key could not be found. |
628 |
The connection was terminated by the remote computer before it could be completed. |
629 |
The connection was closed by the remote computer. |
630 |
The modem (or other connecting device) was disconnected due to hardware failure. |
631 |
The user disconnected the modem (or other connecting device). |
632 |
An incorrect structure size was detected. |
633 |
The modem (or other connecting device) is already in use or is not configured properly. |
635 |
There was an unknown error. |
636 |
The device attached to the port is not the one expected. |
638 |
The remote server is not responding in a timely fashion. |
645 |
There was an internal authentication error. |
646 |
The account is not permitted to log on at this time of day. |
647 |
The account is disabled. |
648 |
The password for this account has expired. |
649 |
The account does not have permission to dial in. |
651 |
The modem (or other connecting device) has reported an error. |
652 |
There was an unrecognized response from the modem (or other connecting device). |
653 |
A macro required by the modem (or other connecting device) was not found in the device.INF file. |
654 |
A command or response in the device.INF file section refers to an undefined macro. |
655 |
The <message> macro was not found in the device.INF file section. |
656 |
The <defaultoff> macro in the device.INF file section contains an undefined macro. |
657 |
The device.INF file could not be opened. |
658 |
The device name in the device.INF or media.INI file is too long. |
659 |
The media.INI file refers to an unknown device name. |
660 |
The device.INF file contains no responses for the command. |
661 |
The device.INF file is missing a command. |
662 |
There was an attempt to set a macro not listed in device.INF file section. |
663 |
The media.INI file refers to an unknown device type. |
664 |
The system has run out of memory. |
665 |
The modem (or other connecting device) is not properly configured. |
666 |
The modem (or other connecting device) is not functioning. |
667 |
The system was unable to read the media.INI file. |
668 |
The connection was terminated. |
669 |
The usage parameter in the media.INI file is invalid. |
670 |
The system was unable to read the section name from the media.INI file. |
671 |
The system was unable to read the device type from the media.INI file. |
672 |
The system was unable to read the device name from the media.INI file. |
673 |
The system was unable to read the usage from the media.INI file. |
676 |
The phone line is busy. |
677 |
A person answered instead of a modem (or other connecting device). |
678 |
The remote computer did not respond. To make sure that the server can be reached, ping the remote computer. |
679 |
The system could not detect the carrier. |
680 |
There was no dial tone. |
691 |
The connection was denied because the username or password you specified is not valid or because the selected authentication protocol is not permitted on the remote server. Credentials are not valid for any of the following reasons: your username or password was not typed correctly; the username does not exist on the server; your password has expired; or the administrator has not given you access to connect remotely. |
692 |
There was a hardware failure in the modem (or other connecting device). |
693 |
ERROR_NOT_BINARY_MACRO |
694 |
ERROR_DCB_NOT_FOUND |
695 |
The state machines are not started. |
696 |
The state machines are already started. |
697 |
The response looping did not complete. |
698 |
A response keyname in the device.INF file is not in the expected format. |
699 |
The modem (or other connecting device) response caused a buffer overflow. |
700 |
The expanded command in the device.INF file is too long. |
701 |
The modem moved to a connection speed not supported by the COM driver. |
702 |
Device response received when none expected. |
703 |
The connection needs information from you, but the application does not allow user interaction. |
704 |
The callback number is invalid. |
705 |
The authorization state is invalid. |
707 |
There was an error related to the X.25 protocol. |
708 |
The account has expired. |
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. |
710 |
Serial overrun errors were detected while communicating with the modem. |
711 |
The operation could not finish because it could not start the Remote Access Service Manager service in time. Please try the operation again. |
713 |
No active ISDN lines are available. |
716 |
The Remote Access Service IP configuration is unusable. |
717 |
No IP addresses are available in the static pool of Remote Access Service IP addresses. |
718 |
The connection was terminated because the remote computer did not respond in a timely manner. |
720 |
A connection to the remote computer could not be established. You might need to change the network settings for this connection. |
721 |
The remote computer did not respond. |
722 |
Invalid data was received from the remote computer. This data was ignored. |
723 |
The phone number, including prefix and suffix, is too long. |
726 |
The IPX protocol cannot be used for dialing out on more than one modem (or other connecting device) at a time. |
728 |
The system cannot find an IP adapter. |
729 |
SLIP cannot be used unless the IP protocol is installed. |
731 |
The protocol is not configured. |
732 |
Your computer and the remote computer could not agree on PPP control protocols. |
733 |
A connection to the remote computer could not be completed. You might need to adjust the protocols on this computer. |
734 |
The PPP link control protocol was terminated. |
735 |
The requested address was rejected by the server. |
736 |
The remote computer terminated the control protocol. |
737 |
Loopback was detected. |
738 |
The server did not assign an address. |
739 |
The authentication protocol required by the remote server cannot use the stored password. Redial, entering the password explicitly. |
740 |
An invalid dialing rule was detected. |
741 |
The local computer does not support the required data encryption type. |
742 |
The remote computer does not support the required data encryption type. |
749 |
The destination address or phone number is either invalid or not present. |
752 |
A syntax error was encountered while processing a script. |
753 |
The connection could not be disconnected because the user does not have the required permission to disconnect. |
754 |
The system could not find the multi-link bundle. |
755 |
The system cannot perform automated dial because this connection has a custom dialer specified. |
756 |
This connection is already being dialed. |
757 |
Remote Access Services could not be started automatically. Additional information is provided in the event log. |
764 |
No smart card reader is installed. |
765 |
Internet Connection Sharing cannot be enabled. A LAN connection is already configured with the IP address that is required for automatic IP addressing. |
766 |
A certificate could not be found. Connections that use the L2TP protocol over IPSec require the installation of a machine certificate, also known as a computer certificate. |
767 |
Internet Connection Sharing cannot be enabled. The LAN connection selected as the private network has more than one IP address configured. Please reconfigure the LAN connection with a single IP address before enabling Internet Connection Sharing. |
768 |
The connection attempt failed because of failure to encrypt data. |
769 |
The specified destination is not reachable. |
770 |
The remote computer rejected the connection attempt. |
771 |
The connection attempt failed because the network is busy. |
772 |
The remote computer's network hardware is incompatible with the type of call requested. |
773 |
The connection attempt failed because the destination number has changed. |
774 |
The connection attempt failed because of a temporary failure. Try connecting again. |
775 |
The call was blocked by the remote computer. |
776 |
The call could not be connected because the remote computer has invoked the Do Not Disturb feature. |
777 |
The connection attempt failed because the modem (or other connecting device) on the remote computer is out of order. |
778 |
It was not possible to verify the identity of the server. |
780 |
An attempted function is not valid for this connection. |
782 |
Internet Connection Sharing (ICS) and Internet Connection Firewall (ICF) cannot be enabled because Routing and Remote Access has been enabled on this computer. To enable ICS or ICF, first disable Routing and Remote Access. For more information about Routing and Remote Access, ICS, or ICF, see Help and Support. |
783 |
Internet Connection Sharing cannot be enabled. The LAN connection selected as the private network is either not present, or is disconnected from the network. Please ensure that the LAN adapter is connected before enabling Internet Connection Sharing. |
784 |
You cannot dial using this connection at logon time, because it is configured to use a user name different than the one on the smart card. If you want to use it at logon time, you must configure it to use the user name on the smart card. |
785 |
You cannot dial using this connection at logon time, because it is not configured to use a smart card. If you want to use it at logon time, you must edit the properties of this connection so that it uses a smart card. |
786 |
The connection attempt failed because there is no valid machine certificate on your computer for security authentication. |
787 |
The L2TP connection attempt failed because the security layer could not authenticate the remote computer. |
788 |
The L2TP connection attempt failed because the security layer could not negotiate compatible parameters with the remote computer. |
789 |
The L2TP connection attempt failed because the security layer encountered a processing error during initial negotiations with the remote computer. |
790 |
The L2TP connection attempt failed because certificate validation on the remote computer failed. |
791 |
The L2TP connection attempt failed because security policy for the connection was not found. |
792 |
The L2TP connection attempt failed because security negotiation timed out. |
793 |
The L2TP connection attempt failed because an error occurred while negotiating security. |
794 |
The Framed Protocol RADIUS attribute for this user is not PPP. |
795 |
The Tunnel Type RADIUS attribute for this user is not correct. |
796 |
The Service Type RADIUS attribute for this user is neither Framed nor Callback Framed. |
797 |
A connection to the remote computer could not be established because the modem was not found or was busy. |
798 |
A certificate could not be found that can be used with this Extensible Authentication Protocol. |
799 |
Internet Connection Sharing (ICS) cannot be enabled due to an IP address conflict on the network. ICS requires the host be configured to use 192.168.0.1. Please ensure that no other client on the network is configured to use 192.168.0.1. |
800 |
Unable to establish the VPN connection because a tunnel could not be setup. This might be because the VPN server cannot be reached or because security parameters for this connection are not configured correctly. |
801 |
This connection is configured to validate the identity of the access server, but Windows cannot verify the digital certificate sent by the server. |
802 |
The card supplied was not recognized. Please check that the card is inserted correctly, and fits tightly. |
803 |
The PEAP configuration stored in the session cookie does not match the current session configuration. |
804 |
The PEAP identity stored in the session cookie does not match the current identity. |
805 |
You cannot dial using this connection at logon time, because it is configured to use logged on user's credentials. |
806 |
The VPN connection between your computer and the VPN server could not be completed. The most common cause for this failure is that at least one Internet device (for example, a firewall or a router) between your computer and the VPN server is not configured to allow Generic Routing Encapsulation (GRE) protocol packets. If the problem persists, contact your network administrator or Internet Service Provider. |
807 |
The network connection between your computer and the VPN server was interrupted. This can be caused by a problem in the VPN transmission and is commonly the result of internet latency or simply that your VPN server has reached capacity. Please try to reconnect to the VPN server. If this problem persists, contact the VPN administrator and analyze quality of network connectivity. |
808 |
The network connection between your computer and the VPN server could not be established because the remote server refused the connection. This is typically caused by a mismatch between the server's configuration and your connection settings. Please contact the remote server's Administrator to verify the server configuration and your connection settings. |
809 |
The network connection between your computer and the VPN server could not be established because the remote server is not responding. This could be because one of the network devices (e.g, firewalls, NAT, routers, etc) between your computer and the remote server is not configured to allow VPN connections. Please contact your Administrator or your service provider to determine which device may be causing the problem. |
810 |
A network connection between your computer and the VPN server was started, but the VPN connection was not completed. This is typically caused by the use of an incorrect or expired certificate for authentication between the client and the server. Please contact your Administrator to ensure that the certificate being used for authentication is valid. |
811 |
The network connection between your computer and the VPN server could not be established because the remote server is not responding. This is typically caused by a pre-shared key problem between the client and server. A pre-shared key is used to guarantee you are who you say you are in an IP Security (IPSec) communication cycle. Please get the assistance of your administrator to determine where the pre-shared key problem is originating. |
812 |
The connection was prevented because of a policy configured on your RAS/VPN server. Specifically, the authentication method used by the server to verify your username and password may not match the authentication method configured in your connection profile. Please contact the Administrator of the RAS server and notify them of this error. |
813 |
You have attempted to establish a second broadband connection while a previous broadband connection is already established using the same device or port. Please disconnect the earlier connection and then reestablish the connection. |
814 |
The underlying Ethernet connectivity required for the broadband connection was not found. Please install and enable the Ethernet adapter on your computer via the Network Connections folder before attempting this connection. |
815 |
The broadband network connection could not be established on your computer because the remote server is not responding. This could be caused by an invalid value for the 'Service Name' field for this connection. Please contact your Internet Service Provider and inquire about the correct value for this field and update it in the Connection Properties. |
816 |
A feature or setting you have tried to enable is no longer supported by the remote access service. |
817 |
Cannot delete a connection while it is connected. |
818 |
The Network Access Protection (NAP) enforcement client could not create system resources for remote access connections. Some network services or resources might not be available. If the problem persists, disconnect and retry the remote access connection or contact the administrator for the remote access server. |
819 |
The Network Access Protection Agent (NAPAgent) service has been disabled or is not installed on this computer. Some network services or resources might not be available. If the problem persists, disconnect and retry the remote access connection or contact the administrator for the remote access server. |
820 |
The Network Access Protection (NAP) enforcement client failed to register with the Network Access Protection Agent (NAPAgent) service. Some network services or resources might not be available. If the problem persists, disconnect and retry the remote access connection or contact the administrator for the remote access server. |
821 |
The Network Access Protection (NAP) enforcement client was unable to process the request because the remote access connection does not exist. Retry the remote access connection. If the problem persists, make sure that you can connect to the Internet, and then contact the administrator for the remote access server. |
822 |
The Network Access Protection (NAP) enforcement client did not respond. Some network services or resources might not be available. If the problem persists, disconnect and retry the remote access connection or contact the administrator for the remote access server. |
823 |
Received Crypto-Binding TLV is invalid. |
824 |
Crypto-Binding TLV is not received. |
825 |
Point-to-Point Tunneling Protocol (PPTP) is incompatible with IPv6. Change the type of virtual private network to Layer Two Tunneling Protocol (L2TP) |
826 |
EAPTLS validation of the cached credentials failed. Please discard cached credentials. |
827 |
The VPN connection cannot be completed because the 'IKE and AuthIP IPSec Keying Modules' service and/or the 'Base Filtering Engine' service is not running. These services are required to establish the connection. Please ensure that these services have been started before dialing the connection. |
828 |
The connection was terminated because of idle timeout. |
829 |
The modem (or other connecting device) was disconnected due to link failure. |
830 |
The connection was terminated because user logged off. |
831 |
The connection was terminated because user switch happened. |
832 |
The connection was terminated because of hibernation. |
833 |
The connection was terminated because the system got suspended. |
834 |
The connection was terminated because Remote Access Connection manager stopped. |
835 |
The L2TP connection attempt failed because the security layer could not authenticate the remote computer. This could be because one or more fields of the certificate presented by the remote server could not be validated as belonging to the target destination. |
836 |
The Network Access Protection (NAP) health state of the computer cannot be determined. Contact your administrator to verify that the NAP enforcement client is enabled, the NAP Agent service is running, and NAP is enforced in the Protected Extensible Authentication Protocol (PEAP) properties of the remote access connection. |
837 |
Invalid Tunnel ID. |
838 |
Another Update connection request is in progress. RAS allows only one Update Connection request at a time. |
839 |
Negotiating using configured protocol is disable. Edit connection properties and select different protocol for negotiation and try again. |
840 |
Internal address negotiation failed. |
841 |
Client has to request a Internal IPv4 or IPv6 address. |
842 |
Traffic Selectors negotiation failed. |
843 |
Mobility is disabled for this connection. |
844 |
The VPN Connection is still connecting or reauthenticating because of Quarantine state change. Initiate mobile update only when connection state is 'Connected'. |
845 |
Server rejected client authentication, due unexpected TLV or value mismatch for a TLV. |
846 |
Either VPN Destination preference is not selected by the user or it is no longer valid. |
847 |
Cached smart card credential is invalid. |
848 |
VPN connection attempt failed due to internal error occurred while adding cookies to the Secure Socket Tunneling Protocol (SSTP). Please see the System Event Log for the detailed information. |
849 |
The PEAP inner method attributes stored in the cookie is invalid |
850 |
The Extensible Authentication Protocol type required for authentication of the remote access connection is not installed on your computer. |
851 |
The Extensible Authentication Protocol type configured on the remote access connection does not support single sign- on. |
852 |
The Extensible Authentication Protocol type configured on the remote access connection does not support the requested operation. |
853 |
The remote access connection completed, but authentication failed because the certificate that authenticates the client to the server is not valid. Ensure that the certificate used for authentication is valid. |
854 |
The remote access connection completed, but authentication failed because the certificate that authenticates the client to the server is expired. Renew the certificate. |
855 |
The remote access connection completed, but authentication failed because the certificate that authenticates the client to the server is revoked. |
856 |
The remote access connection completed, but authentication failed because of an error in the certificate that authenticates the client to the server. |
857 |
The remote access connection completed, but authentication failed because the certificate that the client uses to authenticate the server is not valid. |
858 |
The remote access connection completed, but authentication failed because the certificate that the client uses to authenticate the server is expired. |
859 |
The remote access connection completed, but authentication failed because the certificate that the client uses to authenticate the server is revoked. |
860 |
The remote access connection completed, but authentication failed because of an error in the certificate that the client uses to authenticate the server. |
861 |
The remote access connection completed, but authentication failed because a trusted root certificate that validates the user certificate was not found in the Trusted Root Certification Authorities certificate store. |
862 |
The remote access connection completed, but authentication failed because the trusted root certificate that is used to validate the user certificate is not valid. |
863 |
The remote access connection completed, but authentication failed because the certificate in the Trusted Root Certification Authorities certificate store that authenticates the user certificate is expired. Renew the certificate. |
864 |
The remote access connection completed, but authentication failed because a certificate that validates the server certificate was not found in the Trusted Root Certification Authorities certificate store. |
865 |
The remote access connection completed, but authentication failed because the certificate in the Trusted Root Certification Authorities certificate store that validates the server certificate is not valid. |
866 |
The remote access connection completed, but authentication failed because the certificate on the server computer does not have a server name specified. |
867 |
The PEAP outer identity is not same as the inner identity when identity privacy is turned OFF. |
868 |
The Dns name is not resolvable. Make sure the DNS Name is resolvable and reachable. |