In the process of using Network and Dial-up Connection, we may receive one or more of the following error messages. Below, we will sort out the detailed information about these errors.
600 operation suspended.
60 1 An invalid port handle was detected.
The port specified by 602 is already open.
The com port that the network connection is trying to use is being used by other active network connections or other processes.
603 caller's buffer is too small.
604 specified incorrect information.
605 Unable to set port information.
If the error persists, delete and recreate the network and dial-up connections.
The port specified by 606 is not connected.
607 An invalid event was detected.
608 The specified device does not exist.
If the error persists, delete and recreate the network and dial-up connections.
609 The specified device type does not exist.
If the error persists, delete and recreate the network and dial-up connections.
The buffer specified by 6 10 is invalid.
6 1 1 The specified route is not available.
If the error persists, please refer to the Windows 2000 error log for detailed warnings or errors.
The route specified in 6 12 is not assigned.
This error can also occur when the computer is running with very low resources. If the error persists, please refer to the Windows 2000 error log for detailed warnings or errors.
The compression specified by 6 13 is invalid.
6 14 does not have enough buffers.
If the error persists, please refer to the Windows 2000 error log for detailed warnings or errors.
6 15 cannot find the specified port.
If the error persists, delete and recreate the network and dial-up connections.
6 16 asynchronous request is suspended.
The 6 17 modem has been disconnected.
Wait for the network and dial-up connection to disconnect.
The port specified by 6 18 is not open.
The port specified by 6 19 is not connected.
Restart the computer.
Unable to determine the end point.
If the error persists, please refer to the Windows 2000 error log for detailed warnings or errors.
62 1 The system cannot open the phone book.
Network and dial-up connections use the rasphone.pbk file located in the %systemroot%\system32\ras folder. Please make sure that the file is in this folder, and then restart the network and dial-up connection.
The system could not load the phone book.
Network and dial-up connections use the rasphone.pbk file located in the %systemroot%\system32\ras folder. Please make sure that the file is in this folder, and then restart the network and dial-up connection.
The system could not find the phone book entry for this connection.
The network and dial-up connection are in the phone book, but the specified connection item cannot be found. This error does not occur unless another application is using a network and dial-up connection and an incorrect connection item is used.
The system could not update the phone book file.
Network and dial-up connections use the rasphone.pbk file located in the %systemroot%\system32\ras folder. Make sure that the disk is not full and that you have permission to change the file.
The system found invalid information in the phone book.
The phone book file rasphone.pbk may be corrupted. Please delete the file from the %systemroot%\system32\ras folder, and then restart the network and dial-up connection to create a new file.
Unable to load string.
If the error persists, please refer to the Windows 2000 error log for detailed warnings or errors.
627 Unable to find the keyword.
A configuration file for network and dial-up connections may contain invalid information. If the modem you are using is not supported by Windows 2000, you should install a supported modem.
The connection has been closed.
If it is a virtual private network (VPN) connection, access may be denied due to remote access policy or other authentication problems. Please consult your system administrator.
This sometimes happens because the broadband connection speed of the computer is faster than the network connection speed of the modem. At this point, you can wait for half a minute before reconnecting the Broadband Connection, or restart the modem, and then reconnect the Broadband Connection after all four lights on the modem are on (one of them flashes several times every few seconds).
Re-establishing a new broadband connection can eliminate this failure.
The 629 connection was closed by the remote computer.
The connection link is broken for one of the following reasons:
1, unrecoverable telephone line error
2. Noisy lines
3. Disconnected by the system administrator
4. Unable to negotiate correctly with the modem on the remote access server at the selected speed.
If the redial error persists, slow down the connected modem and try redialing. You can try to connect to other servers to determine whether this problem is related to the specific remote access server you are calling. Similarly, you can try to connect to the original server through another phone line.
The modem was disconnected due to hardware failure.
The link was broken for one of the following reasons:
1, an unrecoverable error occurred in the modem (or other communication equipment).
2. There is an unrecoverable error in the communication port.
3. The modem cable is not plugged in.
To diagnose and correct the problem:
1. Make sure the modem is turned on and the cable connection is reliable.
2. In order to ensure the normal operation of the modem, the command test can be conducted through the control panel.
63 1 The user disconnected the modem.
An operation on the computer disconnected. Redial.
632 Incorrect structural dimensions have been detected.
If the error persists, please refer to the Windows 2000 error log for detailed warnings or errors.
The 633 modem is in use or not configured to dial out.
If it is a dial-up network connection, the com port that the network connection is trying to use is being used by other active network connections or other processes.
If it is a virtual private network (VPN), you will not be able to open the VPN device that the network connection is trying to use. If the problem persists, please consult your system administrator.
Your computer cannot be registered on the remote network.
The remote access server cannot register your computer name on the network, which usually appears in NetBIOS protocol, but it may also appear in tcp/ip or ipx. Typically, this error occurs when the address is already in use on the network. Please contact the system administrator.
An unknown error occurred in 635.
If the error persists, please refer to the Windows 2000 error log for detailed warnings or errors.
The device connected to the port is not the expected device.
The hardware configuration and configuration settings used for the connection may be contradictory. If you change the communication device (such as serial port or modem), please reconfigure the dial-up connection.
637 A string that cannot be converted was detected.
The request timed out.
639 asynchronous network is not available.
NetBIOS network configuration may be incorrect. Restart the computer.
A NetBIOS-related error occurred in 640.
The modem could not negotiate the connection at the set speed. Set the initial speed of the modem to a lower value, and then redial. You can also try to disable modem compression and software compression. If the connection cannot be established, try adding ipx/spx and NetBIOS protocols to the connection.
64 1 The server could not allocate NetBIOS resources needed to support the client.
Ask the system administrator to increase the resource capacity of remote access server or stop some unimportant services, such as messenger service and network DDE.
The NetBIOS name of the 642 computer has been registered on the remote network.
Another computer with the same name has logged into the remote network, and each computer in the network must be registered with a unique name to verify the following items:
1. The computer with the same name as your computer is not in the network you are connecting to.
2. The computer is not physically connected to the network you are trying to connect to.
The network card on the server side is out of order.
Please report this error to the system administrator.
You will not be able to receive network pop-up messages.
Another computer connected to the network is using your computer name, and the mail sent to you will be sent to that computer. If you want to receive information from a remote workstation, you must remember to log off the office computer before dialing into the network next time. This error does not affect messages sent by outlook, express and exchange.
645 An internal validation error occurred.
This account is currently not allowed to log in.
Configure an account to restrict access to this network. If you need to access the network at different times of the day (instead of the currently configured time), ask the system administrator to change the settings.
This account has been disabled.
The user account is disabled. This may be due to multiple failed login attempts, or because the system administrator has disabled the account for security reasons. Ask your system administrator to enable this account in local users and groups.
The password for this account has expired.
If you connect through a network and dial-up connection, you will be prompted to change your password. If you connect using rasdial, you can change the password by doing the following:
1, press Ctrl+Alt+Del.
2. Click "Change Password" and follow the prompts.
If you are a system administrator, but your password has expired, you can't change it yourself. Only another administrator can change it.
Account number 649 has no permission to dial in.
The account has no dial-in permission for the following reasons:
1. There is a valid account in the selected domain, but the account does not have access to the remote network. Ask your system administrator to enable dial-in permissions for user accounts or for routing and remote access.
2. The account has expired, been disabled, locked or the dial-in access is locked.
You tried to connect outside the allowed server login time limit, or you tried to connect outside the allowed dial-in access time limit, or the policy applied to the account may not allow dial-in access.
3. The caller's ID rules may prevent the connection, for example, you need to dial an account from a specified number.
4. The remote computer may only allow local accounts to connect.
5. An authentication protocol is required, and the computer cannot negotiate the protocol, or the computer tries to use a protocol that has not been verified by the policy on the remote computer.
If you have an account with dial-in permission in another domain, please do the following to use the account in that domain.
1. Right-click the connection, and then click Properties.
2. On the Options tab, select Prompt for Name, Password, Certificate, etc. And the Windows login domain check box.
3. In the Security Measures tab, clear the Automatically use my Windows login 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.
The 650 remote access server is not responding.
This error can be caused by any of the following conditions:
1. The remote access server is not running. Please contact the system administrator to ensure that the server is running.
2. The line noise is too loud, or the modem cannot negotiate correctly with the modem of the remote access server at the selected speed. In any case, you should reduce the initial speed (bps) of the modem and redial.
3. Check the hardware compatibility list to ensure that your modem is listed.
4. It may be necessary to replace the serial cable of the modem.
5. The authentication settings used to connect may be incorrect. Please contact your system administrator to ensure that your authentication settings meet the requirements of the remote access server.
6. Software compression of remote access server and hardware compression of modem can be enabled at the same time. Generally, remote server software compression is enabled and hardware compression is disabled.
The 65 1 modem reported an error.
The modem (or other device) reported an error.
If you have a dial-up connection and use a supported external modem, turn off and restart the modem. Shut down and restart.
652 has an unrecognized response from the modem.
The message returned by the modem (or other device) is not listed in one or more script files (Pad.inf, Switch.inf or filename.scp). If you use a supported external modem, turn off and restart the modem, and then redial. If the problem persists, try connecting at a lower initial speed.
Telephone line 676 is busy.
Redial the number. Realize automatic redial in the options tab of the connection properties. Also contact the system administrator to verify that the remote server is running.
The 678 server didn't answer.
The modem or other device is not off-hook. Also make sure that the telephone line (network cable) is plugged into the correct slot of the modem (network card).
The carrier cannot be detected by the 679 system.
The modem or other device is not off-hook. Many modems will return this error if the remote modem is not off-hook. Automatic redial can be realized in the tab of connection properties.
680 has no dial tone.
The telephone line may not be properly connected to or disconnected from the modem. The phone number needs a prefix, such as 9, to dial an outside line, or the number is too long. Make sure that the telephone line is plugged into the correct slot of the modem. Also make sure that all special access numbers connected to the outside line are added, such as prefix 9 followed by a comma. For example: 9555 * 0 100. Check the telephone line for intermittent sounds, which means there is voice mail. Many modems cannot dial more than 34 digits. When a long number is encountered, these modems divide it into two or more strings and dial only the first string (incomplete). This happens in robots and multi-technology demodulators. The only known way to solve this problem is to use another brand of modem.
69 1 Access is denied because the user name and/or password are invalid on this domain.
The user account is not registered in the listed domain, the password has expired, or the information entered is incorrect. If no domain is specified, the remote access server will try to verify the user name and password in the domain to which it belongs.
Please re-enter the user name, password and domain carefully. If you are not sure about this information, please consult your system administrator.
The 692 modem has a hardware failure.
The modem (or other device) is not responding for the following reasons:
The modem is off, out of order or not reliably connected to the computer.
To solve this problem, do the following:
1) resets the modem. Refer to the hardware documentation for details.
2) If you use an external modem, please make sure that you use an appropriate serial cable and the cable connection is reliable. You may want to try replacing the modem cable. Similarly, if you use an adapter to connect an external modem to a serial port, make sure that the adapter is wired correctly so that the modem can communicate. For example, the mouse's 9-pin to 25-pin adapter does not work properly in a serial network connection.
3) Test the serial port or multi-port adapter and replace it if necessary.
4) Make sure that the handshake option of the modem is configured correctly. Consult your hardware documentation for information about the different handshake options available to your modem.
5) If your modem is not supported by the network and dial-up connection, please switch to a supported modem.
6) Verify that other applications (for example, "HyperTerminal") are not using the communication port. If you are using this port, starting the network and dial-up connection may cause this message to appear.
The machine is not started.
The 696 state machine has been started.
The response loop did not complete.
The response of the 699 modem caused a buffer overflow.
Extended commands in 700 devices. INF file is too long.
The command in the script file cannot exceed 256 characters. The command is decomposed into multiple commands.
COM driver does not support the connection speed used by 70 1 modem.
The modem tried to connect at a speed that the serial port could not explain. Please reset the initial speed to the next lowest standard bps speed.
The 703 connection requires user information, but the application does not allow user interaction.
The server you are trying to connect to requires user interaction. Rasdial commands, or applications used to try dialing, do not support user interaction.
If possible, try to connect using an existing connection in the Network and Dial-up Connections folder.
If you use a script to connect, try using a dial-up connection with terminal features configured. The terminal window can realize the required user interaction.
The 704 callback number is invalid.
The callback number specified for customer is invalid.
The 705 authentication status is invalid.
Look for detailed warnings or errors.
707 has an error related to the X.25 protocol.
The X.25 connection returned an error. Ask the X.25 provider to explain the diagnostic information given.
708 account expires.
Ask your system administrator to reactivate your account.
Error changing the password on the domain. The password may be too short or the same as the previous password.
Please try to change the password again. If you continue to receive this message, please report it to your system administrator.
7 10 detected a sequence overflow error when communicating with the modem.
You should slow down the initial speed of the modem (bits per second) and redial.
7 1 1 Remote Access Service Manager failed to start. Additional information is provided in the event log.
The Remote Access Connection Manager service may not be running. Modify the service to start automatically.
Restart the computer. For more information, please visit the Personal Support Center on the Microsoft website.
There may be a problem with the modem or the modem cable. Try replacing the modem cable.
7 12 dual port is initializing. Wait a few seconds before redialing.
This error occurred on a connection configured to receive calls (duplex connection). This error may also occur when the server dials out while initializing the connection to receive the call. Network and dial-up connections will be redialed in a few seconds.
.713 has no active ISDN line available.
Please make sure that the ISDN cable is inserted correctly and the terminal resistor is installed correctly (refer to the documentation of the ISDN card), and then redial. If you still receive this error, please contact the customer service of ISDN provider or ISDN telephone company.
7 14 has no ISDN channel to dial.
All available ISDN channels are busy. Generally speaking, ISDN provided at BRI ("Basic Rate Interface") service level provides two channels through which voice or data calls can be made. If both channels are in use, the network and dial-up connection cannot be dialed out. Hang up a channel and redial.
7 15 There are too many errors due to the poor quality of the telephone line.
During authentication, there were too many asynchronous errors on the telephone line. Try again. If the problem persists, you should lower the baud rate and disable all functions of setting up the modem.
7 16 remote access service IP configuration is not available.
There is a problem with the TCP/IP configuration on the remote access server. For example, the connection is requesting an unavailable TCP/IP address from the server.
Please contact the system administrator to verify the TCP/IP settings of the server.
7 17 There is no IP address available in the static pool of IP addresses of the remote access service.
Try to use an IP address that will not cause remote network conflicts. If possible, use DHCP to avoid address conflicts.
7 18 The connection waiting for a valid response from the remote computer timed out.
The PPP session was started, but it was interrupted because the remote computer didn't respond within an appropriate time. This may be due to poor line quality or problems with the server.
The 7 19 connection was terminated by the remote computer.
The PPP session started, but was interrupted at the request of the remote computer. There may be an error in the server.
The connection attempt failed because the PPP control protocol between your computer and the remote computer is inconsistent.
PPP network control protocol is not configured for this connection or the corresponding network protocol is not installed. This error may occur when the network protocol type changes during the product upgrade.
72 1 The remote computer is not responding.
An attempt was made to use a PPP session, but the remote computer did not respond. This error occurs when the server (for example, Windows NT 3.5 1 or an earlier version of Remote Access Server or SLIP Server) does not support PPP.
This error also occurs if you need to log in to the terminal window before the server starts PPP. If you use the terminal window to log in and solve the problem, you can make the future connection process automatically.
This error also indicates a hardware error on your computer or remote server.
Invalid data received from the remote computer. This data will be ignored.
The received PPP packet format is invalid. System administrators may need to log PPP events to a file to solve this problem.
The phone number (including prefix and suffix) is too long.
The maximum length of a phone number (including prefix and suffix) is 128 characters.
726IPX protocol cannot be used to dial out on multiple modems at the same time.
With IPX protocol, only one connection can be used for dialing out.
The 728 system cannot find the IP adapter.
There is a problem with the TCP/IP configuration. Restart the computer.
SLIP cannot be used unless the IP protocol is installed.
Verify that TCP/IP is installed.
73 1 has no configuration protocol.
Specific information about unconfigured PPP control protocols is required. To identify PPP negotiation issues, ask the system administrator to enable PPP login using the Netsh.exe utility.
The PPP control protocols of your computer and the remote computer are inconsistent.
PPP parameter negotiation failed because the local computer and the remote computer could not agree on a common parameter set. Please consult your system administrator to verify the configuration of network protocols, such as TCP/IP, IPX or NetBEUI.
The PPP control protocols of your computer and the remote computer are inconsistent.
The server supports PPP, but does not support the connected network protocol. Ask the system administrator to configure the connection to use the network protocol supported by the server.
734PPP link control protocol was terminated.
PPP link control protocol session starts.
The server rejected the requested address.
Configure a connection to request a specific IP address. The server is not configured to allow customers to request a specific IP address, or a specific IP address can be used by other customers. If possible, use DHCP to avoid address conflicts.
The remote computer terminated the control protocol.
Session initialization of PPP network control protocol.
Loopback detected.
The local computer and the remote computer involved in the PPP session are the same computer. This usually means that a device in the link (for example, a modem) is echoing characters. Try resetting these devices.
For other vendors' servers, this may indicate that the remote computer tried to log in using a Teletypewriter (TTY) before connecting. You can configure the connection of connected terminals on the Security Measures tab.
The 738 server has no assigned address.
The server was unable to assign you an IP address from the assigned address pool. Ask the system administrator to configure this connection to use a specific IP address on the client, so as not to cause conflicts on the remote network.
739 The authentication protocol required by the remote server cannot use the stored password. Dial again and enter the password explicitly.
This error occurs when establishing a PPP connection to a non-Microsoft server. The standard PPP authentication protocol used to interact with other servers requires the password to be in plaintext format, but for security reasons, Windows only stores the encrypted format.
740 An invalid dialing rule was detected.
TAPI devices configured for network and dial-up connections failed to initialize or were not installed correctly. Restart the computer.
If the error persists, please refer to the event log for specific warnings or errors.
74 1 The local computer does not support the required data encryption type.
Select the "Require data encryption (if not, please disconnect)" check box on the Security Measures tab, but your connection has no encryption function. Clear the check box to use an unencrypted connection or consult your system administrator.
This error can also occur if the password exceeds 14 characters. On the Security tab, select the Require data encryption (disconnect without encryption) check box, and in Verify my identity as, select Require password with security measures. Use a password less than 14 characters, clear the "Require data encryption (disconnect if not encrypted)" check box, and click "Allow unsecured passwords" in "Verify my identity".
The remote computer does not support the required data encryption type.
The required encryption level is not available on the remote computer. One computer may use 128-bit encryption technology, while another computer uses 40-bit or 56-bit encryption. Please consult your system administrator to determine the encryption level and verify that the servers use the same encryption level.
North American users of Windows 2000 and Windows NT 4.0 with Service Pack 3 and customers who use dial-up network 1.2 or above can use it without restriction.