|
|
 |
|
|
Network and Dial-up Connection Errors (MS Windows)
Listed here are Microsoft Windos Network and DUN errors along with some
tips, tutorials and fixes. Feel free to add your tip or
tutorial to the page with credit to the author by clicking on "Share a tip" link.
|
DUN Error 691
:: Access was denied because the user name and/or password was invalid on the domain |
Share a tip. Click here. |
| Either your user account is not registered with the domain listed, your password is expired, or you mistyped the information. If you do not specify a domain, the remote access server attempts to verify your user name and password on the domain of which it is a member.Carefully retype your user name, password, and domain. If you are unsure of this information, ask your system administrator. |
|
DUN Error 692
:: There was a hardware failure in the modem |
Share a tip. Click here. |
Your modem (or other device) is not responding because of the following:
· The modem is either turned off, malfunctioning, or is not securely connected to your computer.
To resolve this problem, do the following:
· Reset your modem. For more information, consult your hardware documentation.
· If you are using an external modem, ensure that you are using a proper serial cable, and that it is connected securely. You may want to try replacing the modem cable. Also, if you are using an adapter to connect your external modem to your serial port, ensure that the adapter is wired properly for modem communication. For example, a 9-to-25 pin adapter for a mouse does not work properly with a serial network connection.
· Test the serial port or multiport adapter, and replace it if necessary.
· Ensure that the handshaking options for the modem are configured properly. Consult your hardware documentation for information about different handshaking options available for your modem.
· If your modem is not supported by Network and Dial-up Connections, switch to a supported modem. For the most up-to-date list of supported modems, see the Hardware Compatibility List at the Microsoft Web site (http://www.microsoft.com/). Your Windows 2000 CD includes a copy of this list ( drive: \Support\hcl.txt) that was accurate as of the date Windows 2000 was released.
· Verify that another application, such as HyperTerminal, is not using the communications port. If the port is being used, subsequently starting Network and Dial-up Connections may cause this message to appear. |
|
DUN Error 695
:: The state machines are not started |
Share a tip. Click here. |
| An internal error occurred. Restart your computer to make sure that all recent configuration changes have taken effect. |
|
DUN Error 696
:: The state machines are already started |
Share a tip. Click here. |
| An internal error occurred. Restart your computer to make sure that all recent configuration changes have taken effect. |
|
DUN Error 697
:: The response looping did not complete |
Share a tip. Click here. |
| An internal error occurred. Restart your computer to make sure that all recent configuration changes have taken effect. |
|
DUN Error 699
:: The modem response caused a buffer overflow |
Share a tip. Click here. |
| An internal error occurred. Restart your computer to make sure that all recent configuration changes have taken effect. |
|
DUN Error 700
:: The expanded command in the device .INF file is too long |
Share a tip. Click here. |
| Commands in script files cannot exceed 256 characters. Break up the command into multiple commands. See Automating the dial-up logon process by using Windows scripting or Automating the dial-up logon process by using Switch.inf scripts. |
|
|
