In the interests of production processes, the question arises of providing users with access to the local network of the enterprise through a VPN.

A special case of the implementation of this task is the organization of access through the MikroTik gateway using the L2TP protocol using IpSec and an authentication key (IPSec Secret). In this case, when creating users for VPN access through the L2TP server, the SSTP profile is used.

However, as practice has shown, difficulties arise with the connection, expressed in displaying error 809 to the user when he tries to connect to the local network, for example:

Elimination of this error is a complex solution to the problem and includes conditionally 3 stages.

1. Modem. When working from home, users typically use a home router provided by an Internet service provider. You need to make sure that your home router will correctly handle L2TP and IpSec protocols. An example of a solution for one of the modems is given.

From personal experience, this was enough when working in Linux.

2. Windows Firewall, by default, blocks connections required for the described type of VPN connection to certain ports. To ensure the connection, you need to open access to UDP ports 500, 1701, 4500. Purpose of these ports:

500 - ISAKMP - Internet Security Association and Key Management Protocol;

1701 - Layer 2 Forwarding Protocol (L2F) & Layer 2 Tunneling Protocol (L2TP);

4500 - NAT-T - IPSec Network Address Translator Traversal.

Launch the Windows Firewall Management snap-in and click on the "Advanced Settings" link:

You need to create 2 rules: for incoming connections and outgoing connections. Activate the corresponding item in the top menu on the left:

When prompted for the type of rule, indicate that this rule is created for a port:

Specify local UDP ports: 500, 4500, 1701

Do the same for another type of connection (in this example, further - for outgoing).

Try to establish a connection. If it doesn't help - we work further.

3. Making changes to the Windows registry.

Launch Registry Editor (regedit) and go to the branch

HKEY_LOCAL_MACHINE \ System \ CurrentControlSet \ Services \ Rasman \ Parameters

Manually editing the Windows registry to remove invalid Error 809 keys is not recommended unless you are PC service professional. Errors made while editing the registry can cause your PC to malfunction and cause irreparable damage to your operating system. In fact, even a single comma in the wrong place can prevent your computer from booting!

Because of this risk, we highly recommend using a trusted registry cleaner such as WinThruster [download] (Developed by Microsoft Gold Certified Partner) to scan and repair any Error 809-related registry problems. Using a [Download] registry cleaner can automate The process of finding invalid registry entries, missing file references (like the one causing your %% error_name %% error), and broken links within the registry. Before each scan, a backup is automatically created, allowing you to undo any changes with one click and protecting you from possible damage to your computer. The best part is that fixing registry errors [Download] can dramatically improve system speed and performance.

A warning: Unless you are an experienced PC user, we do NOT recommend manually editing the Windows Registry. Incorrect use of Registry Editor can lead to serious problems and require you to reinstall Windows. We do not guarantee that problems resulting from improper use of Registry Editor can be corrected. Your use of the Registry Editor is at your own risk.

To manually repair your Windows registry, first you need to create a backup by exporting a portion of the registry related to Error 809 (eg.Windows 8.1):

1. Click on the button To begin.
2. Enter " command" v search bar ... DO NOT PRESS YET ENTER!
3. Holding the keys CTRL-Shift on the keyboard, press ENTER.
4. A dialog box for access will be displayed.
5. Click on Yes.
6. The black box opens with a blinking cursor.
7. Enter " regedit" and press ENTER.
8. In the Registry Editor, select the Error 809-related key (eg.Windows 8.1) you want to back up.
9. On the menu File choose Export.
10. In the list Save to select the folder where you want to save the Windows 8.1 backup key.
11. In field File name type a name for your backup file, such as "Windows 8.1 Backup".
12. Make sure in the box Export range value selected Selected branch.
13. Click on Save.
14. The file will be saved with the extension .reg.
15. You now have a backup of your Windows 8.1-related registry entry.

The next steps for manually editing the registry will not be described in this article, as they can most likely damage your system. If you would like more information on manually editing the registry, please see the links below.

Setting up a VPN connection in Windows XP

This section describes how to configure VPN on Windows XP. If you are interested in how to set up a VPN in Windows Vista or Windows 7, then look at here

You can also familiarize yourself with setting up a VPN for Linux, and the instructions for configuring routers here.

New Connection Wizard

Press the button "Start" in the lower left corner of the desktop, in the appeared main menu of the system, select the item "Control Panel" if your control panel looks like "XP Style" and you cannot find the icon "Network connections", go to the classic view of the panel by selecting the appropriate item on the left side of the window:

or select "Network connections" directly from the main menu "Start":

If you have a classic view window, find the icon in it "Network connections" and open it, in the window that opens, find and run "New Connection Wizard":

In the first window, just click the button "Further":

In the second, select "Connect to the network at the workplace" and press the button "Further":

In the third select "Connecting to a virtual private network" and press the button "Further":

In the fourth, in the free field, enter a name for your connection, for example, "Internet VPN" and press the button "Further":

On some computers where there are other connections, between step 4 and step 5, an additional window appears asking you to dial the number to connect. In this case, you need to refuse to dial the number and go to step 5.

In the fifth window, enter the IP address of the default access gateway nas.iksnet(or nas3.iksnet for some subscribers) and click the "Next" button (note that there should not be any spaces or other invisible characters before and after the server name):

In the sixth, for the convenience of work, check the box "Add a shortcut to the connection to the desktop" and press the button "Ready":

Connection properties

After that, you will immediately open a connection window, at the bottom of the window find the button "Properties" and click on it:

Or press the button "Cancel" and with the connection selected, right-click on it and select "Properties":

In the window that opens, select the tab "Parameters", uncheck the box Include Windows Logon Domain:

In the "Security" tab, take off tick off the item "Data encryption required" and click on the "OK" button:

In the tab "Parameters" you can check the box opposite "Call back when the connection is broken", then, in case of an unexpected break, the connection will be restored on its own:

We connect:

Now in the field "User" you must enter the number of your contract ( for those subscribers who have a three-digit contract number, add "0" in front! For example, a contract 111 typed as 0111 .), and in the field "Password", your access password for viewing statistics and mail from the contract. Please note that there should not be any extra spaces after the contract number in the "User" field.

After a successful connection, for ease of use, on the tab "Parameters" you can uncheck the box "Prompt for name, password, certificate, etc.", then the username and password will no longer be prompted.

Save password

Attention: it is not recommended to save the password in the system, because the saved username and password can be stolen by spyware or your computer can be used to access the Internet in your absence.

Please note that Internet access control is carried out by name and password, so take this point more seriously. Do not disclose this data to unauthorized people. If your password is too simple and short, in order to increase security, we suggest changing it. You can do it yourself, from your workplace, using the client part of the new settlement system, available at the link: Statistics.There you can change the password separately for entering the statistics page and separately for accessing the Internet. We hope that there you can still find a lot of new, interesting and useful things!

Note

When the VPN connection is disconnected, you, as before, can freely use the resources of the local network, the VPN connection is needed only to access the external network. If you turned it off, then to create a VPN connection, be sure to turn on "LAN connection" otherwise, the VPN connection will not be established.

Errors

Most often, the system generates the following errors:

Error 619 or 734

• Occurs if you forgot to uncheck the "Required data encryption"In the connection properties, the" Security "tab.

Error 629

This error occurs if your username and password are already connected (remember if you did not let any of your friends use your Internet), if not, then this connection is not broken on the server. To do this, wait 10 minutes, and then try to reconnect after this time ... If nothing helped from the 3rd attempt, then I advise you to contact the support service.

Error 650

"The Remote Access Server is not responding":

• Internet access server unavailable. Check if "Local Area Connection" is turned on, if the network card is working, if the network cable is working, if a specific IP address is set in the IP connection settings.

Error 651 or 800

Your modem (or other device) reported an error " or "There is no connection with the VPN connection server"

• These errors can occur if you removed or disabled the old "Local Area Connection" connection.
• Or if you specified in step 5 wrong address... Check it out, make sure the numbers are separated by periods and not commas.
• Firewall blocks outgoing requests for VPN connections.
• The request does not reach the server for some reason, i.e. it is possible that the gateway of your segment is not allowing the request due to the arisen load or failure.
• The server sends a response about the impossibility to connect because there are a lot of concurrent connection attempts at the moment.

Possible fixes

• Check if the local network is working at this point in time.
• Check the signal flow with the ping command to your gateway, and then to your authorization server.
• Fix the key pair in the registry or reinstall Windows

Error 678

"No response received"

• If it does not help, then try to recreate the VPN connection again (pay attention to the connection type, it must be PPTP, not PPPoE or L2TP).
• Also, this error can occur when negative balance your personal account.

Error 679

• This error occurs when the network adapter is disabled. You need to enable the network adapter by going to "START-> Control Panel-> System-> Device Manager-> Hardware".

Error 691 or 718

"Wrong login or password"

• Check if the login (contract number) is typed correctly. It must be 4-digit (three-digit contract numbers must be padded with a leading zero). Try typing your username and password again. When typing, check that the correct keyboard layout (typing language) is turned on, the state of the Caps Lock indicator.
• Or if at the moment
• If the operating system does not offer to enter a username and password when connecting, then you must do the following: Open the "Control Panel", select "Network Connections", right-click on your VPN connection and select "Properties" from the menu. The properties of the VPN connection will open. Now you need to go to the "Options" tab and check the box next to "Request a name, password, certificate, etc.". After that, confirm the changes by clicking the "OK" button. The next time you connect, you will be prompted for a username and password.

