Then I leave you the errors that you can give when connecting to the VPN and its meanings:
600
There is a pending operation.
601
The port indicator is not valid.
602
The port is already open.
603
The caller's buffer is very small.
604
The information specified is incorrect.
606
The port is not connected.
608
The device does not exist.
609
The type of device does not exist.
610
The buffer is not valid.
612
The route is not assigned.
615
The port was not found.
616
An asynchronous request is pending.
617
The device or port is already disconnecting.
618
The port is not open.
619
The port is disconnected.
621
Can not open the phone book file.
622
Can not load the phone book file.
623
The entry can not be found in the phone book.
624
Can not write to the phone book file.
625
The information found in the phone book is not valid.
627
The key can not be found.
628
The port was disconnected.
629
The remote computer disconnected the port.
630
The port was disconnected due to a hardware error.
631
The user disconnected the port.
632
The size of the structure is not correct.
633
The port is already in use or not configured for Remote Access dialing.
635
Unknown error
636
The wrong device is connected to the port.
638
The request has exhausted the waiting time.
645
Internal authentication error.
646
Unable to sign in to the account at this time of day.
647
The account is disabled.
648
The password has expired.
649
The account does not have remote access permission.
651
The modem or other connection device has reported an error.
652
Unrecognized device response
653
A macro required by the device was not found in the device section of the .INF file.
654
A command or response in the device section of the .INF file refers to an undefined macro.
655
The <message> macro was not found in the .INF file section of the device.
656
The <defaultoff> macro in the .INF file section of the device contains an undefined macro.
657
The device .INF file can not be opened.
658
The device name in the device .INF file or in the media .INI file is too long.
659
The media .INI file refers to an unknown device name.
660
The device .INF file does not contain responses to the command.
661
A command is missing in the device's .INF file.
662
You tried to set a macro that does not appear in the device section in the .INF file.
663
The media .INI file refers to an unknown device type.
664
Can not allocate memory.
665
The port is not configured for remote access.
666
The modem (or other connection device) does not work.
667
The media .INI file can not be read.
668
The connection was removed.
669
The usage parameter in the media .INI file is not valid.
670
The name of the section in the media .INI file can not be read.
671
The device type can not be read from the media .INI file.
672
The device name can not be read from the media .INI file.
673
The usage can not be read from the media .INI file.
676
The line is busy.
677
A person responded instead of a modem.
678
There's no answer.
679
The carrier can not be detected.
680
There is no dial tone.
691
Access was denied because the username or password, or both, are not valid in the domain.
692
Hardware error in port or connected device.
693
ERROR: MACRO IS NOT BINARY
694
DCB ERROR NOT FOUND
695
ERROR STATE MACHINES WITHOUT INITIATING
696
ERROR STATE MACHINES ALREADY INITIATED
697
PARTIAL RESPONSE LOOP ERROR
698
A response key name in the device .INF file does not have the expected format.
699
The response of the device has caused a buffer overflow.
700
The expanded command in the device .INF file is too long.
701
The device was moved at a BPS speed incompatible with the COM driver.
702
The answer was received from the device when none was expected.
703
INTERACTIVE MODE ERROR
704
INCORRECT CALL RETURN NUMBER ERROR
705
ERROR OF STATUS OF INVALID AUTHORIZATION
707
Diagnostic indication X.25.
708
The account has expired.
709
Error changing the password in the domain.
710
Several saturation errors were detected when communicating with the modem.
711
RasMan initialization error. Check the event log.
713
There are no active ISDN lines available.
716
The remote access IP configuration can not be used.
717
There are no IP addresses available in the static set of remote access IP addresses.
718
Exhausted PPP waiting time
720
PPP control protocols have not been configured.
721
The remote PPP partner does not respond.
722
The PPP package is not valid.
723
The telephone number, including the prefix and suffix, is too long.
726
The IPX protocol can not be used to make a call on more than one port at the same time.
728
Can not find an IP adapter linked to remote access.
729
Error using SLIP unless the IP protocol is installed.
730
The equipment has not been registered.
731
The protocol is not configured.
732
The PPP negotiation does not converge.
733
The PPP control protocol for this network protocol is not available on the server.
734
The PPP link control protocol ended.
735
The required address has been rejected by the server.
736
The remote computer has finished the control protocol.
737
A loopback has been detected.
738
The server has not assigned an address.
739
The remote server can not use the encrypted Windows NT password.
740
TAPI devices configured for remote access were not initialized or installed correctly.
741
The local machine does not support encryption.
742
The remote server does not support encryption.
749
ERROR_BAD_PHONE_NUMBER
752
A syntax error was encountered when processing a script.
753
The connection could not be disconnected because it was created by the multi-protocol router.
754
The system can not find the multi-link package.
755
The system can not perform an automated markup because this connection has a specified custom marker.
756
This connection has already been marked.
757
Remote access services can not be started automatically. Additional information is provided in the event log.
764
No smart card reader is installed.
765
The shared Internet connection can not be enabled. A LAN connection is already configured with the IP address that is required for automatic IP addressing.
766
Can not find a certificate Connections that use the L2TP protocol over IPSec require the installation of a machine certificate, which is also known as a computer certificate.
767
The shared Internet connection can not be enabled. The LAN connection selected as a private network has more than one IP address. Reconfigure it with an IP address before enabling the shared Internet connection.
768
Error in the connection attempt due to an error when encrypting the data.
769
The specified destination can not be reached.
770
The remote computer rejected the connection attempt.
771
Connection attempt failed because the network is busy.
772
The network hardware of the remote computer is incompatible with the type of call requested.
773
Connection attempt failed because the destination number has changed.
774
Connection attempt failed due to a temporary error. Try connecting again.
775
The remote computer blocked the call.
776
The call can not be connected because the remote device has called the Do Not Disturb feature.
777
Connection attempt failed because the modem (or other device with connection) on the remote computer does not work.
778
The identity of the server can not be verified.
780
An attempted function is not valid for this connection.
782
Internet Connection Sharing (ICS) or Internet Connection Security Server can not be enabled because Routing and Remote Access has been enabled. 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
Unable to enable Internet Connection Sharing. The LAN connection selected as a private network is not present or is disconnected from the network. Verify that the LAN adapter is connected before enabling the shared Internet connection.
784
You can not dial with this connection during logon, as it is configured to use a different user name than the smart card. To use it, configure it with the user name of the smart card.
785
You can not dial with this connection during logon, as it is not configured to use a smart card. To use it, modify the properties of this connection so that it uses a smart card.
786
Error in L2TP connection attempt because there is not a valid computer certificate on your computer for security authentication.
787
Error in the L2TP connection attempt because the security level could not authenticate the remote computer.
788
Error in the L2TP connection attempt because the security level could not negotiate parameters compatible with the remote computer.
789
Error in the L2TP connection attempt because the security level encountered a process error during the initial negotiations with the remote computer.
790
Error in the L2TP connection attempt because there was an error in the validation of the certificate on the remote computer.
791
Error in the L2TP connection attempt because the security policy for the connection was not found.
792
The L2TP connection attempt failed because the security negotiation timeout expired.
793
Error in the L2TP connection attempt because there was an error during the security negotiation.
794
The RADIUS attribute of the frame protocol for this user is not PPP.
795
The RADIUS attribute of the tunnel type for this user is not correct.
796
The RADIUS attribute of the service type for this user is not lattice or lattice with callback.
797
A connection to the remote computer can not be established because a modem was not found or the modem was busy. For more details, click More Information or search for the following error number in the Help and Support Center.
798
Can not find a certificate that can be used with this extended authentication protocol.
799
The Internet Connection Sharing (ICS) can not be enabled due to a conflict of IP addresses in the network. ICS requires that the host be configured to use 192.168.0.1. Make sure that no other client in the network is configured to use 192.168.0.1.
800
The VPN connection could not be established. It is possible that the VPN server can not be reached or that the security settings are not correct for this connection.
801
This connection is configured to validate the identity for access to the server, but Windows can not check the digital certificate sent by the server.
802
The card you have provided has not been recognized. Check that the card has been inserted correctly and that it fits the intended space.
803
The PEAP configuration stored in the cookie of the session does not match the current session configuration.
804
The PEAP identity stored in the cookie of the session does not match the current identity.
805
You can not dial using this connection at the time of login, because it is configured to use connected user credentials.
806
A connection has been initiated between the computer and the VPN server, but the VPN connection can not be completed. The most common cause is that at least one Internet device (for example, a firewall or a router) is not configured between the computer and the VPN server to support Generic Route Encapsulation (GRE) packets. If the problem persists, contact your network administrator or Internet service provider.
807
The network connection between the computer and the VPN server was interrupted. It may be due to a problem in the VPN transmission and is usually a consequence of Internet latency or simply that the VPN server has reached its maximum capacity. Try reconnecting with the VPN server. If this problem persists, contact the VPN administrator and analyze the quality of the network connection.
808
The network connection between the computer and the VPN server could not be established because the remote server refused the connection. The most common cause is the discrepancy between the server configuration and its connection configuration. Contact the administrator of the remote server to check the configuration of the server and its connection.
809
The network connection between the computer and the VPN server could not be established because the remote server does not respond. This could be because some of the network devices (such as firewalls, NATs, routers, etc.) between the computer and the remote server are not configured to allow VPN connections. Contact the administrator or your service provider to determine which device may be causing the problem.
810
A network connection between the computer and the VPN server was initiated, but the VPN connection was not completed. The most likely cause is the use of an incorrect or expired certificate for authentication between the client and the server. Contact the administrator to make sure that the certificate that is being used for authentication is valid.
811
The network connection between the computer and the VPN server could not be established because the remote server does not respond. The most likely cause is a problem of keys previously shared between the client and the server. A previously shared key is used to guarantee its identity in an IP security communication cycle (IPSec). Request the help of the administrator to determine the source of the previously shared key problem.
812
The connection was prevented due to a policy configured on the RAS / VPN server. Specifically, the authentication method used by the server to verify its user name and password may not match the one configured in the connection profile. Contact the RAS server administrator and inform him / her of this error.
813
You have attempted to establish a broadband connection when a previous broadband connection has already been established with the same device or port. Disconnect the previous connection and reconnect.
814
The underlying Ethernet connectivity required for the broadband connection was not found. Before attempting this connection, install and enable the Ethernet adapter on the computer through the Network Connections folder.
815
The broadband network connection could not be established on the computer because the remote server does not respond. This may be due to an invalid value in the 'Service name' field for this connection. Contact your Internet service provider and request the correct value from this field and update it in Connection properties.
816
The remote access service no longer supports a feature or configuration value that you tried to enable.
817
A connection can not be deleted while connected.
818
The Network Access Protection (NAP) compliance client could not create the system resources for the remote access connections. Some resources or network services will not be available. If the problem persists, disconnect and retry the remote access connection or contact the administrator of the remote access server.
819
The Network Access Protection Agent (NAP Agent) service has been disabled or is not installed on this computer. Some resources or network services will not be available. If the problem persists, disconnect and retry the remote access connection or contact the administrator of the remote access server.
820
The Network Access Protection (NAP) compliance compliance client failed to register with the Network Access Protection Agent (NAP Agent) service. Some resources or network services will not be available. If the problem persists, disconnect and retry the remote access connection or contact the administrator of the remote access server.
821
The Network Access Protection (NAP) compliance client could not process the request because the remote access connection does not exist. Retry the remote access connection If the problem persists, make sure you can connect to the Internet and contact the administrator of the remote access server.
822
The compliance client of Network Access Protection (NAP) did not respond. Some resources or network services will not be available. If the problem persists, disconnect and retry the remote access connection or contact the administrator of the remote access server.
823
The Crypto-Binding TLV is not valid.
824
TLV of Crypto-Binding not received.
825
The Point-to-Point Tunneling Protocol (PPTP) is incompatible with IPv6. Change the virtual private network type to Level Two Tunneling Protocol (L2TP)
826
EAPTLS validation error of the credentials in the cache. Drop the credentials in the cache.
827
The L2TP / IPsec connection can not be completed because the IPSec Key Creation Modules service for IKE and AuthIP or the Base Filter Engine service are not running. These services are necessary to establish an L2TP / IPSec connection. Make sure that these services were started before dialing the connection.