Quite often, many users of Windows-based computer systems encounter an unpleasant problem when, when they try to connect to the Internet, instead of the expected connection, a failure occurs with code 711 (error). How to fix it in several simple ways, and now it will be shown.
The reasons for the failure
If you look, there can be a lot of reasons for the appearance of such failures. However, among all situations, several typical cases can be distinguished, which are mainly associated with a malfunction of a number of services responsible for making a dial-up connection, as well as components related to PPPoE telephony (this is especially common when using a connection via VPN).
Therefore, the failure occurs because the following services may be disabled:
- Plug & Play support service (self-tuning devices);
- dispatchers of standard and automatic connection of remote access;
- telephony service;
- SSTP service (Windows 7 and later only).
In parallel, consider a few more options for the failure of 711 (error). How to fix the situation will be given for each specific case. In addition, a not entirely standard recommendation will be given, which can be used, so to speak, in case of emergency, and then only at your own peril and risk.
Error 711, Windows 7: how to fix in the services section?
So, for starters, we need to check the operation of the above components. You can do this from the administration section, which is located in the standard “Control Panel”, however, it will be faster to use the “Run” menu, in which the command services.msc should be written.
Now we find each of the above services in the list on the right and right-click on the submenu, where we select the property section. Here you need to pay attention to the type of launch. To support Plug & Play devices, you need to set automatic start, and for all others - start manually. At the end of the parameter change, we save everything and reboot the system.
Connection error 711: how to fix using extended permissions?
Unfortunately, business may not be limited to only non-working components of services. Another reason may be that the user does not have sufficient access rights to the system. In this case, failure 711 appears again (error). How to fix it if the previous solution does not work? Yes, very simple.
We use the standard "Explorer", on the system disk (most often this is the "C" section) we find the Windows folder, right-click on the context menu and select the properties section from there, and then go to the security tab.
Here we are interested in the line "System". A little lower we press the button for changing permissions, and in a new window we look at user groups. For the groups “CREATOR-OWNER”, “system” and “TrustedInstaller” we use the button for changing parameters, after which we indicate full access (in the window below we put “birds” opposite all the available items). Save the changes and reboot again.
Rename the LogFiles folder
Quite often you can meet another situation related to report files. Here, 711 failure may also occur (error). How to fix the problem in this case? Yes, just rename the folder itself, where this data is stored.
As a rule, the directory itself can be found in the System32 system folder of the system root directory (Windows). But first you should boot either in safe mode or use some kind of LiveCD (in normal mode, the system will not allow renaming the folder).
We boot, find the necessary directory and give it a name of our choice (Logfiles 1, Logfiles_1, yes anything). The main thing is to leave the original name in the title with the addition of something else). Then, as usual, a reboot follows, that's all.
Command line at your own risk
Finally, let's see how to fix error 711 when connecting to the Internet using a special command. Immediately, we note the fact that experts recommend using it exclusively in situations where nothing else helps.
We call the command line (cmd in the Run menu (Wind + R)), and then we write the sequence shown in the figure in it and press the enter key. This command allows you to restore the standard rights and permissions of the security system for system folders. Next, we reboot the computer terminal in normal mode. In theory, after applying such a cardinal method, there should be no problems.
Conclusion
As can be understood from the foregoing, there are no special reasons to worry, in principle, since the error itself is not critical for the system. Yes, and the most typical failures are considered here. In theory, after all, the system services presented in the first section should not be disabled by themselves, which means that the error was caused by something else. Who knows, maybe this is the impact of viruses or the usual intervention in the operation of a user's system with administrator rights, which does not have the necessary knowledge. But in general, as you can see, the problem is solved quite simply.