DUNS ERROR 781
781 - The encryption attempt failed because no valid certificate was found.
This error may occur with Windows 2000 or XP client attempting to connect to a virtual private network (VPN) using Layer 2 Tunneling Protocol (L2TP) and IP Security Protocol (IPSec).
If you are not attempting to connect with VPN, L2TP or IPSec, check your Connectoid's Security tab - and set it according to your ISP's instructions (most ISPs use 'Typical - allow unsecured password).
If you are attempting to connect with VPN, L2TP or IPSec:
· There may be a problem with the remote computer:
The certificate on the VPN server is not valid or missing - the administrator of the remote computer must correct the problem.
The IPSec Policy Agent service on the remote computer may be stopped, or stopped and re-started without stopping and re-starting the Routing and Remote Access service on the server. The administrator of the remote computer must correct the problem.
For more information - see MS KB 247231
782 - Network Address Translation (NAT) is currently installed as a routing protocol, and must be removed before enabling Internet Connection Sharing.
783 Internet Connection Sharing cannot be enabled. The LAN connection selected as the private network is either not present, or is disconnected from the network. Please ensure that the LAN adapter is connected before enabling Internet Connection Sharing.
784 You cannot dial using this connection at logon time, because it is configured to use a user name different than the one on the smart card. If you want to use it at logon time, you must configure it to use the user name on the smart card.
785 You cannot dial using this connection at logon time, because it is not configured to use a smart card. If you want to use it at logon time, you must edit the properties of this connection so that it uses a smart card.
786 The L2TP connection attempt failed because there is no valid machine certificate on your computer for security authentication.
787 The L2TP connection attempt failed because the security layer could not authenticate the remote computer.
788 The L2TP connection attempt failed because the security layer could not negotiate compatible parameters with the remote computer.
789 The L2TP connection attempt failed because the security layer encountered a processing error during initial negotiations with the remote computer.
790 The L2TP connection attempt failed because certificate validation on the remote computer failed.
791 The L2TP connection attempt failed because security policy for the connection was not found.
DUNS ERROR 792
792 - The L2TP Connection Attempt failed because security negotiation timed out.
Windows 2000 & XP: This error can occur if you have a preshared key configured on the client, but the key is not configured on the RRAS (Routing and Remote Access Service) server. This error can occur even if valid certificates are configured on both the client and server. This can be resolved by removing the preshared key from the client so that a security negotiation process using certificates can occur.
See MS KB Q299307
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.
DUNS ERROR 797
797 - The modem could not be found.
This error occurs only in Windows 2000 and XP. The error can occur if the modem is no longer visible to the system, and may be a problem related to the modem driver, or system conflicts that cause the modem to work only some of the time.
In some cases, rebooting the machine may "solve" the problem.
If the modem is an external and is not powered on when the system is booted this error may occur: shut-down, power on the modem & re-boot the system.
If the error persists, check to see if there is an updated driver for your modem.
DUNS ERROR 798
798 - A certificate could not be found that can be used with this Extensible Authentication Protocol.
This error may occur if your dial-up networking security settings require a certificate that cannot be located.
Most ISPs do not require EAP (extensible authentication protocol) for access: check your Connectoid's Security Tab settings - normally, 'Typical' is selected, and EAP is not used.
For this error to occur, the security tab settings are set to 'Advanced (Custom Settings), which enables the 'Settings...' button, which produces a windows with 'Logon Security' settings which include EAP. Change the security settings if the server you are connecting to does not require EAP.
If the server does require EAP, contact the system administrator or see the 'Certificates' help section of Windows' Help for Network Connections.
DUNS ERROR 799
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.
If you are not using ICS (Internet Connection Sharing), edit the Advanced tab of your connectoid and un-check the 'Allow other computers to connect through this computer's Internet connection' checkbox.
If you are using ICS, the IP address of your machine's LAN connection, and/or other machines on the network are incorrect. As the error message indicates, your machine must be assigned IP 192.168.0.1, and no other machine or device on the LAN can use that address. Your machine's IP address is controlled by Properties associated with your Local Area Connection in the 'LAN or high-speed Internet' section of Windows' Network Connections. (Start->Connect To -> Show All Connections)
This error applies to Windows 2000 & XP.
DUNS ERROR 800
800 - Unable to establish the VPN connection. The VPN server may be un-reachable, or security parameters may not be configured properly for this connection.
This error may occur if a Virtual Private Network connection is specified, but fails to authenticate. See this Microsoft how-to article on using Virtual Private Networks for Secure Internet Data Transfer.
Some of the reasons this error occurs include:
· The PPTP or L2TP server is not reachable. A firewall could be blocking traffic; the server name specified in your connection could be incorrect.
· Your connection configuration might prevent IPSec from establishing a secure channel with the server. A network component such as Network Address Translation (NAT) or a firewall might be blocking IPSec traffic.
· Verify whether you have a current machine certificate or that the pre-shared key is correct. Check the security settings in the properties for your network connection.
· There are no free VPN ports on the server (over-subscribed - maximum number of users already connected).
This error applies to Windows 2000 & XP.
801 This connection is configured to validate the identity of the access server, but Windows cannot verify the digital certificate sent by the server.
900 The router is not running.
901 The interface is already connected.
902 The specified protocol identifier is not known to the router.
903 The Demand-dial Interface Manager is not running.
904 An interface with this name is already registered with the router.
905 An interface with this name is not registered with the router.
906 The interface is not connected.
907 The specified protocol is stopping.
908 The interface is connected and hence cannot be deleted.
909 The interface credentials have not been set.
910 This interface is already in the process of connecting.
911 An update of routing information on this interface is already in progress.
912 The interface configuration in invalid. There is already another interface that is connected to the same interface on the remote router.
913 A Remote Access Client attempted to connect over a port that was reserved for Routers only.
914 A Demand Dial Router attempted to connect over a port that was reserved for Remote Access Clients only.
915 The client interface with this name already exists and is currently connected.
916 The interface is in a disabled state.
917 The authentication protocol was rejected by the remote peer.
918 There are no authentication protocols available for use.
919 The remote computer refused to be authenticated using the configured authentication protocol. The line has been disconnected.
920 The remote account does not have Remote Access permission.
921 The remote account has expired.
922 The remote account is disabled.
923 The remote account is not permitted to logon at this time of day.
924 Access was denied to the remote peer because username and/or password is invalid on the domain.
925 There are no routing enabled ports available for use by this demand dial interface.
926 The port has been disconnected due to inactivity.
927 The interface is not reachable at this time.
928 The Demand Dial service is in a paused state.
929 The interface has been disconnected by the administrator.
930 The authentication server did not respond to authentication requests in a timely fashion.
931 The maximum number of ports allowed for use in the multilinked connection has been reached.
932 The connection time limit for the user has been reached.
933 The maximum limit on the number of LAN interfaces supported has been reached.
934 The maximum limit on the number of Demand Dial interfaces supported has been reached.
935 The maximum limit on the number of Remote Access clients supported has been reached.
936 The port has been disconnected due to the BAP policy.
937 Because another connection of your type is in use, the incoming connection cannot accept your connection request.
938 No RADIUS servers were located on the network.
939 An invalid response was received from the RADIUS authentication server. Make sure that the case sensitive secret password for the RADIUS server is set correctly.
940 You do not have permission to connect at this time.
941 You do not have permission to connect using the current device type.
942 You do not have permission to connect using the selected authentication protocol.
943 BAP is required for this user.
944 The interface is not allowed to connect at this time.
945 The saved router configuration is incompatible with the current router.
946 RemoteAccess has detected older format user accounts that will not be migrated automatically. To migrate these manually, run XXXX.
948 The transport is already installed with the router.
949 Received invalid signature length in packet from RADIUS server.
950 Received invalid signature in packet from RADIUS server.
951 Did not receive signature along with EAPMessage from RADIUS server.
952 Received packet with invalid length or Id from RADIUS server.
953 Received packet with attribute with invalid length from RADIUS server.
954 Received invalid packet from RADIUS server.
955 Authenticator does not match in packet from RADIUS server.
No comments:
Post a Comment