[RAS] RAS Error Code & Message(Details)

Error Code	Error Message
5	ACCESS DENIED  The username and/or the Password are incorrect. Verify that the username and password are correct; spelled correctly, and are in the proper case. Check to see if the account is active.  And that nothing is in the domain name.
87	A function call to the RasDial() API from a 16-bit Windows-based application that is running in Windows 95 fails with error 87 in Windows 95 if the hWndNotifier parameter of the RasDial() API is initialized to a NULL value. An application should always provide a window handle for this parameter even if it will not be processing the messages posted by the RAS DLLs to this window. Specifying a NULL value for window handle in the RasDial() API call is common for a Visual Basic application. In such a scenario, the application makes repetitive calls to RasGetConnectStatus() to get the status of the connection. However, calling RasDial() in this fashion causes it to fail on Windows 95 with error 87. Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. Microsoft is researching this problem and will post new information in the Microsoft Knowledge Base as it becomes available.
127	Error After cu runs Copyadmn.cmd on a computer with Remote Access Service  (RAS) installed,you will receive the error: Cannot load the Remote Access  Connection Manager  service. Error 127: The specified procedure could not  be found. This behavior is by design. To restore RAS functionality, expand the following DLLs from the Windows  NT CD-ROM to your  %SystemRoot%\System32 directory. After expanding the files, have cu reapply thier current service pack and restart their computer. Expand the following files to thier system32 directory:          Rasdlg.dl_          Rasapi32.dl_          Rasfil32.dl_          Rasscrpt.dl_          Example: expand D:\i386\Rasdlg.dl_ C:\Winnt\System32\Rasdlg.dll
600	An operation is pending.
601	The port handle is invalid.
602	The port is already open.
603	Caller's buffer is too small.
604	Wrong information specified.
605	Cannot set port information.
606	The port is not connected.
607	The event is invalid.
608	The device does not exist.
609	The device type does not exist.
610	The buffer is invalid.
611	The route is not available.
612	The route is not allocated.
613	Invalid compression specified.
614	Out of buffers.
615	The port was not found.
616	An asynchronous request is pending.
617	The port or device is already disconnecting.
618	The port is not open.
619	The port is disconnected.
620	There are no endpoints.
621	Cannot open the phone book file.
622	Cannot load the phone book file.
623	Cannot find the phone book entry.
624	Cannot write the phone book file.
625	Invalid information found in the phone book.
626	Cannot load a string.
627	Cannot find key.
628	The port was disconnected.
629	The port was disconnected by the remote machine. This is usually the result of a mismatch in what the ISP requires and how the RAS entry is configured. Try the following steps one at a time. Most of these steps steps are performed in the phone book properties.      1.Change the authentication to Clear Text under Security.      2.Lower the connection speed under Modem Configuration.      3.Disable hardware flow control under Modem Configuration.      4.Disable modem error control under Modem Configuration.      5.Disable modem compression under Modem Configuration.      6.Disable software compression under Server.      7.Disable PPP LCP extensions.      8.Disable IP header compression.      9.Check DNS configuration.      10.Check the user name and password syntax (mixed case, "ppp" extension needed, and so on.) You may need to contact the ISP for assistance.      11.Connect using a Terminal window if you can get connected then there is a possible problem with CHAP or PAP. (This determines the user name and password. Set at the remote host site.) You will need to call your ISP for additional support.      12.Check to see if the modem is supported.      13.Contact the modem's manufacturer for updated modem files.      14.Try another supported modem.      15.Have the phone company check the phone lines.      16.If you are not prompted for a user name or password and you get the error message, then choose UnSave Password on the Security tab in the phone book. Try to reconnect. You should be prompted for a user name and password.      17.If running a script, disable it and try to connect with a Terminal window. If you are able to connect then there is a problem with the script file.
630	The port was disconnected due to hardware failure.
631	The port was disconnected by the user.
632	The structure size is incorrect.
633	The port is already in use or is not configured for Remote Access dialout. If Rasdial.exe terminates prematurely, it can leave the port in an indeterminate state. The port disappears from Remote Access  Server Manager if it is configured for dial-in. When a cu attempts to dial out using RAS, cu receives the error message. NOTE: This problem is not specific to Rasdial.exe. Any program that terminates prematurely without clearing the port state may cause this problem.     Stopping and restarting the Remote Access Service temporarily resolves the problem.
634	Cannot register your computer on the remote network.
635	Unknown error.
636	The wrong device is attached to the port.
637	The string could not be converted.
638	The request has timed out.
639	No asynchronous net available.
640	A NetBIOS error has occurred. If the telephone line is unusually noisy, the modem may not be able to negotiate a connection at a higher speed. Try setting the modem speed on the cu computer down to a lower speed such as 9600 bps.
641	The server cannot allocate NetBIOS resources needed to support the client.
642	One of your NetBIOS names is already registered on the remote network.
643	A network adapter at the server failed.
644	You will not receive network message popups.
645	Internal authentication error.
646	The account is not permitted to log on at this time of day.
647	The account is disabled.
648	The password has expired.
649	The account does not have Remote Access permission.
650	The Remote Access server is not responding.
651	Your modem (or other connecting device) has reported an error.
652	Unrecognized response from the device.
653	A macro required by the device was not found in the device .INF file section.
654	A command or response in the device .INF file section refers to an undefined macro
655	The  macro was not found in the device .INF file section.
656	The  macro in the device .INF file section contains an undefined macro
657	The device .INF file could not be opened. This error occurs because one or more remote access configuration files is damaged or missing. Remove the Remote Access Service, and restart the computer. Reinstall the Remote Access Service.
658	The device name in the device .INF or media .INI file is too long.
659	The media .INI file refers to an unknown device name. These errors can occur if one or more of the remote access configuration files is missing or damaged. WARNING: If you have modified the original configuration files for the Remote Access service in any way, you should back up the files before proceeding. For example, if you modified the Modem.inf file to add information for an unsupported modem, or if you modified the Switch.inf file to create a script to connect to your ISP, make sure to back up these files. To resolve this issue, replace the damaged files by removing and reinstalling the Remote Access service.
660	The device .INF file contains no responses for the command.
661	The device .INF file is missing a command.
662	Attempted to set a macro not listed in device .INF file section.
663	The media .INI file refers to an unknown device type.
664	Cannot allocate memory.
665	The port is not configured for Remote Access.
666	Your modem (or other connecting device) is not functioning.
667	Cannot read the media .INI file.
668	The connection dropped.
669	The usage parameter in the media .INI file is invalid.
670	Cannot read the section name from the media .INI file.
671	Cannot read the device type from the media .INI file.
672	Cannot read the device name from the media .INI file.
673	Cannot read the usage from the media .INI file.
674	Cannot read the maximum connection BPS rate from the media .INI file.
675	Cannot read the maximum carrier BPS rate from the media .INI file.
676	The line is busy. The Phone Number you are dialing is busy try dialing the number again, untill the line is no longer busy, or use a different phone number. Check to make sure that the phone number is correct and that you are not dialing any unnessacary numbers.
677	A person answered instead of a modem. Self explanitory.
678	There is no answer. The Phone Number you are dialing either not answering or incorrect. Make sure that the number being dialed is correct, with no extra numbers or settings, and that the dialer is configured properly. While Microsoft says that this message may also mean a problem with the PPTP connection, unless your ISP is aware of a specific network problem on thier side (or if your are  on a network), it is most likely a dialer misconfiguration.
679	Cannot detect carrier.
680	There is no dial tone.
681	General error reported by device.
682	ERROR WRITING SECTIONNAME
683	ERROR WRITING DEVICETYPE
684	ERROR WRITING DEVICENAME
685	ERROR WRITING MAXCONNECTBPS
686	ERROR WRITING MAXCARRIERBPS
687	ERROR WRITING USAGE
688	ERROR WRITING DEFAULTOFF
689	ERROR READING DEFAULTOFF
690	ERROR EMPTY INI FILE
691	Access denied because username and/or password is invalid on the domain.
692	Hardware failure in port or attached device. This error message can occur  if the modem is turned off or malfunctioning. Reset the modem.
693	ERROR NOT BINARY MACRO
694	ERROR DCB NOT FOUND
695	ERROR STATE MACHINES NOT STARTED
696	ERROR STATE MACHINES ALREADY STARTED
697	ERROR PARTIAL RESPONSE LOOPING
698	A response keyname in the device .INF file is not in the expected format.
699	The device response caused buffer overflow.
700	The expanded command in the device .INF file is too long.
701	The device moved to a BPS rate not supported by the COM driver.
702	Device response received when none expected.
703	ERROR INTERACTIVE MODE
704	ERROR BAD CALLBACK NUMBER
705	ERROR INVALID AUTH STATE
706	ERROR WRITING INITBPS
707	X.25 diagnostic indication.
708	The account has expired.
709	Error changing password on domain.
710	Serial overrun errors were detected while communicating with your modem.
711	RasMan initialization failure. Check the event log.
712	Biplex port is initializing. Wait a few seconds and redial.
713	No active ISDN lines are available.
714	Not enough ISDN channels are available to make the call.
715	Too many errors occurred because of poor phone line quality.
716	The Remote Access IP configuration is unusable.
717	No IP addresses are available in the static pool of Remote Access IP addresses.
718	PPP timeout.  When the screen comes up with the username, password, domain, you may have something in the domain line. Remove it from the domain line and that should correct the problem.
719	PPP terminated by remote machine.
720	No PPP control protocols configured. You may also receive one of the following errors when you try      to add a protocol to a phonebook entry:           The  protocol cannot be selected because it is not      installed or is disabled for Remote Access. To change this, start the      the Control Panel Network applet, choose Configure Remote Access, and      press the Network button.         -or-           The  protocol cannot be selected because it is not      installed or is disabled for Remote Access. To change, in Control Panel      start Network, choose Services page, Remote Access Properties, and      press the Network button. This problem can occur if RAS is configured to      receive calls only. To use RAS or DUN to dial out, RAS must be configured      to either dial out only or dial out and receive calls.           To resolve this problem, use the appropriate method below:        Windows NT versions 3.1, 3.5, and 3.51      1.Double-click the Control Panel icon in the Main group, and then double-click        the Network icon.      2.Under Installed Network Software, click Remote Access Service, click Configure,        and then click Configure again.      3.Under Port Usage, click either Dial Out Only or Dial Out And Receive Calls.      4.Click OK, click Continue, click OK, and then click Restart Now to restart the        computer when you are prompted.        Windows NT version 4.0      1.Click Start, point to Settings, and then click Control Panel.      2.Double-click Network, and then click the Services tab.      3.Click Remote Access Service, and then click Properties.      4.Click Configure, and then click either Dial Out Only or Dial Out And  Receive Calls.      5.Click OK, Click Continue, click Close, and then click Yes to restart the computer when you are prompted.
721	Remote PPP peer is not responding.
722	The PPP packet is invalid.
723	The phone number, including prefix and suffix, is too long.
724	The IPX protocol cannot dial-out on the port because the computer is an IPX router.
725	The IPX protocol cannot dial-in on the port because the IPX router is not installed..
726	The IPX protocol cannot be used for dial-out on more than one port at a time.
727	Cannot access TCPCFG.DLL.
728	Cannot find an IP adapter bound to Remote Access.
729	SLIP cannot be used unless the IP protocol is installed.
730	Computer registration is not complete.
731	The protocol is not configured.
732	The PPP negotiation is not converging.
733	Error over PPP due to cause unknown. The cause of this problem is unknown. You will need to call Microsoft. Error over PPP due to RAS static addresses also used by DHCP server. The remote access static address pool is not excluded from the scope(s) of the DHCP server on the same network. If the IP addresses in the RAS static address pool are also included in a DHCP scope, the IP addresses in the RAS static pool will also be assigned to clients on the LAN, which will make them unavailable to remote access clients, or can cause duplicate IP addresses on the network. Check the range of IP addresses in the RAS static address pool. From DHCP Manager, examine the range of IP addresses in      each scope. Make sure that the scope(s) and the RAS static pool do not share a common address range.      Exclude the RAS pool from the DHCP scope(s) for common IP address ranges. Error over PPP due to invalid static IP address pool range. The static IP address pool in the 'RAS Server TCP/IP Configuration' dialog box consists of IP addresses which are invalid for the network. Use a valid range of IP addresses on the network for the remote access static address pool.      If you have created subnets on the network, make sure you have configured the subnets correctly. Error over PPP due to TCP/IP bindings disabled on RAS device. The network bindings for the 'TCP/IP Protocol' or 'WINS Client TCP/IP' are disabled for the remote access device. Open the Control Panel and double-click the 'Network' icon. Click the 'Bindings' tab. Enable the bindings for 'TCP/IP Protocol' and 'WINS Client TCP/IP' on the remote access device. Error over PPP due to unknown. The cause of this problem is unknown. You will need to call Microsoft. Error over PPP due to active lease. The DHCP scope indicates that an IP address lease is already active for the RAS client. This can be caused by an error in the DHCP database, or the client failing to properly release an IP address. To force the client computer to release the IP address, type the following at the command prompt on the client: IPCONFIG /RELEASE Use DHCP Manager to delete the active lease from the DHCP scope, and reserve or exclude the IP address. Error all IP addreses in the DHCP scope are already in use by other clients. No IP addresses in the scope are available for assignment to new clients attempting to join the network. Enlarge the DHCP scope to include sufficient IP addresses for new clients, or shorten the lease duration to force clients to renew their IP address leases more frequently. If neither of these options are viable, create a new subnet on your network to create sufficient client IP addresses. Error over PPP due to DHCP server down. The DHCP server is not functioning properly or is not available to assign IP addresses to clients. Check to make sure the DHCP server is functioning properly. Error over PPP due to DHCP service stopped. The DHCP Server service is stopped on the DHCP server, or the DHCP Client service is stopped on the remote access client. Make sure the Microsoft DHCP Server service is started on the DHCP server, and the DHCP Client service is started on the remote access client. Error over PPP due to using DHCP with no DHCP server. RAS clients are unable to have their IP addresses assigned by DHCP because there is no DHCP server installed. Install a DHCP server on the subnet of the remote access clients, or create a static address pool on the RAS server to assign IP addresses to remote access clients. Error over PPP due to RAS not using TCP/IP. The Remote Access server cannot connect TCP/IP clients because the TCP/IP protocol is not selected in the RAS server network configuration. In the 'Remote Access Setup' dialog box, select the RAS device used to connect clients and click 'Network...'. In the 'Server Settings' group, select the 'TCP/IP' check box and click 'Configure...'. The PPP control protocol for this network protocol is not available on the server.
734	The PPP link control protocol terminated. The Security is set to send encrypted Passwords Most ISP's do not accept encrypted passwords. Set to send in plain text passwords by:        1) Open up Dial-up Networking        2) Click More, then click Edit Entry and Modem Properties        3) Click on the Security Tab        4) Make sure that Any Authentication including clear text is checked
735	The requested address was rejected by the server..
736	The remote computer terminated the control protocol. The Windows NT PPP server is configured to allocate TCP/IP addresses using dynamic host configuration protocol (DHCP), but there is no DHCP server on the network. To correct this error, perform one of the following steps:           Install a DHCP server on the network.          NOTE: Verify that the DHCP server has a scope that includes IP addresses on the same subnet as that of the network adapter in the Remote Access Service (RAS) server.         -or-          Configure the RAS server to use a pool of IP addresses for PPP instead of DHCP for PPP clients.         -or-          Remove TCP/IP from the RAS server.
737	Loopback detected..
738	The server did not assign an address.
739	The remote server cannot use the Windows NT encrypted password.
740	The TAPI devices configured for Remote Access failed to initialize or were not installed correctly.
741	The local computer does not support encryption.
742	The remote server does not support encryption.
743	The remote server requires encryption.
744	Cannot use the IPX net number assigned by the remote server. Check the event log.
752	A syntax error was encountered while processing a script.
1068	Error after RAS is installed (due to Service Pack). Error starting Remote Access Service on (servername). Check the Event log on (servername) for details. Error 1068: The dependency service failed to start. If you installed Remote Access Service after you installed a Service Pack, an older version of Nwlnkrip.sys is installed.   Event ID 7000 and Event ID 7001 appear in the System event log when this occurs.          To resolve this issue, reapply the Windows NT Service Pack.
20077	An error occurred in the Point to Point Protocol module on port COM x.                        The account is disabled. This error results from an RAS client's exceeding the number of bad logon attempts permitted by the setting in the Account Policy option of the User Manager. By itself, the error message text for  event 20077 does not provide the information needed to identify the RAS client responsible for the error. To track the source of the invalid logon attempts, you can enable the Auditing for Logon Failure option. To do this, go into User Manager,open the Policies menu, and use the Auditing option to enable Auditing for Logon Failure." You should then be able to correlate the failed logon error message with the RAS client that triggered the error.
20091	You are using DHCP on your network, but you have not created an active scope that includes addresses from the same subnet as the subnet of the RAS server's network card. Thier RAS server is configured to use DHCP to assign remote TCP/IP client addresses (the default option), however, there is no DHCP server on your network.