Error 711

This error occurs when the required service is not running on the computer. In this case, it is impossible to connect to the network, and also in some cases - the installation of network adapters. This problem can occur if some or all of the following services are not running.

• Plug and Play Plug and Play Support
• Remote Access Automatic Connection Manager
• Remote Access Connection Manager
• Telephony

To resolve this error, follow these steps for each of the above services.

1. Open the Administrative Tools by clicking the Start button and selecting Control Panel, System and Maintenance, and Administrative Tools. Administrator Permission Required Enter the administrator password or confirm password if prompted.
2. Double click Services. Administrator permission required Enter the administrator password or confirm the password if prompted.
3. Right-click one of the above services and then click Properties.
4. On the General tab, under Startup Type, select Manual.
5. Click Apply and then click Run.

Error 720

"Unable to connect to remote computer."

This error occurs when the network protocol stack in Windows is damaged. You can check the integrity of the stack using the netdiag utility.

• Enter the command

netdiag / test: winsock

• Netdiag displays the results of a number of network components, including Winsock. For more information about this test, type the netdiag command in the following form:

netdiag / test: winsock / v

• If Netdiag reports an error, you must restore the Winsock2 registry key.
• The easiest and fastest solution:

netsh int ip reset resetlog.txt netsh winsock reset

• After that, we restart the computer and configure the local network connection, since executing this command will overwrite the registry settings that are used by the TCP / IP protocol stack, which is equivalent to removing it and reinstalling it. Recreate the VPN connection if necessary.
• If this does not help, then you can completely reinstall the TCP / IP stack like this:

1. Delete the registry key with REG DELETE HKEY_LOCAL_MACHINE \ System \ CurrentControlSet \ Services \ Winsock
2. Delete the registry key with the REG DELETE command HKEY_LOCAL_MACHINE \ System \ CurrentControlSet \ Services \ Winsock2
3. Reboot your computer
4. Open the folder% winroot% \ inf
5. Find the nettcpip.inf file in it, make a backup copy and then open it in a text editor (eg Notepad).
6. Find the lines in it:

; TCPIP has properties to display Characteristics = 0xA0; NCF_HAS_UI | NCF_NOT_USER_REMOVABLE

1. Fix them to:

; TCPIP has properties to display Characteristics = 0x80; NCF_HAS_UI

1. Save changes to nettcpip.inf file
2. Open Network Connections and by right-clicking on the property of the network connection we need, select Install-> Protocol-> Add. Then select "have disk" and specify the path% winroot% \ inf (usually this folder is hidden!)
3. Select TCP / IP from the list. After that, you will again be taken to the network connection properties window, but for TCP / IP, the Uninstall button will now be active.
4. Select TCP / IP from the This connection uses the following items list and click the Uninstall button.
5. Reboot your computer
6. Install TCP / IP protocol in the same way as in steps 2-5.

• If all of the above does not work, then look at the instructions at

Error 733

• Occurs if you forgot to uncheck all protocols except Internet protocol and QoS.

Error 734

• Most likely you have a virus WIN32.Sality.

Error 735

• "The requested address was rejected by the server": Occurs if you entered IP address in "TCP / IP Properties"(it should be obtained automatically).

Errors 741 - 743

"Encryption settings are incorrect"

• Go to the VPN connection settings, and in the "Security" tab, turn off the "data encryption" item.

Error 764

"Smart card readers not installed"

• This error occurs if you configured the VPN connection incorrectly. Try to remove it and configure it again according to these instructions.

Error 769

"The specified destination is unreachable"

• The error occurs due to a disconnected local network connection or the absence of a physical link. It is recommended to check the LAN status (must be on) and the physical network connection (network cable must be connected).
• Sometimes it occurs if the router, for some reason, did not issue the correct IP address via DHCP

Error 781

"The encoding attempt failed because no valid certificates were found."

• Reasons: VPN client tries to use L2TP / IPSec protocol to connect.
• Tip: Go to connection settings VPN-Properties-> Network-> VPN type and select PPTP VPN

Error 789

"Wrong VPN connection type selected"

• Go to the VPN connection settings and on the "Network" tab from the "VPN Type" list select "Automatic" or "PPTP". Try to reconnect.
• This error also occurs if you made a mistake when entering the IP address, and enter commas instead of periods to separate octets.

Error 807

If you are using the "Automatic" VPN connection type, try changing to "PPTP". In the properties of the network card, set Receive-Side Scaling State - disable and Receive Window Auto-Tuning Level - disable. It is also possible that the connection to the access server is blocked by a firewall (firewall). You can also re-create the VPN connection according to the instructions, if the problem persists, uninstall the KB958869 system update, or restore the system to an earlier state.

Error 809

Occurs when:

1Using L2TP VPN connection type in Windows Vista and Windows 7 because the connection is blocked by the Windows firewall. Solution: Correct the VPN connection type to PPPtP. Enable Routing and Remote Access (PPPtP) firewall rule

2 Blocking by the firewall or antivirus with firewall function you installed Solution: Correctly configure your firewall.

Error 1717

"Unknown interface"

• Try restarting your computer
• If it does not help, then run from the command line (check the integrity of system files)

sfc / scannow

Configuring VPN connection in Windows Vista / 7

New Connection Wizard

Similarly, setting up a VPN connection in Windows XP, start "Setting up a connection or network" and select "VPN connection":

We select the creation of a new connection and type PPTP, then press the button Further:

If you have not yet created a single VPN connection, then in the window that appears, select "Use my Internet connection (VPN)"

If connections have already been created in the system, then in the window that appears, select "No, create a new connection"

Fill in the field for the server address, put a tick Don't connect now and press the button Further:

