Each has its own tricks to restore the "local connection" to normal

We need to start with "Local Connection" to configure the network parameters, whether on the Internet or on the local area network. However, during the actual Internet access process, we sometimes find that "Local Connection" May cause various inexplicable faults. These faults often make it impossible for us to set network parameters in a targeted manner, this affects our Internet access efficiency. To effectively improve internet access efficiency, we must master some troubleshooting methods related to "Local Connection, this article lists several failures that are prone to "local connections" and provides different countermeasures for each fault phenomenon. I believe this will bring you some benefits!

Solve the "local connection" Fault

Some ADSL users use the PPPoE dialing method built in Windows System for broadband dial-up Internet access in Windows XP SP2 operating system. However, when using this method for Internet access, these users may find the display status of the "local connection" icon in the network connection List window, which is often inexplicably changed to "restricted or unconnected ", however, in this status, the Internet operation is normal. So how does this strange state show that a fault occurs? How can we eliminate such a fault?

If the display status of "Local Connection" changes to "restricted or connectionless" for no reason, this is usually caused by not specifying a fixed IP address for the NIC. Under normal circumstances, when we find that the "local connection" status is abnormal, we may first try to set a static IP address for the network connection, this method often solves many inexplicable network faults for us. Once we find that the local network connection does not use a fixed IP address, you can click the "Start"/"set"/"network connection" command in sequence, on the network connection list page that appears, right-click the "local connection" icon and run the "properties" command from the right-click menu to open the attribute setting window for the local connection; on the "General" tab page of the window, select the "Internet Protocol" project and click "properties" (1 );

Figure 1

Then, select the "use the following IP Address" option and set the IP address of the Local Computer to "192.168.0.2 ", then, set the IP address of the local gateway to "192.168.0.1" (the factory IP address of most ADSL devices is 192.168.0.1 by default), and click "OK, restart the computer system and believe that the state of "Local Connection" is limited and most of the faults can be solved.

Solves "Local Connection" extra faults

In general, if a network card is installed and configured for each computer, a corresponding "Local Connection" icon should appear in the network connection List window. If multiple network cards are installed on the computer at the same time, then we should be able to see multiple "Local Connection" icons, and each "Local Connection" name should be followed by numbers like "2" and "3, corresponds to the number of NICs. In fact, sometimes we only install one network card on the computer, but there may still be two "local connections" icons in the network connection List window. Why is this fault, how can we solve the fault?

If there is only one network card in the computer, but two "local connections" icons appear in the network connection List window, this indicates that the NIC driver has been installed twice at least on the local computer. This often occurs after we change the NIC slot location. In general, when the network response is not as sensitive as normal, we always like to open the computer chassis and try to adjust the NIC installation location from the original slot to other slots, in order to improve the contact reliability between the network card and the slot. When adjusting the installation location of the network card, we did not uninstall the original network card driver even before changing the network card location, however, after the NIC location changes, the Windows system still prompts that we must reinstall the NIC driver at the new location, especially for those enable the plug-and-play function, in Windows, we often reinstall the NIC driver without prompting us. As a result, the drivers of the same Nic device may be installed twice by the system. The original driver of the NIC is not uninstalled in time, so the driver of the NIC is still in the Windows system after the location is changed, after the location is changed, the driver of the NIC is installed again, considering that a "Local Connection" has appeared on the local computer ", therefore, the "local connection" icon will automatically add numbers such as "2" and "3" to avoid duplicate names.

Obviously, the repeated installation of this Nic often causes us trouble. For example, if we have already set an IP address for the NIC device, when you try to set the same IP address for the NIC again after the NIC installation location changes, the Windows system will automatically prompt that the current IP address conflicts with other Nic addresses, we need to set another IP address for the NIC again, so that we can no longer use the previous IP address. However, how can we eliminate the IP address conflict prompt when we have only one original IP address available? In fact, it is very simple. we can delete the previously installed virtual Nic device by following the steps below:

Click Start or run to open the system running dialog box, enter the string command cmd, and click OK, switch the system running status to MS-DOS command line mode;

In the doscommand line, enter the string command "set devmgr_show_nonpresent_devices = 1" (2) and click the Enter key, in Windows, all virtual devices hidden in the computer are automatically displayed;

Figure 2

Then, at the DOS prompt, enter the string command "start devmgmt. msc, click the Enter key to go to the system's device list page, and then click View/Show Hidden devices in the menu bar, the figure of the virtual Nic device can be found on the list page;

Double-click the virtual device icon to go to the property settings page of the device, click the driver tab, and then click the Uninstall button on the corresponding tab page, you can delete the previously installed virtual network card device from the computer system.

Of course, if you are familiar with the system registry, you can also open the registry editing window of the system, and then click the "edit"/"Search" command in the menu bar, enter the keyword "Local Connection" in the Search dialog box that appears to search for all the "local connection" values. Then, save the required "Local Connection" item values, delete all other item values, close the registry editing window, and restart the computer system, in this way, the original Nic device can be completely detached.

When we unmount the virtual Nic device and open the network connection List window again, we will find that there is only one "Local Connection" icon in the local system, in this case, we can re-allocate the original IP address to the NIC device after the change.

Solve the "local connection" loss fault

Sometimes we want to reconfigure the network parameters, but after entering the network connection List window, we can find that the "local connection" icon is missing! The "Local Connection" icon cannot be found. How can we set network parameters ?! So how is "Local Connection" Lost? How can we make it "lost?

In fact, there are many factors that cause "Local Connection" loss and failure. For example, if the NIC is not successfully installed, system services related to "Local Connection" are accidentally stopped, the network parameters are not correctly set, or the system is improperly set. Different Causes of local connection loss must be addressed in different ways:

First, open the Device Manager interface of the system and check whether there is a NIC device. If no Nic device is found, it indicates that the NIC has not been installed. You must reinstall the NIC device correctly; if the NIC can be displayed in the Device Manager, right-click the NIC device and run the "properties" command from the right-click menu, in the subsequent window, we can see the current working status of the NIC device (3). If the device is found to be unavailable, change the NIC installation location, then re-install the driver of the NIC to see if the fault can be eliminated. If the NIC cannot be restored to normal after the NIC is reinstalled, the NIC itself is damaged, in this case, you must replace the New Nic device.

Figure 3

Next, go to the System Service list interface and check the system service startup status related to "Local Connection". For example, check whether the "Network Connections" service is enabled, if the service is disabled, check whether the Remote Procedure Call Service is working properly, once the service is accidentally disabled, the "Network Connections" service may also be disabled. Of course, if the "Plug and Play" service is not working properly, it will also affect the normal display of the "local connection" icon. Therefore, we must ensure that the service can run normally.

When connected, we can open the system runtime dialog box and execute the mongodcomcnfg.exe string command in it to enter the Distributed COM configuration interface of the system, and click the "Default attribute" tab, check whether "enable Distributed COM on this computer" is selected on the corresponding tab page. If the project is not selected at this time, most of the "local connection" loss failures are caused by this factor. At this time, we only need to re-select "enable Distributed COM on this computer, at the same time, adjust the simulated level permission to "ID" and click "OK". In this case, the "local connection" icon may appear after the system restarts.

If the above steps do not allow the "local connection" icon to review the day, it is necessary to check whether the "Network Neighbor" function is hidden, in this case, you must open the system running box and execute the "poledit" string command to open the System Policy Editor interface; click "file"/"open registry" in the menu bar, and double-click the "local user" icon on the page, click the "Shell Interface"/"restriction" project one by one, deselect "Hide network neighbors" under the "restriction" project, and save the preceding settings, and restart the computer system to restore the display function of the network neighbors, which can also solve the "local connection" loss fault.