Common solutions and steps in the case of 678:
1. First, check that the adsl modem dial-up is normal. Because the IP address automatically obtained by The NIC is not cleared, a 678 error will be prompted when the Nic cannot get a new IP address when dialing again. The operation is as follows: disable adsl modem, enter the network connection on the control panel, right-click the local connection, and select Disable. After five seconds, right-click the local connection and Select Enable. Then enable the adsl modem dialing function;
2. If the first step is invalid, disable the local connection (NIC), restart the computer, and enable the local connection (NIC) when the adsl modem is disabled ), enable the adsl modem;
3. If the above steps cannot be solved, check whether the Nic light is on. If the Nic light is not on, refer to"
Nic lights are not on or are often not on.
4. If the Nic lights are normal and cannot be solved in step 1 or 2, you will be taken to load the NIC driver and reinstall the NIC driver. For more information, see
How to set up an ADSL dial-up connection in WINXPCreate a dial-up connection.
5. If the above operation is invalid, contact the telecommunications department to confirm the port.
Code Overview
Description of some fault codes for adsl pppoe dialing errors:
Error 602 The port is already open
Problem: The dial-up network cannot be connected due to a device installation error or in use.
Cause: PPPoE is not fully and correctly installed.
Solution: uninstall and reinstall any PPPoE software.
Error 605 Cannot set port information
Problem: The Port cannot be set for the dial-up network due to device installation errors
Cause: PPPoE is not fully and correctly installed.
Solution: uninstall and reinstall any PPPoE software.
Error 606 The port is not connected
Problem: The dial-up network cannot connect to the required device port
Cause: PPPoE is not fully and correctly installed. Connection line faults and adsl modem faults
Solution: uninstall any PPPoE software, reinstall it, and check the network cable and adsl modem.
Error 608 The device does not exist
Problem: The device connected to the dial-up network does not exist.
Cause: PPPoE is not fully and correctly installed.
Solution: uninstall and reinstall any PPPoE software.
Error 609 The device type does not exist
Problem: the type of the device connected to the dial-up network cannot be determined.
Cause: PPPoE is not fully and correctly installed.
Solution: uninstall and reinstall any PPPoE software.
Error 611 The route is not available/612 The route is not allocated
Problem: The dial-up network connection route is incorrect.
Cause: PPPoE is not fully and correctly installed, and the ISP server is faulty.
Solution: uninstall and reinstall any PPPoE software, and call the ISP to ask
Error 617 The port or device is already disconnecting
Problem: The device connected to the dial-up network has been disconnected.
Cause: PPPoE is not fully and correctly installed, ISP server faults, connection lines, and adsl modem faults
Solution: uninstall and reinstall any PPPoE software. Call the ISP to check the network cable and adsl modem.
Error 619
Problem: unable to establish a connection with the ISP server
Cause: adsl isp server fault and ADSL telephone line fault
Solution: Check whether the ADSL signal lights are correctly synchronized. Call ISP to ask
Error 621 Cannot open the phone book file
Error 622 Cannot load the phone book file
Error 623 Cannot find the phone book entry
Error 624 Cannot write the phone book file
Error 625 Invalid information found in the phone book
Problem: Windows NT or Windows 2000 Server network RAS network component failure
Cause: uninstall all PPPoE software and reinstall the RAS network component and RasPPPoE.
Error 630
Problem: No response from ADSL MODEM
Cause: ADSL telephone line fault, adsl modem fault (power supply not open, etc)
Solution: check the ADSL device
Error 633
Problem: The dial-up network cannot be connected due to a device installation error or in use.
Cause: PPPoE is not fully and correctly installed.
Solution: uninstall and reinstall any PPPoE software.
Error 638
Problem: After a long time, you cannot connect to the ISP's ADSL access server
Cause: The ISP server is faulty. You entered a wrong phone number in the poor connection created by PPPoE.
Solution: run pppoe.exe with the created dial to check whether the ISP service can be listed to ensure that the ISP is normal. Clear the phone number in the used dial-up connection or retain only one 0.
Error 645
Problem: The Nic does not respond correctly
Cause: Nic fault or NIC driver fault
Solution: check the NIC and reinstall the NIC driver.
Error 650
Problem: the remote computer does not respond and the connection is disconnected.
Cause: network protocol error caused by adsl isp server fault, Nic fault, abnormal shutdown
Solution: Check whether the ADSL signal lamp can be correctly synchronized. Call the ISP to ask. Check the NIC and delete all network components to reinstall the network.
Error 651
Problem: error reported by ADSL MODEM
Cause: Windows is in safe mode, or other errors
Solution: when this error occurs, repeat it to report the specific error code.
Error 691
Problem: The user name and password entered are incorrect. A connection cannot be established.
Cause: The user name and password are incorrect, and the ISP server is faulty.
Solution: Use the correct user name and password, and use the correct ISP account format (name @ service), and call the ISP to ask.
Error 718
Problem: No response is returned when the remote computer Times out when the user name is verified. The connection is closed.
Cause: adsl isp server fault
Solution: call the ISP to ask
Error 720
Problem: The dial-up network cannot coordinate server protocol settings in the network
Cause: The adsl isp server is faulty. An abnormal shutdown may cause a network protocol error.
Solution: call the ISP to delete all network components and reinstall the network.
Error 734
Problem: the PPP connection control protocol is suspended.
Cause: The adsl isp server is faulty. An abnormal shutdown may cause a network protocol error.
Solution: call the ISP to delete all network components and reinstall the network.
Error 738
Problem: The server cannot assign an IP address
Cause: The adsl isp server is faulty. Too many ADSL users exceed the IP addresses that the ISP can provide.
Solution: call the ISP to ask
Error 769
Problem: The NIC is disabled or the NIC driver is not correctly installed
Solution: Check whether the NIC driver is correctly installed. If the NIC driver is normal, go to the device manager and set the disabled NIC status to enable. Then, connect again.
Error 797
Problem: the adsl modem connection device is not found
Cause: The power supply of the adsl modem is not enabled, and the connection line between the NIC and the adsl modem is faulty. After the software is installed, the corresponding protocol is not properly bound. When a dial-up connection is created, an incorrect null connection is established.
Solution: check the power supply and connection lines, check the network properties, and check whether the PPPoE-related protocols are correctly installed and correctly bound (related protocols), and check whether the NIC appears? No. Or! To Enable the connection. Check whether the connected device uses an "ISDN channel-Adapter Name (xx)" device, this device is an empty device. If you cancel it, select the correct PPPoE device to replace it, or re-create a dial-up connection.
The following are error codes for using ADSL in VISTA:
798
No certificate can be found for scalable authentication protocols.
799
Internet Connection Sharing (ICS) cannot be enabled due to an IP address conflict ). ICS requires that the host be configured with 192.168.0.1. Make sure no other clients on the network are configured with 192.168.0.1.
800
You cannot establish a VPN connection. The VPN server may not be accessible, or the security parameters of the connection are not correctly configured.
801
This connection is configured to verify the identity of the access server, but Windows cannot verify the digital certificate sent by the server.
802
The provided card cannot be identified. Check whether the card is correctly inserted and whether it is tightly inserted.
803
The PEAP configuration saved in the session cookie does not match the current session configuration.
804
The peap id in the session cookie does not match the current ID.
805
You cannot use this connection to dial when logging on because it is configured with the user ID card after logon.
806
The connection between the computer and the VPN server has been started, but the VPN connection cannot be completed. The most common cause of this problem is that at least one Internet device (such as a firewall or router) between your computer and the VPN server is not configured to allow the GRE protocol package. If the problem persists, contact your network administrator or Internet service provider.
807
The network connection between the computer and the VPN server is interrupted. This may be caused by problems in the VPN transmission process, usually due to Internet latency or only because the VPN server has reached the capacity limit. Try again to connect to the VPN server. If the problem persists, contact the VPN administrator and analyze the network connection quality.
808
The network connection between the computer and the VPN server cannot be established because the remote server rejects the connection. This is usually because the server configuration and connection settings do not match. Contact the remote server administrator to verify the server configuration and connection settings.
809
The network connection between the computer and the VPN server cannot be established because the remote server does not respond. This may be because you have not configured a network device (such as firewall, NAT, or vro) between the computer and the remote server to allow VPN connections. Contact the administrator or service provider to determine which device may cause this problem.
810
The network connection between the computer and the VPN server has been started, but the VPN connection is not completed. This is usually because an incorrect or expired certificate is used for authentication between the client and the server. Contact the administrator to ensure that the certificate used for authentication is valid.
811
The network connection between the computer and the VPN server cannot be established because the remote server does not respond. This is usually caused by pre-shared keys between the client and the server. The pre-shared key is used to ensure your identity in the IP security settings (IPSec) communication cycle. Ask the administrator for help to determine where the pre-shared key issue comes from.
812
The connection is blocked due to a policy configured on the RAS/VPN server. In particular, the authentication method used by the server to verify the user name and password may not match the authentication method configured in the connection configuration file. Contact the administrator of the RAS server and notify them of this error.
813
When the previous broadband connection is established, you try to establish another broadband connection using the same device or port. Disconnect the previous connection and establish a new connection.
814
The basic Ethernet connection required for the broadband connection is not found. Before trying this connection, install and enable the Ethernet adapter on your computer through the network connection folder.
815
You cannot establish a broadband network connection on your computer because the remote server does not respond. This may be because the "service name" field value of this connection is invalid. Contact your Internet service provider to obtain the correct value of this field and update it in connection properties.
816
The Remote Access Service no longer supports the features or settings you are trying to enable.
817
A connection cannot be deleted when it is in the connection status.
818
Network access protection (NAP) forces the client to fail to create system resources for remote access connections. Some network services or resources may be unavailable. If the problem persists, disconnect the connection, retry the remote access connection, or contact the administrator of the Remote Access Server.
819
The network access protection proxy (NAPAgent) service is disabled or not installed on this computer. Some network services or resources may be unavailable. If the problem persists, disconnect the connection, retry the remote access connection, or contact the administrator of the Remote Access Server.
820
Network access protection (NAP) forces clients to be unable to register the network access protection proxy (NAPAgent) service. Some network services or resources may be unavailable. If the problem persists, disconnect the connection, retry the remote access connection, or contact the administrator of the Remote Access Server.
821
Network access protection (NAP) forces the client to fail to process requests because the remote access connection does not exist. Try the remote access connection again. If the problem persists, make sure that you can connect to the Internet and then contact the administrator who remotely accesses the server.
822
Network access protection (NAP) forces the client to have no response. Some network services or resources may be unavailable. If the problem persists, disconnect the connection, retry the remote access connection, or contact the administrator of the Remote Access Server.
823
The received encrypted binding TLV is invalid.
824
The encrypted binding TLV is not received.
825
Point-to-Point Tunneling Protocol (PPTP) is incompatible with IPv6. Change the VPC type to L2 Tunneling Protocol (L2TP)
826
EAPTLS verification for cached creden。 failed. Discard cache creden.
827
The L2TP/IPSec connection cannot be completed because IKE and AuthIP IPSec key module services and/or basic filter engine services are not running. To establish an L2TP/IPSec connection, the above services are required. Make sure these services are enabled before dialing connections.
O-fareast-theme-font: minor-fareast; "> The peap id stored in the session cookie does not match the current one.
805
You cannot use this connection to dial when logging on because it is configured with the user ID card after logon.
806
The connection between the computer and the VPN server has been started, but the VPN connection cannot be completed. The most common cause of this problem is that at least one Internet device (such as a firewall or router) between your computer and the VPN server is not configured to allow the GRE protocol package. If the problem persists, contact your network administrator or Internet service provider.
807
The network connection between the computer and the VPN server is interrupted. This may be caused by problems in the VPN transmission process, usually due to Internet latency or only because the VPN server has reached the capacity limit. Try again to connect to the VPN server. If the problem persists, contact the VPN administrator and analyze the network connection quality.
808
The network connection between the computer and the VPN server cannot be established because the remote server rejects the connection. This is usually because the server configuration and connection settings do not match. Contact the remote server administrator to verify the server configuration and connection settings.
809
The network connection between the computer and the VPN server cannot be established because the remote server does not respond. This may be because you have not configured a network device (such as firewall, NAT, or vro) between the computer and the remote server to allow VPN connections. Contact the administrator or service provider to determine which device may cause this problem.
810
The network connection between the computer and the VPN server has been started, but the VPN connection is not completed. This is usually because an incorrect or expired certificate is used for authentication between the client and the server. Contact the administrator to ensure that the certificate used for authentication is valid.
811
The network connection between the computer and the VPN server cannot be established because the remote server does not respond. This is usually caused by pre-shared keys between the client and the server. The pre-shared key is used to ensure your identity in the IP security settings (IPSec) communication cycle. Ask the administrator for help to determine where the pre-shared key issue comes from.
812
The connection is blocked due to a policy configured on the RAS/VPN server. In particular, the authentication method used by the server to verify the user name and password may not match the authentication method configured in the connection configuration file. Contact the administrator of the RAS server and notify them of this error.
813
When the previous broadband connection is established, you try to establish another broadband connection using the same device or port. Disconnect the previous connection and establish a new connection.
814
The basic Ethernet connection required for the broadband connection is not found. Before trying this connection, install and enable the Ethernet adapter on your computer through the network connection folder.
815
You cannot establish a broadband network connection on your computer because the remote server does not respond. This may be because the "service name" field value of this connection is invalid. Contact your Internet service provider to obtain the correct value of this field and update it in connection properties.
816
The Remote Access Service no longer supports the features or settings you are trying to enable.
817
A connection cannot be deleted when it is in the connection status.
818
Network access protection (NAP) forces the client to fail to create system resources for remote access connections. Some network services or resources may be unavailable. If the problem persists, disconnect the connection, retry the remote access connection, or contact the administrator of the Remote Access Server.
819
The network access protection proxy (NAPAgent) service is disabled or not installed on this computer. Some network services or resources may be unavailable. If the problem persists, disconnect the connection, retry the remote access connection, or contact the administrator of the Remote Access Server.
820
Network access protection (NAP) forces clients to be unable to register the network access protection proxy (NAPAgent) service. Some network services or resources may be unavailable. If the problem persists, disconnect the connection, retry the remote access connection, or contact the administrator of the Remote Access Server.
821
Network access protection (NAP) forces the client to fail to process requests because the remote access connection does not exist. Try the remote access connection again. If the problem persists, make sure that you can connect to the Internet and then contact the administrator who remotely accesses the server.
822
Network access protection (NAP) forces the client to have no response. Some network services or resources may be unavailable. If the problem persists, disconnect the connection, retry the remote access connection, or contact the administrator of the Remote Access Server.
823
The received encrypted binding TLV is invalid.
824
The encrypted binding TLV is not received.
825
Point-to-Point Tunneling Protocol (PPTP) is incompatible with IPv6. Change the VPC type to L2 Tunneling Protocol (L2TP)
826
EAPTLS verification for cached creden。 failed. Discard cache creden.
827
The L2TP/IPSec connection cannot be completed because IKE and AuthIP IPSec key module services and/or basic filter engine services are not running. To establish an L2TP/IPSec connection, the above services are required. Make sure these services are enabled before dialing connections.