Enter in the field Username contract number, and in the field Password- the password for the VPN connection (specified in Appendix # 2 to the agreement as the Password for viewing statistics, mail and VPN connections) and press the button Create:

VPN connection properties

After that, select "VPN connection properties" and fix in the marked places:

If you uncheck the box "Prompt for name, password, certificate, etc." then when the connection is made, the computer will not display the connection window and ask for a username and password. If Windows forgets the login and password (and this happens), the connection will not be established. Error 691 will be displayed. In this case, the user will not be prompted to re-enter the username and password. What to do in this case.

The connection shortcut on the desktop in Windows Vista and 7 can be done as follows: Open the "Network and Sharing Center", in the left column, click the link "Changes to adapter settings", in the window that opens you need to find your "VPN connection" (the name may be different depending on how you specified the Destination Name during setup). Right click on the connection and select "create shortcut". By default, you will be prompted to position this shortcut on your desktop. Click "Yes".

Errors

Error 609

This method of solving the problem does not always work.

1. Run Command Prompt (CMD) as Administrator
2. Enter the following commands (remove miniport drivers):

C: \> netcfg -u ms_l2tp C: \> netcfg -u ms_pptp

1. Now the following two (installing miniport drivers):

C: \> netcfg -l% windir% \ inf \ netrast.inf -c p -i ms_pptp C: \> netcfg -l% windir% \ inf \ netrast.inf -c p -i ms_l2tp

Error 619

"Port disabled"

Possible causes and solutions:

1. Operating system problems. In this case, we recommend contacting specialists.
2. Firewall is enabled. In this case, we recommend disabling the firewall.

Error 651

"Your modem (or other device) reported an error."

Possible causes and solutions (in order of execution):

1. Operating system crash. In this case, we recommend that you restart your computer.
2. The driver of the network card is downed. We recommend that you reinstall the drivers and re-configure the network.
3. OS malfunctions. We recommend that you reinstall the operating system.
4. The network card is defective. We recommend replacing the network card.

Error 678

"No response"

Often occurs when MAC-IP binding is down. At the same time, VPN servers and gateway are not pinged. In this case, it is recommended to call us and reset the MAC-IP binding.

The error may appear if an attempt is made to connect to a server that does not support PPTP VPN. We recommend that you reconfigure the VPN connection using the Autoconfigurator or manually check the settings.

Error 691 (Vista / 7)

"Access denied because such username and password are not valid in this domain."

Appears in the following cases:

1. Incorrect username / password entered. Completely clear the login / password entry window and retype them. Login must be 4-digit (three-digit contract numbers must be padded with a zero in front). When typing, check that the correct keyboard layout (typing language) is turned on, the state of the Caps Lock indicator.
2. The VPN session was not completed correctly (connection failure, abnormal computer shutdown). In this case, you need to wait a few minutes.
3. Or if at the moment a connection has already been created with your username and password... (If you have more than one computer connected).
4. Quite often it happens that Windows "forgets" the entered username and password, and then they must be re-entered, after deleting them from the input fields.

• If the operating system does not prompt you to enter a username and password when connecting, then you must do the following: Open the "Control Panel", select "Network and Sharing Center", in the left column, go to the link "Change adapter settings", right-click click on your VPN connection and select "Properties" from the menu. The properties of the VPN connection will open. Now you need to go to the "Options" tab and check the box next to "Request a name, password, certificate, etc.". After that, confirm the changes by clicking the "OK" button. The next time you connect, you will be prompted for a username and password.

Error 711

run in the command line with Administrator rights:

Secedit / configure / cfg% windir% \ inf \ defltbase.inf / db defltbase.sdb / verbose

in order to start the command line with administrator rights, you must click the start menu, then in the run tab, type cmd in the English layout, an icon with the inscription cmd will appear in the menu, right-click on it and select "Run with administrator rights"

Error 814

"Basic Ethernet connection not found"

• The error is caused by the unavailability of the network adapter used for this connection.

Error 868

"DNS name not resolved"

• This error occurs only on "Windows 7". The crux of the problem is that the DNS client is unstable in some "builds" of this Windows.
• Solution:
  • Check that the addresses of DNS servers in the local network connection are obtained automatically (at the moment, 10.0.1.5 and 192.168.2.1 should be issued)
  • Disable IPv6 (or better - everything except IPv4) in the properties of the local area network connection
  • Set the access server address instead of nas.iksnet in the form of an IP-address (You need to select one of the server addresses. You can check them with the command ping nas.iksnet, currently 10.0.1.13 and 10.0.1.14)
  • In some cases, resetting directories helps: at the command line, enter the commands

netsh int ip reset c: \ log netsh winsock reset ipconfig flushdns

VPN setup in Windows 8

1. Open the start menu

2.From the Start menu select the Desktop tile

3. Right-click on the Network icon in the system tray (located in the lower right corner) and select "Network and Sharing Center".

4. In the "Network and Sharing Center" select "Create and configure a new connection or network"

5. Select "Connect to a workplace", click "next"

6.Select "Use my internet connection (VPN)"

7. Click "Postpone Internet Connection Setup"

8. In the line "Internet address" enter nas.iksnet and click "next", then "Create"

9.Return to the "Network and Sharing Center", on the left side in the menu, select "Change adapter settings"

10. Right-click on the created connection and select the "Properties" menu. Switch to the "Security" tab and set the parameters as shown in the figure. Click OK.

NOTE: If, on the tab Options uncheck "Prompt for name, password, certificate, etc." then when the connection is made, the computer will not display the connection window and ask for a username and password. If Windows forgets the login and password (and this happens), the connection will not be established. Error 691 will be displayed. In this case, the user will not be prompted to re-enter the username and password. What to do in this case.

11.Click the left mouse button on the Network icon in the system tray (located in the lower right corner). The window that appears will display a list of all VPN connections created on this computer. Select the connection you need and click "Connect".

12.In the window that opens, enter your username and password. In the Username field, enter the contract number, and in the Password field, the password for the VPN connection (specified in Appendix # 2 to the contract as Password for viewing statistics, mail and VPN connections) and press the OK button.

If you have any problems with the setup, contact the technical support service.

Configuring VPN on Linux

Debian

First, install the required package:

$ apt-get install pptp-linux

Then edit the file describing the network interfaces. Here's an example:

$ cat / etc / network / interfaces auto lo iface lo inet loopback auto eth0 ppp9 iface eth0 inet dhcp iface ppp9 inet ppp provider iksnet pre-up ip link set eth0 up

Then edit the file describing your VPN connection. It should be something like this:

$ cat / etc / ppp / peers / iksnet unit 9 lock noauth nobsdcomp nodeflate #mtu 1300 persist maxfail 3 lcp-echo-interval 60 lcp-echo-failure 4 pty "pptp nas.iksnet --nolaunchpppd --loglevel 0" name # Your contract number remotename iksnet ipparam iksnet defaultroute replacedefaultroute usepeerdns #nodebug kdebug 0

After that, enter your credentials = contract number, = VPN password in the file (note the quotes for the password):

$ cat / etc / ppp / chap-secrets * "" *

After that, you can manually connect the VPN:

$ ifup ppp9

And turn off:

$ ifdown ppp9

The connection can be checked using the command:

$ ifconfig ppp9 ppp9 Link encap: Point-to-Point Protocol inet addr: 89.113.252.65 PtP: 10.0.1.11 Mask: 255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU: 1450 Metric: 1 RX packets: 40 errors: 0 dropped: 0 overruns: 0 frame: 0 TX packets: 418 errors: 0 dropped: 0 overruns: 0 carrier: 0 collisions: 0 txqueuelen: 3 RX bytes: 7750 (7.5 KiB) TX bytes: 1189 (1.1 KiB)

We wish you pleasant work and sincerely hope for constructive cooperation in order to improve the quality of services. You can leave your questions and wishes in the "HelpDesk" section of the new billing system - these questions will be visible only to our technical service, or by calling 2-55-24.

If at starting a VPN connection an error has occurred, you need to remember its three-digit code. Errors with a 6XX code (errors associated with incorrectly entering a password, name or choosing the type of communication protocol and indicate that the network is working, but it is necessary to check the entered data), 7XX (errors related to incorrect and indicate that the network is working , but you need to check the settings) or 8XX (errors related to problems with network configuration or lack of network connection.

Installed anti-virus software and especially firewalls can block the establishment of a VPN connection, for example, causing errors 789 and 792. In this case, you must enable UDP ports 500 and 4500 in the security settings for communication with the VPN concentrator.

If the VPN connection cannot be established and gives an error

Also, problems with establishing a VPN connection does not occur on computers directly connected to the Internet with obtaining an IP address forwarded on the Internet (and not an address from the private address space: 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/24). Otherwise, your local network administrator (or ISP if you got a private IP address from it) must set up address translation (NAT / PAT).

Please note that connecting your computer to the Internet means that you can exchange data at the network (IP) level with any other computer on the Internet. Protocols used for VPN connection setup(IPsec protocols) are peers on the Internet with any other protocols that run over a network layer protocol (IP) - for example, HTTP for browsing the web or SMTP for sending e-mail. If your ISP allows web browsing, but it blocks the establishment of a VPN connection, this is an artificial limitation of your access to the Internet.

Make sure the following Windows XP services are running (Start - Control Panel - Administrative Tools - Services):
- "Telephony";
- "Manager of automatic connections for remote access";
- "Remote Access Connection Manager".

To enable them on the command line, run the following commands:

sc config RasAuto start = demand
sc config RasMan start = demand
sc config TapiSrv start = demand

Error	Cause	Solution
678		If the operating system is Windows XP, open the registry editor (regedit.exe) and check if there is a ProhibitIpSec parameter in the HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ services \ RasMan \ Parameters key. If it is present and has the value "1", then change it to "0" and restart the computer. Attention!!! If your ISP uses an l2tp VPN connection to provide Internet access, changing this parameter may lose Internet access. In this case, you need to return the setting to "1" and reboot.
691	Incorrect username and / or password entered	Enter the correct username and password. Or, if this VPN connection has already worked before, you must re-enter your login password.
692	Problems with Windows Firewall Seven	Disable firewall.
720		This error occurred quite recently, it seems that after the next update for Windows 7 instead of error 738, error 720 appeared. Unlike the second problem leading to error 720 described below, this error occurs only on a PC with Windows 7 and occurs after it has passed " Checking the username and password ... "and" Registering the computer on the network ... ". Thus, for error 720 with such symptoms, the solution is described in paragraph with 738th error.
734	The VPN type is set to "Automatic"	In the properties of the VPN connection on the "Network" tab, change the VPN type from "Automatic" to "L2TP IPSec VPN". If it does not help, you need to recreate the connection.
738	VPN user with this login is already connected	If you need to work simultaneously via VPN from several workstations, you must use different usernames.
766	Pre-shared key not saved	Open the properties of the VPN connection, go to the "Security" tab, click on the "Additional parameters" button and in the window that opens, enter the pre-shared key in the "Key" field.
768	IPSec service not started	Make a right-click on the "My Computer" icon, select the "Management" menu item. In the window that opens, expand "Services and Applications" and select "Services". Find the "IPSec Services" service. Run it and set the startup type to "Auto".
769	The address of the VPN concentrator is entered incorrectly, the DNS service is not configured, or there is no Internet connection	Re-enter the VPN concentrator address. If the address is entered correctly, check the connection with the VPN concentrator. If there is no connection, contact your system administrator or your Internet provider.
781	Pre-shared key not entered	In the properties of the VPN connection, enter the pre-shared key provided to you.
789	The "IPsec Key Modules ..." service is not running	If the operating system is Windows 7 or Vista, Windows XP, then right-click on the icon "My Computer", select the menu item "Manage". In the window that opens, expand "Services and Applications" and select "Services". Find the "IPsec Key Modules ..." service. Run it and set the startup type to "Auto".
789	see error 792
792	Invalid pre-shared key entered	Re-enter the pre-shared key
792	The connection is made using NAT technology without SP2 installed on a computer running Windows XP	Install SP2 for Windows XP
792	UDP packets are blocked	Allow UDP ports 500 and 4500 to communicate with the VPN Concentrator. If you are using an IP address from the private address space (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/24), then you need to configure address translation (NAT / PAT).
800	see bug 734
809	The operating system is globally prohibited from using encryption	If the operating system is Windows 7 or Vista, open the registry editor (regedit.exe) and check if the HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ services \ RasMan \ Parameters key contains the ProhibitIpSec parameter. If it is present and has the value "1", then change it to "0" and restart the computer. Attention!!! If your ISP uses to provide Internet access, L2tp VPN connection If you change this parameter, Internet access may be lost. In this case, you need to return the setting to "1" and reboot.

Error codes for creating dial-up connections and VPN connections.

Listed are error codes that occur when creating dial-up or VPN connections on client computers running Windows 2000, Windows XP, and Windows Server 2003.

Errors with codes more than 900 appear only when connecting to a Routing and Remote Access server running Windows 2000 or a later operating system.

Error 600 The operation started is not completed.
Recommendation:

Error 601 An invalid port descriptor was found.
Recommendation: An internal error has occurred. Restart your computer to make sure any recent configuration changes take effect.

Error 602 The specified port is already open.
Recommendation: The COM port to be used by the network connection is already in use by another active network connection or process (for example, a telephone line monitoring program such as a fax program). Exit the application blocking the COM port

Error 603 The caller's buffer is too small.
Recommendation: An internal error has occurred. Restart your computer to make sure any recent configuration changes take effect.

Error 604 Invalid information provided.
Recommendation: The dial-up phone book file and the current dial-up network configuration may not be compatible. If you have replaced your communications hardware (serial port or modem), check the Dial-up Networking configuration.

Error 605 Unable to set port information.
Recommendation:

Error 606
Recommendation: An internal error has occurred. Restart your computer to make sure any recent configuration changes take effect.

Error 607 Invalid event encountered.
Recommendation: An internal error has occurred. Restart your computer to make sure any recent configuration changes take effect.

Error 608 A non-existent device was specified.
Recommendation: The dial-up phone book file and the current dial-up network configuration may not be compatible. If you have replaced your communications hardware (serial port or modem), check the Dial-up Networking configuration. If this error continues to occur, delete and re-create the dial-up network connection.

Error 609 A non-existent device type was specified.
Recommendation: The dial-up phone book file and the current dial-up network configuration may not be compatible. If you have replaced your communications hardware (serial port or modem), check the Dial-up Networking configuration. If this error continues to occur, delete and re-create the dial-up network connection.

Error 610 Invalid buffer specified.
Recommendation: An internal error has occurred. Restart your computer to make sure any recent configuration changes take effect.

Error 611 The specified route is not available.
Recommendation:

Error 612 The specified route is not allocated.
Recommendation: The network configuration is probably wrong. Restart your computer to make sure any recent configuration changes take effect. This error can also occur if your computer is running low on resources.

Error 613 Invalid compression type specified.
Recommendation: An internal error has occurred. Restart your computer to make sure any recent configuration changes take effect.

Error 614 Insufficient buffers available.
Recommendation: An internal error has occurred. Restart your computer to make sure any recent configuration changes take effect.

Error 615 The specified port was not found.
Recommendation: The dial-up phone book file and the current dial-up network configuration may not be compatible. If you have replaced your communications hardware (serial port or modem), check the Dial-up Networking configuration. If this error continues to occur, delete and re-create the dial-up network connection.

Error 616 The asynchronous request has been suspended.
Recommendation: An internal error has occurred. Restart your computer to make sure any recent configuration changes take effect.

Error 617 The modem is already disconnecting.
Recommendation: Wait for Dial-Up Networking to complete the connection.

Error 618 The specified port is not open.
Recommendation: An internal error has occurred. Restart your computer to make sure any recent configuration changes take effect.

Error 619 The specified port is not connected.
Recommendation: Restart your computer to make sure any recent configuration changes take effect.

Error 620 Failed to determine endpoints.
Recommendation: The network configuration is probably wrong. Restart your computer to make sure any recent configuration changes take effect.

Error 621 The system was unable to open the phone book file.
Recommendation:

Error 622 The system was unable to load the phone book file.
Recommendation: Remote Web Access uses the Rasphone.pbk file located in the \ System32 \ Ras directory. Make sure the file is in this directory and then restart Remote Access to the Network.

Error 623 The system could not find a phonebook entry for this connection.
Recommendation: Dial-up Networking has found the phone book, but cannot find an entry that matches the connection. This error will not occur unless another application is using the Dial-Up Networking phonebook and specifies an invalid connection entry.

Error 624 The system was unable to update the phone book file.
Recommendation: Remote Web Access uses the Rasphone.pbk file located in the \ System32 \ Ras directory. Make sure your disk is not full and you have permission to modify this file.

Error 625 The system found invalid data in the phone book file.
Recommendation: The phone book file Rasphone.pbk may be damaged. Delete this file from the \ System32 \ Ras directory, then restart the Remote Access to the Net in order to create a new phone book.

Error 626 Failed to load string.
Recommendation: An internal error has occurred. Restart your computer to make sure any recent configuration changes take effect.

Error 627 The key could not be found.
Recommendation: One of the Remote Access Network configuration files may contain incorrect information. If you are using a modem that is not supported by your version of Windows, install a supported modem.

Error 628 The connection was closed.
Recommendation: If this is a dial-up connection, try overdriving. If you continue to receive this message, reduce the initial modem speed and disable advanced modem settings. If this problem continues to persist, contact your system administrator. If it is a virtual private network (VPN) connection, access may be denied due to remote access policy or otherwise.

Error 629 The connection was closed by the remote computer.
Recommendation:
Fatal phone line error.
Line noises.
Disabled by the system administrator.
Unsuccessful attempt to connect to the modem of the remote access server at the selected speed.
To re-establish the connection, click "Re-dial". You can also activate automatic redial in the Properties section for this connection. If this error occurs in the future, reduce the connection speed of the modem to 9600 bps, and then try to call again.
You can try connecting to a different server in order to determine if this problem is related specifically to the north you are trying to reach. Also, you can try to connect to your server from a different phone line.

Error 630 The modem was disconnected due to a hardware error.
Recommendation: The connection was dropped for one of the following reasons:
An unrecoverable error has occurred in your modem (or other communications equipment).
An unrecoverable error has occurred on your communication port.
Your modem cable is disconnected.
To diagnose and fix the problem, do the following:
Make sure your modem is turned on and the cable is securely connected.
Make sure your modem is functioning properly.

Error 631 The user disconnected the modem.
Recommendation: Due to an event on your computer, the connection was dropped. Call back.

Error 632 Incorrect structure size detected.
Recommendation: An internal error has occurred. Restart your computer to make sure any recent configuration changes take effect.

Error 633 The modem is already in use or not configured for outbound dial-up connections.
Recommendation: If it is a dial-up connection, the COM port to be used by the network connection is already in use by another active network connection or process (for example, a telephone line monitoring program such as a fax program). Exit the application blocking the COM port. If it is a virtual private network (VPN) connection, the VPN device to be used by the network cannot be opened. If this problem continues to persist, contact your system administrator.

Error 634 Failed to register the computer on the remote network.
Recommendation: The Remote Access Server cannot register your computer name on the network. Most often this is possible with the NetBIOS protocol, however, it can also happen with the TCP / IP or IPX protocols. This usually happens if the address is already in use on the network. Contact your system administrator.

Error 635 An unknown error has occurred.
Recommendation: An internal error has occurred. Restart your computer to make sure any recent configuration changes take effect.

Error 636 The device connected to the port is not as expected.
Recommendation: It is possible that your hardware configuration and the configuration settings for your connection are incompatible with each other. If you have replaced your communications hardware (serial port or modem), check the Dial-up Networking configuration.

Error 637 A string was found that could not be converted (converted).
Recommendation: An internal error has occurred. Restart your computer to make sure any recent configuration changes take effect.

Error 638 The request has expired.
Recommendation: An internal error has occurred. Restart your computer to make sure any recent configuration changes take effect.

Error 639 There is no asynchronous network available.
Recommendation: Your NetBIOS network may be misconfigured. Restart your computer to make sure any recent configuration changes take effect.

Error 640 An error has occurred affecting NetBIOS.
Recommendation: The modem cannot establish a connection at the specified speed. Reduce the initial modem speed and call back. Also, try disabling hardware and software compression. If the connection still fails, try adding the NWLink IPX / SPX / NetBIOS Compatible Transport Protocol.

Error 641 The server was unable to allocate NetBIOS resources required to support this client.
Recommendation: Ask your system administrator to increase the capacity of the remote access server resource, or use Services in Computer Management to stop nonessential services on your computer, such as Messenger and Network DDE.

Error 642 One of the NetBIOS computer names is already registered on the remote network.
Recommendation: Another computer with the same name is already connected to the remote network. Each computer on this network must be registered with a unique baud name. Check the following:
Is the computer with the same name as yours on the network to which you are connecting.
Is your computer physically connected to the network you are trying to connect to?

Error 643 Server network adapter error.
Recommendation: Please report the error to your system administrator.

Error 644 No pop-up network messages will be received.
Recommendation: Another computer already connected to this network uses your name to receive network messages. Messages addressed to you are sent to this computer. If you want to receive messages to your remote workstation, you must log out of your office computer before dialing into the network next time. This error does not affect messages from Microsoft Outlook, Microsoft Outlook Express, or Microsoft Exchange.

Error 645 An internal authentication error has occurred.
Recommendation: An internal error has occurred. Restart your computer to make sure any recent configuration changes take effect.

Error 646 The user with this account is not allowed to log in at this time of day.
Recommendation: Your account is configured for time-of-day network access. If you need to log on to the network at a different time of day from the one currently configured, ask your system administrator to change the configuration.

Error 647 Account is disabled.
Recommendation: The user account has been disabled. This could be due to multiple, repeated failed connection attempts, or because the system administrator disabled the account for security reasons (or for non-payment). Ask your system administrator to enable your account.

Error 648 The password for the account has expired.
Recommendation: You need to change your password.
If you connect via Dial-up Networking, you will automatically be prompted to change your password. If you are connecting using the rasdial command, you can change the password by doing the following:
Press CTRL + ALT + DEL.
Click "Change Password" and then follow the instructions that appear on the screen.
If you belong to the Administrators group and your password has expired, another administrator must change your password. You cannot change your password yourself.

Error 649 The account is not authorized to dial.
Recommendation: The account does not have access to the server for one of the following reasons:
Your account on the selected server is valid, but you do not have remote network access rights. Ask your system administrator to set the remote access permission for your account, or set the permission in Routing and Remote Access.
Your account has expired and your account has been disabled or your remote access has been closed.
You are trying to connect to the server outside the allowed time of day, the number of connection attempts has exceeded the maximum allowed, or your account may not allow remote login.
Your account settings can prevent connections. For example, your account may only allow connections from certain phone numbers. The remote computer can only allow connections to local accounts.
It is possible that your computer does not support the requested authentication protocol, or your computer is trying to use a protocol that the remote computer does not accept.
If you have an account with remote access rights on a different domain, do the following to use your account on that domain:
1. Right-click on the connection, then select Properties.
2. On the Properties tab, select. Prompt for username and password, certificate, etc. and enable Windows logon domain checkboxes.
3. On the Security tab, clear the Automatically use my username, password and domain checkboxes, then click OK.
4. Double click on the connection, then click Dial.
5. Provide the appropriate username, password, and domain.

650 The Remote Access Server is not responding.
Recommendation: The error can be caused by one of the following:
The remote access server is not running. Check with your system administrator to make sure the server is running.
The line may be too noisy, or your modem could not correctly establish a connection with the modem of the remote access server at the selected speed. For both of these reasons, lower the initial bps rate of the modem and then call back.
Check the HCL to make sure your modem is listed there. For the most up-to-date list of supported modems, see the Microsoft website at www.microsoft.com. If your modem is listed, contact the modem manufacturer for a driver update.
The serial cable of the modem may need to be replaced.
The authentication settings for this connection may be incorrect. Check with your system administrator to ensure that your authentication settings meet the requirements of the remote access server.
The remote access server may have both software and hardware compression enabled. Typically, remote access servers have software compression enabled and hardware compression disabled.

Error 651 The modem reported an error.
Recommendation: Your modem (or other device) reported an error. If you are using a dial-up connection and are using a supported external modem, turn off and then turn on the modem. Close and restart Dial-up Networking, and then call back. If your modem is not supported by Dial-up Networking, switch to a supported modem. For the most up-to-date list of supported modems, see the Microsoft website at www.microsoft.com. Make sure you have correctly configured your modem for remote access. If it is a virtual private network (VPN) connection, you may have incorrectly entered the TCP / IP address in your network configuration, or the server you are trying to connect to may not be available. To determine if the server is free, contact your system administrator.

Error 652 Modem response not recognized.
Recommendation: Your modem (or other device) generated a message that is missing from one of your script files (Pad.inf, Switch.inf, or filename.scp). If you are using a supported external modem, turn off and then turn on the modem, and then call back. If this problem continues to occur, try connecting at a lower initial speed. For the most up-to-date list of supported modems, see the Microsoft website at www.microsoft.com.

Error 653 The macro required by the modem was not found in the device .inf file.
Recommendation:

Error 654 The command or response in the device INF section refers to an undefined macro.
Recommendation: It is possible that one of the Remote Access Network configuration files contains invalid information. If your modem is not supported by Dial-up Networking, switch to a supported modem. For the most up-to-date list of supported modems, see the Microsoft website at www.microsoft.com.

Error 655 The macro was not found in the .INF file section.
Recommendation: It is possible that one of the Remote Access Network configuration files contains invalid information. If your modem is not supported by Dial-up Networking, switch to a supported modem. For the most up-to-date list of supported modems, see the Microsoft website at www.microsoft.com.

Error 656 The macro in the .INF file section contains an undefined macro.
Recommendation: It is possible that one of the Remote Access Network configuration files contains invalid information. If your modem is not supported by Dial-up Networking, switch to a supported modem. For the most up-to-date list of supported modems, see the Microsoft website at www.microsoft.com.

Error 657 Could not open device .inf file.
Recommendation: It is possible that one of the Remote Access Network configuration files contains invalid information. If your modem is not supported by Dial-up Networking, switch to a supported modem. For the most up-to-date list of supported modems, see the Microsoft website at www.microsoft.com.

Error 658 The device name is too long in the device INF file or in the media INI file.
Recommendation: It is possible that one of the Remote Access Network configuration files contains invalid information. If your modem is not supported by Dial-up Networking, switch to a supported modem. For the most up-to-date list of supported modems, see the Microsoft website at www.microsoft.com.

Error 659 The media INI file refers to an unknown device name.
Recommendation: It is possible that one of the Remote Access Network configuration files contains invalid information. If your modem is not supported by Dial-up Networking, switch to a supported modem. For the most up-to-date list of supported modems, see the Microsoft website at www.microsoft.com.

Error 660 The device INF file does not contain any responses for this command.
Recommendation: It is possible that one of the Remote Access Network configuration files contains invalid information. If your modem is not supported by Dial-up Networking, switch to a supported modem. For the most up-to-date list of supported modems, see the Microsoft website at www.microsoft.com.

Error 661 The device INF file is missing a command.
Recommendation: It is possible that one of the Remote Access Network configuration files contains invalid information. If your modem is not supported by Dial-up Networking, switch to a supported modem. For the most up-to-date list of supported modems, see the Microsoft website at www.microsoft.com.

Error 662 An attempt was made to install a macro that is not listed in the device INF file section.
Recommendation: It is possible that one of the Remote Access Network configuration files contains invalid information. If your modem is not supported by Dial-up Networking, switch to a supported modem. For the most up-to-date list of supported modems, see the Microsoft website at www.microsoft.com.

Error 663 The media INI file refers to an unknown device type.
Recommendation: It is possible that one of the Remote Access Network configuration files contains invalid information. If your modem is not supported by Dial-up Networking, switch to a supported modem. For the most up-to-date list of supported modems, see the Microsoft website at www.microsoft.com.

Error 664 Not enough memory.
Recommendation: The system is out of memory. Close some programs and then call back.

Error 665 The modem is not configured.
Recommendation: If the device is already in use by another connection, terminate that connection. Reconfigure the connection to use a different device.

Error 666 The modem is not working properly.
Recommendation: Your modem (or other device) is not responding for one of the following reasons:
The external modem is turned off.
The modem is not securely connected to the computer. Make sure the cable is securely connected to both the modem and the computer.
The serial cable does not meet the requirements for Remote Network Access.
The modem is experiencing hardware problems. Turn off the modem, wait 20 seconds, and turn on the modem.

Error 667 The system was unable to read the media .INI file.
Recommendation: It is possible that one of the Remote Access Network configuration files contains invalid information. If your modem is not supported by Dial-up Networking, switch to a supported modem. For the most up-to-date list of supported modems, see the Microsoft website at www.microsoft.com.

Error 668 The connection was interrupted.
Recommendation: Call over. If you continue to receive this message, cancel the initial modem speed and disable advanced modem options such as software compression. If this problem continues to occur, contact your system administrator. Also, you must make sure the modem is compatible. For the most up-to-date list of supported modems, see the Microsoft website at www.microsoft.com. If you are dialing manually, make sure you are in a connected state when you click Finish. You are dialing manually if you have selected Dialing through the Operator in the additional menu of the Remote Access to the Network folder.

Error 669 Invalid use of the parameter in the media INI file.
Recommendation: It is possible that one of the Remote Access Network configuration files contains invalid information. If your modem is not supported by Dial-up Networking, switch to a supported modem. For the most up-to-date list of supported modems, see the Microsoft website at www.microsoft.com.

Error 670 The system was unable to read the section name from the media .INI file.
Recommendation: It is possible that one of the Remote Access Network configuration files contains invalid information. If your modem is not supported by Dial-up Networking, switch to a supported modem. For the most up-to-date list of supported modems, see the Microsoft website at www.microsoft.com.

Error 671 The system was unable to read the device type from the media .INI file.
Recommendation: It is possible that one of the Remote Access Network configuration files contains invalid information. If your modem is not supported by Dial-up Networking, switch to a supported modem. For the most up-to-date list of supported modems, see the Microsoft website at www.microsoft.com.

Error 672 The system was unable to read the device name from the media .INI file.
Recommendation: It is possible that one of the Remote Access Network configuration files contains invalid information. If your modem is not supported by Dial-up Networking, switch to a supported modem. For the most up-to-date list of supported modems, see the Microsoft website at www.microsoft.com.

Error 673 The system was unable to read the usage from the media .INI file.
Recommendation: It is possible that one of the Remote Access Network configuration files contains invalid information. If your modem is not supported by Dial-up Networking, switch to a supported modem. For the most up-to-date list of supported modems, see the Microsoft website at www.microsoft.com.

Error 674 The system was unable to read the maximum connection speed from the media INI file.
Recommendation: It is possible that one of the Remote Access Network configuration files contains invalid information. If your modem is not supported by Dial-up Networking, switch to a supported modem. For the most up-to-date list of supported modems, see the Microsoft website at www.microsoft.com.

Error 675 The system was unable to read the maximum carrier connection speed from the media INI file.
Recommendation: It is possible that one of the Remote Access Network configuration files contains invalid information. If your modem is not supported by Dial-up Networking, switch to a supported modem. For the most up-to-date list of supported modems, see the Microsoft website at www.microsoft.com.

Error 676 The telephone line is busy.
Recommendation: Redial the number. You can automate redialing on the Properties tab in the connection setup. If it is a virtual private network (VPN) connection, check the name or IP address of the server you are connecting to and try connecting again. Also, check with your system administrator to check if the remote server is running.

Error 677 A man answered instead of a modem.
Recommendation: The modem or other device does not pick up the handset. Check the number and redial it again. If it is a virtual private network (VPN) connection, check the name or IP address of the server you are connecting to and try connecting again.

Error 678 No response received.
Recommendation: The modem or other device does not pick up the handset. Check the number and redial it again. If it is a virtual private network (VPN) connection, check the name or IP address of the server you are connecting to and try connecting again. Also, make sure the telephone line is plugged into the correct jack on the modem.

Error 679 The system is unable to determine the carrier.
Recommendation: The modem or other device does not pick up the handset. Many modems will give this error if the remote modem does not pick up the phone. Check the number and redial it again. If it is a virtual private network (VPN) connection, check the name or IP address of the server you are connecting to and try connecting again. You can automate redialing on the Properties tab in the connection setup.

Error 680 There is no dial tone.
Recommendation: The telephone line may be incorrectly connected to or disconnected from your modem. The number may need to be prefixed with a prefix, such as 9, to access an outside line, or the number may be too long.
Make sure the phone line is plugged into the correct jack on your modem. Also, make sure you enter special access numbers for connecting to an outside line, such as the prefix 9 followed by a comma.
Check your telephone line for a stutter tone corresponding to your answering machine message. Many modems cannot dial more than 34 digits. After entering a number exceeding this length, these modems split it into two or more lines, of which only the first (unfinished) one is dialed. This is done by USRobotics and Multitech modems. The only known solution to this problem is to use modems from other manufacturers.

Error 681 The modem reports a general error.
Recommendation: It is possible that one of the Remote Access Network configuration files contains invalid information. If your modem is not supported by Dial-up Networking, switch to a supported modem. For the most up-to-date list of supported modems, see the Microsoft website at www.microsoft.com.

Error 691 Access is denied because such a username or password is not valid on this domain.
Recommendation: Your account is not registered on the specified domain, your password has expired, or you entered the information incorrectly. If you did not specify a domain, the remote access server tries to validate your username and password against the domain of which you are a member. Re-type your username, password and domain carefully. If you are unsure of this information, contact your system administrator.

Error 692 A hardware error has occurred on the modem.
Recommendation: Your modem (or other device) is not responding for the following reason:
The modem is turned off, is not functioning properly, or is not securely connected to the computer.
To solve this problem, do the following:
Reset your modem. See your hardware documentation for more information.
If you are using an external modem, make sure you are using the correct serial cable and that it is securely connected. You can try replacing the modem cable. Also, if you are using an adapter to connect to the serial port, make sure the adapter is properly connected to the modem. For example, a 9-25 pin mouse adapter will not work properly with a serial network connection.
Test the serial port or multiport adapter and replace if necessary.
Make sure the modem handshaking parameters are correct. For information on the handshake options available for your modem, refer to your modem's documentation.
If your modem is not supported by Dial-up Networking, switch to a supported modem. For the most up-to-date list of supported modems, see the Microsoft website at www.microsoft.com.
Check if this communication port is being used by another application such as HyperTerminal. If the port is in use, further launching Dial-up Networking may cause this message to appear.
For more information, visit the Personal Support Center on the Microsoft website at www.microsoft.com.

Error 695 State machines are not running.
Recommendation: An internal error has occurred. Restart your computer to make sure any recent configuration changes take effect.

Error 696 State machines are already running.
Recommendation: An internal error has occurred. Restart your computer to make sure any recent configuration changes take effect.

Error 697 The response cycle is incomplete.
Recommendation: An internal error has occurred. Restart your computer to make sure any recent configuration changes take effect.

Error 699 The modem's response caused a buffer overflow.
Recommendation: An internal error has occurred. Restart your computer to make sure any recent configuration changes take effect.

Error 700 The expanded command in the device INF file is too long.
Recommendation: The script file command cannot exceed 265 characters. Break your team up into multiple teams.

Error 701 The set baud rate for the modem is not supported by this COM driver.
Recommendation: Your modem is trying to connect at a speed not supported by the serial port. Reset the initial connection speed to the next lowest standard mark.

Error 703 The connection requires some data from the user, but the application does not allow user interaction.
Recommendation: The server you are trying to connect to requires user interaction. The rasdial command or the application you are using to connect does not support user interaction. If possible, try connecting using an existing connection from the Dial-up Networking folder. If you are using a script to connect, try connecting using a connection configured to use a terminal. The terminal window can enable the desired user interaction.

Error 704 Invalid callback number.
Recommendation: The callback number specified in the program is not valid.

Error 705 Invalid authorization state.
Recommendation: An internal error has occurred. Restart your computer to make sure any recent configuration changes take effect.

Error 707 An X.25 protocol error has occurred.
Recommendation: The X.25 connection reported an error. Check with your X.25 provider to determine the cause of the error.

Error 708 This account has expired.
Recommendation: Ask your system administrator to activate your account.

Error 709 An error occurred while changing the domain password. The password may be too short or the same as the previous one.
Recommendation: Try changing your password again. If you continue to receive this message, contact your system administrator.

Error 710 A sequence of overflow errors occurred while using this modem.
Recommendation: Reduce the initial modem speed (bps) and call back.

Error 711 Failed to start Remote Access Service Manager. More information is in the event log.
Recommendation: The Remote Access Connection Management service may not be running. Configure the service to start automatically. Restart your computer to make sure any recent configuration changes take effect. For more information, visit the Personal Support Center on the Microsoft website at www.microsoft.com. The problem may be caused by a problem with your modem or modem cable. Make sure your modem is supported by your operating system. For the most up-to-date list of supported modems, see the Microsoft website at www.microsoft.com. Try replacing the modem cable.

Error 712 Initializing a two-way port. Wait a few seconds and call back.
Recommendation: This error can occur with a connection configured to receive calls (bi-directional connection). The error occurs when you make an outgoing call at the same time the server initializes the connection to receive incoming calls. Remote Network Access will call again after a few seconds.

Error 713 There are no ISDN lines available.
Recommendation: Make sure that your ISDN line is connected correctly and that the terminating resistors are correctly set (see the documentation for your ISDN card), then reconnect. If you continue to receive this message, contact your ISDN card dealer or ISDN telephone company.

Error 714 There are no ISDN channels available to make the call.
Recommendation: All available ISDN channels are busy. Typically, ISDN at the BRI (Basic Rate Interface) level provides two channels over which you can make voice calls and transfer data. If both channels are already in use, Dial-up Networking will not be able to place the call. Free one channel and then reconnect.

Error 715 Too many errors occurred due to the poor quality of the telephone line.
Recommendation: Too many asynchronous errors occur on the phone line during authentication. Try again. If this problem continues to occur, reduce the baud rate and disable all modem settings.

Error 716 Remote Access IP configuration is unusable.
Recommendation: There is a problem with the TCP / IP configuration of the remote access server. For example, your connection is requesting a TCP / IP address from an unused server.
Contact your system administrator to check your server's TCP / IP settings.

Error 717 There are no available IP addresses in the static IP address pool of the Remote Access service.
Recommendation: Try to use an IP address that does not cause conflicts on the remote network. If possible If possible, use DHCP to avoid addressing conflicts.

Error 718 Timed out waiting for a valid response from the remote computer.
Recommendation: The PPP conversation started, but it ended due to the absence of a response from the remote computer for a certain amount of time. This could be caused by poor line quality or problems on the server.

Error 719 The connection was interrupted by the remote computer.
Recommendation: The PPP dialogue started, but was terminated at the request of the remote computer. The error might be caused by problems on the server.

Error 720 The connection attempt failed due to a PPP control protocol conflict between your computer and the remote computer.
Recommendation: There are no PPP network control protocols configured for your connection, or the appropriate network protocol has not been installed. This error can occur after changing the network protocol during a software update.

Error 721 The remote computer is not responding.
Recommendation: An attempt was made to start a PPP conversation, but the remote computer is not responding. This error occurs if the server does not support PPP (Windows NT 3.51 and earlier remote access servers, or SLIP server). This error can also occur if the server requires login using a terminal window before starting PPP. If using a terminal window to register solves the problem, for subsequent connections, you can automate the registration process using Windows scripting. This error can also indicate a hardware malfunction of your computer or remote server.

Error 722 Invalid data received from the remote computer. The data was ignored.
Recommendation: The received PPP packet is not in the correct format. To solve this problem, your system administrator needs to keep a PPP event log. For more information, visit the Personal Support Center on the Microsoft website at www.microsoft.com.

Error 723 The phone number, including prefix and suffix, is too long.
Recommendation: The maximum length of a telephone number, including prefix and suffix, cannot exceed 128 characters.

Error 726 The IPX protocol cannot be used to make outgoing calls to more than one modem at the same time.
Recommendation: With IPX, only one connection can be used for dialing.

Error 728 The system cannot find the IP adapter.
Recommendation: Problems with TCP / IP configuration. Restart your computer to make sure any recent configuration changes take effect.

Error 729 Until IP is installed, SLIP cannot be used.
Recommendation: Check if the TCP / IP protocol is installed in the Network Properties.

Error 731 The protocol is not configured.
Recommendation: An unconfigured PPP control protocol was requested for specific information. To determine the cause of the problem, ask your system administrator to enable PPP registration using the Netsh.exe utility.

Error 732
Recommendation: PPP parameters could not be negotiated because the local and remote computers did not agree on a common set of parameters. Contact your system administrator for the configuration of network protocols such as TCP / IP, IPX, or NetBEUI. Also, your sysadmin can enable PPP registration using the Netsh.exe utility, which can help determine the cause of the problem.

Error 733 This computer and the remote computer were unable to negotiate PPP control protocols.
Recommendation: The server supports PPP, but does not support the network protocols for your connection. Ask your system administrator to configure the connection to use the network protocols supported by your server. Also, your sysadmin can enable PPP registration using the Netsh.exe utility, which can help determine the cause of the problem.

Error 734 The PPP link control protocol was interrupted.
Recommendation:

Error 735 The requested address was rejected by the server.
Recommendation: Your connection is configured to request a specific IP address. The server is not configured to allow the client to request a specific IP address, or the specific IP address is already in use by another client. If possible, use DHCP to avoid addressing conflicts.

Error 736 The remote computer has terminated the control protocol.
Recommendation: The PPP link control protocol dialog started, but ended at the request of the remote computer. The error might be caused by problems on the server. Contact your system administrator. Also, your sysadmin can enable PPP registration using the Netsh.exe utility, which can help determine the cause of the problem.

Error 737 Loopback detected.
Recommendation: The local and remote computers participating in the PPP dialogue are one and the same computer. This usually means that a device (for example, a modem) on the link is returning characters back. Try resetting these devices. For non-Microsoft servers, this may mean that the remote computer tries to start a TTY terminal before connecting. You can configure the connection to open a terminal window after connecting on the Security tab.

Error 738 The server did not assign an address.
Recommendation: The server cannot assign your computer an IP address from the pool of available addresses.
1. Check the availability of funds in your account.
2. Check the activity of your account (it may be disabled or suspended).
3. Check for a valid rate for your account.
4. Check if network and Internet servers are blocked on your personal statistics page.

If you cannot find a solution to your problem, contact technical support at 539-500.

Error 739 The authentication protocol required by the remote server cannot use the stored password. Call back and enter the password explicitly.
Recommendation: This error occurs only when establishing a PPP connection to a non-Microsoft server. The standard PPP authentication protocols used to communicate with other servers require the password to be available in text-only format, but Windows stores the password only in encrypted form for security reasons.

Error 740 Invalid dialing rule encountered.
Recommendation: TAPI devices configured to work with Dial-up Networking failed to reset or were incorrectly installed. Restart your computer to make sure any recent configuration changes take effect. If this error continues to occur, refer to the event log for reasons of its occurrence.

Error 741 The local computer does not support the required type of data encryption.
Recommendation: Checkbox selected. Require Data Encryption (disable if not present) on the Security tab, but your connection does not have encryption capabilities. Clear this checkbox to use an unencrypted connection, or contact your system administrator. This error can also occur if your password is longer than 14 characters, you selected the Require Data Encryption (disable if not present) checkbox on the Security tab, and you selected Require Password Encryption in Confirmation of My Identity. Use a password shorter than 14 characters, clear the checkbox. Require Data Encryption (disable if not present) and select Allow Unencrypted Password Transmission in Confirm My Identity.

Error 742 The remote computer does not support the required type of data encryption.
Recommendation: The requested encryption level is not supported on the remote computer. One of the computers is probably using 128-bit encryption, while the other is using 40-bit, or 56-bit. Check with your system administrator to determine your encryption level and make sure the server is using the same encryption level. 128-bit encryption is available without extension to North American Windows 2000 users, Windows NT 4.0 with Service Pack 3, and Windows 9x clients using dial-up networking 1.2 and higher. You must separately order 128-bit encrypted versions of each of these products.

Error 743 The remote server requires data encryption.
Recommendation: The remote access server requires encryption, but encryption is not enabled on your connection.

Error 751 The callback number contains invalid characters. The only valid characters are numbers (0 through 9), T, P, W, (,), -, @, and a space character.
Recommendation: Invalid callback number. Only the following characters are allowed in the number: digits from 0 to 9, T, P, W, (,), -, @ and a space. Enter the correct number and call back.

Error 752 A syntax error was encountered while processing this script.
Recommendation: A syntax error was encountered while processing the script.

Error 753 The connection cannot be dropped because it was created by the multi-protocol router.
Recommendation: This connection is used by Routing and Remote Access. Use Routing and Remote Access to disconnect the connection. The connection appears either in the list of routing interfaces or in the list of remote access clients.

Error 754 The system cannot find a multichannel bundle.
Recommendation: An internal error has occurred. Restart your computer to make sure any recent configuration changes take effect.

Error 755 The system cannot perform automatic dialing because this connection has parameters for a specific caller.
Recommendation: Contact your system administrator.

Error 756 This connection has already been made.
Recommendation:

Error 757 Remote Access Services cannot start automatically. More information can be found in the event log.
Recommendation: An internal error has occurred. Restart your computer to make sure any recent configuration changes take effect.

Error 758 Internet Connection Sharing (ICS) is already enabled for this connection.
Recommendation: This error can occur if the application is enabling Internet Connection Sharing while the connection properties are open and you are trying to enable the same property. Close and reopen the connection properties. The checkbox must be selected. Allow Internet Connection Sharing.

Error 760 An error occurred while enabling routing.
Recommendation: An internal error occurred while trying to enable routing. Contact your system administrator.

Error 761 An error occurred while enabling Internet Connection Sharing.
Recommendation: An internal error occurred while enabling Internet Connection Sharing. Contact your system administrator.

Error 763 Unable to enable Internet Connection Sharing. More than one LAN connection will be shared.
Recommendation: Close and reopen the connection properties. The Allow Internet Connection Sharing checkbox must be selected. Select Local Area Connection from the list.

Error 764 Smart card readers are not installed.
Recommendation: Install a smart card reader.

Error 765 Unable to enable Internet Connection Sharing. The local area connection is already configured to use an IP address that is automatically allocated.
Recommendation: Internet Connection Sharing configures a local area network connection for home networks, or small office networks with a static address. There is another network adapter on the system configured with the same address. Change the static address of your network adapter before enabling Internet Connection Sharing.

Error 766 The system could not find the certificates.
Recommendation: Contact your system administrator.

Error 767 Unable to enable Internet Connection Sharing. The LAN connection selected as private is configured to use more than one IP address. Change the LAN connection settings.
Recommendation: Remove the additional static IP address, or reconfigure your LAN connection for DHCP.

Error 768 Data encryption error while trying to connect.
Recommendation: If you don't need encryption, disable encryption and try again.

Error 769 The specified destination is unreachable.
Recommendation: The address you provided is not correct, or your remote access server is unavailable. Please check the address and try again.

Error 770 The remote computer rejected the connection attempt.
Recommendation: Perhaps the remote computer is refusing to connect to you due to the settings of the calling program, or other hardware settings.

Error 771 The connection attempt failed because the network is overloaded.
Recommendation: Please wait and try again later.

Error 772 The hardware on the remote computer is incompatible with the type of call requested.
Recommendation: Contact your system administrator.

Error 773 The attempt to connect failed due to a change in the destination address.
Recommendation: Enter the correct number and try again.

Error 774 The connection attempt failed due to a temporary error. Try to connect again.
Recommendation: Please wait and try again later. This error may be due to a timeout or a problem with the remote computer.

Error 775 The connection was blocked by the remote computer.
Recommendation: The remote computer may be blocking your connection because of the caller's settings, a distribution policy that only allows access for a specific time, or some other setting.

Error 776 The connection failed because the remote computer entered Do Not Disturb mode.
Recommendation: Contact your system administrator.

Error 777 The connection attempt failed because the modem or other communication device on the remote computer is not working.
Recommendation: Contact your system administrator.

Error 778 Unable to verify the identity of the server.
Recommendation: During the authentication process, the server identified your computer, and your computer identified the server. This error occurred because your computer did not recognize the server.

Error 779 In order to make a call using this connection, you need to use a smart card.
Recommendation: Install the smart card.

Error 780 The trial function is not valid for this connection.
Recommendation: An internal error has occurred. Contact your system administrator. You may need to configure a connection for EAP.

Error 781 The encoding attempt failed because no valid certificates were found.
Recommendation: The VPN client tries to use L2TP / IPSec protocol to connect. Go to connection settings VPN-Properties -> Network-> VPN Type and select PPTP VPN.

Error 783 Unable to enable Internet Connection Sharing. The LAN connection selected as private either does not exist or is disconnected. Make sure the network adapter is connected.
Recommendation: Before allowing Internet Connection Sharing, make sure that the LAN adapter and the corresponding cable are securely connected.

Error 784 This connection cannot be used at boot time because it uses a username other than the smart card user. To use it at boot time, change the name used to the name of the owner of the smart card.
Recommendation: Configure the connection to use the same name as the smart card. On the Security tab, select the Advanced (special options) radio button and click the Options button. Select the Smart card or other certificate (encryption enabled) radio button, click the Properties button, and then clear the Use a different username for connection check box.

Error 785 This connection cannot be used at boot time because it is configured to use a smart card. Modify the properties of this connection to use smart card data.
Recommendation: Configure the connection to use a smart card. See Enabling Smart Card or Other Certificate Authentication.

Error 788 The L2TP connection attempt failed because the security layer could not negotiate parameters with the remote computer.
Recommendation: Contact your system administrator. The current configuration of L2TP parameters is incompatible with Microsoft's implementation of L2TP.

Error 789 The L2TP connection attempt failed due to an error in the security layer during negotiations with the remote computer.
Recommendation: Contact your system administrator.

Error 791 The L2TP connection attempt failed because no security policy was found.
Recommendation:

Error 792 The L2TP connection attempt failed because the security negotiation timed out.
Recommendation: Check if your internet connection is working. If the connection works, contact your system administrator.
Your connection is likely failing for one or more of the following reasons.
The remote server may be down.
The server you are accessing does not have the correct credentials.
Your connection is not configured to use the correct credentials.
Your connection is configured to use a security method other than the security method of the remote computer. Try changing your VPN connection type. To change the VPN connection type, right-click the connection and select Properties, and then view the information on the Networking tab.

Error 793 The L2TP connection attempt failed due to a security negotiation error.
Recommendation: Contact your system administrator. Your connection is likely to fail for one or more of the following reasons.
The remote server may be down.
The server you are accessing does not have the correct credentials.
Your connection is not configured to use the correct credentials
The computer is using an invalid shared secret. Try using a different pre-shared key.
For more information on remote access security, see Security Actions During Connection.

Error 794 The Framed Protocol RADIUS attribute set for this user does not have a PPP value.
Recommendation:

Error 795 The set RADIUS Tunnel Type attribute for this user has an incorrect value.
Recommendation: On the remote network, the attribute for the remote connection must be configured. Contact the administrator of the remote network.

Error 796 The set RADIUS Service Type attribute for this user is neither Framed nor Callback Framed.
Recommendation: On the remote network, the attribute for the remote connection must be configured. Contact the administrator of the remote network.

Error 797 The connection to the remote computer could not be established because the modem is not found or is busy.
Recommendation: This connection requires a modem. Follow these steps:
Close all programs and try to connect again. The modem or communication port to which it is connected may be in use by another program.
Make sure you have a modem installed on your computer. For more information, see Installing the Modem.
Check if the modem is functioning properly. For more information, see Troubleshooting Modems.

Error 799 Failed to enable Internet Connection Sharing (ICS) due to IP conflicts on the network. ICS requires the host to be configured to use the 192.168.0.1 address. Make sure no other client on the network is using 192.168.0.1.
Recommendation: Check the IP addresses of all computers connected to the local network, change them if necessary. See Configuring TCP / IP Settings.

Error 800 Failed to establish a VPN connection. The VPN server is not available, or the security settings for this connection are incorrect.
Recommendation: There is no access to the VPN server. It is recommended to check whether there is a physical connection (whether the lights of the network card on the back of your computer are on), whether the network cable is plugged into the socket on the network card and into the outlet (if any). Then check if LAN connection is enabled. To do this, follow "Start" - "Control Panel" - "Network Connections". In the window that appears, find "Local Area Connection" and enable it if it was disabled. Try pinging (command ping) your local gateway. To do this, press the "Start" button, then "Run". In the line that appears, type in the English layout "cmd", click "OK". In the black window that appears in the English layout, type ping XX.XX.XX.XX (XX.XX.XX.XX must be replaced with the address of your gateway, the gateway address can also be viewed in the properties of the TCP / IP network connection) press Enter on the keyboard ... If in the black window, five, times or more, the words "The request waiting interval has been exceeded" appear, then call the technical support of your Internet provider.

Here are the most common errors that users encounter when connecting to the Internet.
Please read below for information on the error you are experiencing. If this information did not help you, you can ask for help using the feedback form.

Error 691. Access denied because the given username or password is not valid on this domain.
Cause:
1. The username (account) has expired.
2. Incorrect connection data (login and password) have been entered.
3. This login is used on another computer or network device.
Solution:
1. Pay for the Internet and get a new username and password.
2. Re-enter your username and password. ALWAYS erase Username in the connection completely, because there are times when in the internet connection in the line Username besides login symbols there is space, which is not visible to the user, but for a computer it is the same symbol as a letter and a number. Usually a "tricky" space is placed before the login or at the end.
3. It is necessary to make sure that this login is not connected anywhere else at neighbors and acquaintances, because there are cases when roommates take the login and password left by you without asking. One login can be connected only from one network device (computer, router, tablet, etc.).

Error 629. The connection was closed by the remote computer or The port has been disabled on the remote computer.
see bug 691.

Error 800. Failed to create VPN connection. The VPN server is not available, or the security settings for this connection are not configured correctly.
Cause:
1. There is no connection with the Internet server.
2. The connection is blocked by a firewall installed on the computer (it was noticed with many well-known, but with older versions
Solution:
1. If you have a laptop, check that your laptop is was not connected to free Wi-Fi (network MAInet_public).
2. Check if your computer is connected to the local network, for this check the network cable, and then check if you can go to the site site... If the site does not enter, contact the system administrator.
3. Reconfigure the firewall to allow connection per port 1701 TCP(in the case of using L2TP), if you do not know how to do this, disable it ..

Error 809. The network connection between the computer and the VPN server could not be established because the remote server is not responding.
see error 800.

Error 742. The remote computer does not support the required type of data encryption.
Cause:
1. Data encryption is disabled on the Internet server, but it is required on your computer with an Internet connection.
Solution:

Start an internet connection but don't connect i.e. there should be a window where you enter your username-password.
- for Windows 7: press the button Properties Security, on it in the graph Data encryption choose Optional (connect even without encryption)... See the picture:
- for Windows Vista: press the button Properties, in the new window select the tab Security... See the picture:
- for Windows XP: press the button Properties, in the new window select the tab Security, uncheck the box opposite Requires data encryption otherwise disconnect... See the picture:

Error 741. The local computer does not support the required type of data encryption.
see bug 742.

Error 734. The PPP link control protocol was interrupted.
see bug 742.

Error 868. The remote connection could not be established because the name of the remote access server could not be resolved.
Cause:
1. The server address is incorrectly specified in the Internet settings.
2. It is necessary to check the local network settings.
Solution:
1. Start an internet connection, but do not connect, i.e. there should be a window where you enter your login-password data.

Click the button Properties, in the window that appears, check the server address:
- there should be no spaces in the server address either in front, at the end, or between words;
- there should be no commas in the server address, only periods, letters (uppercase or not - it doesn't matter) and numbers;
- for unlimited internet it should be written l2tp.mai.ru(first letter L, not a number; further goes mai.ru, but not mail.ru ).

2. Contact technical support.

Error 609. The specified device type does not exist.
Cause:
1. Damage to system files or miniport L2TP or PPTP port drivers.
Solution:
1. Download this archive (file): NETCFG.zip
2. Unzip it to the C: \ Windows \ System32 \ folder. If windows writes that the file already exists, then you do not need to replace it.
3. Download this file: Error_609.zip
4. You downloaded the archive, which contains 1 file. Unpack (copy) the Error_609.bat file that is inside the archive.
5. For Windows XP: run the Error_609.bat file.
For Windows Vista, 7, 8: right-click on the Error_609.bat file and select "Run as administrator".

Error 619. Unable to connect to the remote computer, so the connection port is closed.
Cause:
1. Connection is blocked by a firewall installed on the computer (it was noticed with many well-known, but with older versions programs like Kaspersky Internet Security, Panda Internet Security, McAfee Total Space Security, and others), especially free antiviruses like Avira, Zone Alarm, F-Secure, etc.
2. Problems with the Internet server: technical problems, hardware failure, etc.
Solution:
1. Reconfigure the firewall to allow connection per port 1701 TCP(in the case of using L2TP) or per port 1723 TCP and protocol GRE(in the case of using PPTP), if you do not know how to do this, disable it.
2. Look at the announcements on the main page of the site, it is possible that work is already underway to troubleshoot. Expect.

Error 769. The specified destination is unreachable.
see bug 619.

Error 692. A hardware error has occurred in the modem or other communication device.
Cause:
1. System glitch (there is no other name for it).
Solution:
Reboot your computer.

Error 735. The requested address was rejected by the server.
Cause:
1. Incorrectly configured Internet connection (V Connection properties -> Net -> Internet Protocol Version 4 (TCP / IPv4)"Obtain an IP address automatically" must be selected).
Solution:
Create an Internet connection again according to the instructions on the site.

Error 789. The L2TP connection attempt failed due to an error in the security layer during negotiations with the remote computer.
Cause:
1. The computer was unable to negotiate security with the Internet server.
Solution:
1. Download this file and unpack it: l2tp-disable-ipsec.zip
2. There is one file in the archive l2tp-disable-ipse.reg- run it. If Windows asks something, click YES and OK.
3. Be sure to restart your computer.

Error 711. The Remote Access Connection Manager service could not be loaded.
Cause:
1. Necessary services (Plug and Play, Windows Event Log, SSTP Service, Telephony, Remote Access Automatic Connection Manager, Remote Access Connection Manager) are not running or disabled.
Solution:
1. Download this archive and unpack it to your desktop: Error_711.zip
2. For Windows XP: run the resulting file Error_711.bat and wait for it to finish executing.
For Windows Vista, 7, 8: click on the resulting file Error_711.bat right mouse button and select Run as Administrator... Wait for it to finish executing.

Device not found.
see bug 711.