Local Connection Overview

Hide the local connection icon

Method 1: The local connection icon and the system's netmask X. DLL, netshell. DLL, netman. DLL is related to the three dynamic link files. Once these three dynamic link files are unregistered, the local connection icon will be automatically hidden. When registering the above three dynamic link files, you can first open the system runtime box and enter the string command "regsvr32 netmask X. run the DLL/u command to restore regsvr32 netmask X. dll/s

Method 2: 1. Open the system running dialog box, run the "gpedit. msc" command, and expand"
User Configuration "," management template "," Taskbar and Start Menu ", on the right of the corresponding" Taskbar and Start Menu"
In the window, double-click the "delete network and dial-up connections from the Start Menu" option. In the displayed interface, select "enable"

Click OK.

Method 3: Run msconfig to disable network connections and workstation in the service. (generally, this operation is optional)

Restart.

After the restart, the system prompts that one service is missing.

 

3. Protect IP addresses in the LAN

IP addresses in the LAN are occupied or tampered with. You can provide several practical methods.

Disable Network Connection Service

To restrict users from modifying TCP/IP parameters at will, the simplest way is to prevent users from opening the TCP/IP Parameter Setting window. Open start, run, and enter services. run the MSC command, select the "Network Connections" Service, right-click, select the stop button from properties, select "Start type" as "disabled", and click OK. In this way, if you enter "network connection" from "start", you cannot find the "local connection" icon. This will also cause trouble to modify network parameters. You can stop the "Plug and Play" service without affecting normal network access.

Restrict Network Parameter Modification

You can modify the network key of the Registry. Enter the "run" command and enter the "Regedit" command to open the registry editing. Go to the HKEY_USERS \ Default \ Software \ Microsoft \ Windows \ CurrentVersion \ Policies \ Network Branch. in the area on the right, select "edit", "new", and "DWORD Value", name the New DWORD Value "nonetsetup", enter the value as "1", and restart the computer, the system will prompt you that you cannot enter the network attribute settings window.

Hide the local connection icon

The local connection icon and the system's netmask X. DLL, netshell. DLL, netman. DLL is related to the three dynamic link files. Once these three dynamic link files are unregistered, the local connection icon will be automatically hidden. When registering the above three dynamic link files, you can first open the system runtime box and enter the string command "regsvr32 netmask X. dll/u command, click the "OK" button, you can put netmask X. DLL file unregistered

 

Delete hidden local connections from the system

Because the NIC of the machine fails, the system finds a new hardware after the NIC is changed. The report shows that a new Nic is found and the system automatically installs the driver. After the driver is installed, it is found that there is no "Local Connection" icon in the network connection, and there is only one "local connection 2" icon. When setting the IP address of "local connection 2", the system prompts that the IP address has been occupied by the hidden Nic.

Because Windows XP does not need to be started to install new hardware devices, when there is a hardware update, the original hardware information of the system still exists. We must manually clear the hardware information by modifying the registry. To delete the hidden NICs in the system, Run regedit to open the Registry Editor and find the hkey_local_mchine \ System \ currentcontrolsetcontrol \ Network \ {4d36e972-e325-11ce-bfc1-08002be10318} key value.

Information about local connections is saved under the sub-key. There is one or more sub-keys here. The first sub-key corresponds to "Local Connection", and the second sub-key corresponds to "local connection 2, we can also expand the subkey and then select the "connection" subkey below. In the right window, we will see the connection corresponding to it, delete the entire sub-key corresponding to the old connection.

After you modify the registry, restart the computer to correctly set the NIC.

 

 

Restore "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 the "properties" button (

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 notProgramUninstall, but after the NIC location changes, windows still prompts that we must reinstall the NIC driver at the new location, especially for those enable the out-of-the-box function Nic, Windows often does not prompt us to automatically reinstall the NIC Driver. As a result, the driver 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" (). Click the Enter key, and the windows system will automatically display all the virtual devices hidden in the computer.

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 (),

If the device is unavailable, change the NIC installation location and reinstall the NIC driver to see if the fault can be eliminated; if you cannot restore the network adapter to normal after you reinstall the network adapter, the network adapter itself is damaged. In this case, you must replace the new network adapter device.

 

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 the Remote Procedure Call Service "Remote Procedure" related to the "Network Connections" service.CALl "indicates whether the service works normally, because 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.

 

 

Find the "Network Connection" that disappears" I. fault symptoms:
In Win2000/XP/2003, click Start> Control Panel> network connection, or click Network Neighbor> properties. The "Local Connection" icon is displayed, generally, a computer may have several local connections when there are several NICs. Of course, some readers may have used programs similar to virtual NICs, so each time a virtual Nic program is added, an additional local connection will be provided. Through the local connection, we can set the network parameters of the corresponding Nic. Of course, in actual work, "Local Connection" May cause one or more failures. Reference content 1: the "local connection" icon is missing.
2. The "dial-up connection" icon is missing.
3. The "New Connection" Wizard icon is missing.
4. Only the "New Connection" icon is displayed, or one or more dial-up connections are displayed. Other connection options are unavailable in gray.
5. Click the "advanced" menu of the network connection and click "Advanced Settings". Only the "Remote Access Connection" item is displayed in "connection.
6. Select a network connection and click "properties". Then, the "Network and dial-up connections" Resource Manager stops responding or closes immediately.

Despite these problems, the network can still run normally, and the ipconfig command also displays all connections and all adapter information. However, it is inconvenient to create new connections and network settings in the future.

2. Solution steps:
How can we solve the problem as a result?
Step 1: Verify that the network DLL file has been correctly registered. In Windows2000/XP/2003, the network-related dynamic link library file mainly includes netshell. DLL, netmask X. DLL, netman. DLL. In actual use, the DLL file registration may be invalid due to some exceptions. You only need to enter "regsvr32 netshell. DLL "(without quotation marks) to complete the registration of the DLL file. Similarly, regsvr32 netmask X. DLL and regsvr32 netman. DLL completes registration of the other two files. After registration, restart the computer.
Step 2: Verify the network adapter settings and expand the network adapter (network adapter) through "My Computer> Properties> hardware> Device Manager ), verify that the correct Nic is listed. Are you sure the NIC model is correct and there is no device in front of it? And !. Double-click the network adapter to verify whether the message "this device is working properly" is displayed in "device status" in the "General" tab.
Step 3: Verify that the necessary services have been started. Go to "Control Panel> Administrative Tools> Services" to check whether the following services have been started. It includes six services: Remote Procedure Call (RPC), network connections, Plug and Play, COM + Event System, Remote Access Connection Manager, and telephony. Note that when the Remote Access Connection Manager Service is not started, a prompt will appear when establishing a network connection.

Step 4: Verify network service settings, go to Control Panel> add or delete Programs> Add/delete Windows components, and select Network Service> details ", verify that the simple TCP/IP service is enabled.
Step 5: Make sure that all windows protected files in the system folder are not affected. You can start the Windows File Checker by typing SFC/purgecache and SFC/scannow at the command prompt to fix the protected files.
Step 6: fix the key values in the Registry and start the Registry Editor (START-> Run-> enter Regedit ), locate and click the Registry subitem hkey_classes_root \ interface \ {secret} to verify whether the subitem nummethods and proxystubclsid32 exist and whether their values are correct (nummethods is 4 and proxystubclsid32 is {secret }. If the registry subkeys do not exist, create them.

Tips for referencing content:
You must back up the registry before modifying the Registry. Otherwise, you may not be able to enter the operating system due to the poor modification.
Step 7: make sure that there are no nonexistent, illusory, or hidden network adapters in the computer. Delete all network adapters if they exist. Delete all third-party network adapter management software.
Step 8: Delete the network adapter in the Device Manager and manually or enable the operating system to automatically install the NIC Driver. This step detects and corrects corrupted registry entries bound to the network adapter. If none of the other steps can solve the problem, perform this step.

Iii. Summary:
You can use the eight steps described above to solve the problem of local connection or dial-up connection in practice. As long as you perform operations step by step, you can basically solve Network Connection-related faults.Five methods to block network settings (prevent others from modifying Network Properties)

Five methods to block network settings (prevent others from modifying Network Properties)
Managing and maintaining the LAN is a very annoying thing, because the network administrator will always face this problem, that is, after the LAN parameters set by others are modified, as a result, the network cannot be normally connected. After a fault occurs, you must carefully resolve the faulty computer until the fault is resolved again. Obviously, this method allows you to set permissions for the network, this not only increases the maintenance workload of the staff, but also greatly reduces the maintenance efficiency. In order to improve the maintenance efficiency of the LAN and avoid unauthorized network parameter settings by others, we should take measures to prohibit others from setting network parameters. Below are some tips for blocking network settings:

1. If the other party is a system of 2000 or above, a group policy is available. (But XP family Edition does not have a group policy)

Enter "gpedit. MSC ", press enter to enter the Group Policy window, find [network] under [user configuration], find" Access to lan prohibited properties "and enable; find "enable 2000 network connection for the Administrator" and enable it! OK. Check again. The local network connection property has changed to unavailable!
2. Hiding network neighbors
As you know, right-click the "Network Neighbor" icon and select "properties" from the shortcut menu to open the "Network parameter settings" dialog box and set the network parameters. To this end, we can hide the "Network Neighbor" icon so that others cannot open the "Network Neighbor attribute" dialog box to disable network parameter settings:

1. Open the Start menu, select the Run Command, and enter the Regedit command in the displayed run dialog box. Then, the system opens a Registry Editor operation window;

2. In this window, you can use the mouse to access the hkey_curren \ Software \ Microsoft \ Windows \ CurrentVersion \ Policies \ Explorer;

3. Then, in the Operation window on the right of the corresponding Explorer key value, you can left-click the blank area of the window, from the shortcut menu that appears, access the "new"/"DWORD string value" command in sequence;

4. In the DWORD String Value Setting box that is opened, you must name the New DWORD string value nonethood and set this value to 1 (hexadecimal );

5. After all the parameters are set, restart the computer to make the settings take effect.

3. Hide the Network icon
To open the network parameter Settings dialog box, you can use the "network" icon in the control panel to access the network parameter Settings dialog box, in addition to using the attribute commands of the network neighbor, to this end, we must disable access to the "network" icon by other users:

1. Find the running command in the Start menu of the Windows system, and enter "control. ini" in the pop-up dialog box ";
2. the system starts the Notepad program to open the system file control. INI, in the [Don't load] Setting section of this file, we enter "netcpl. cpl = No;
3. After the input is complete, save the file and restart the computer to hide the "network" icon in the control panel.

4. disable network neighbor attributes
If you do not want to hide the network neighbor icon on the desktop, you can also prevent users from using the "Network Neighbor" icon to open the network attribute dialog box. This method is to make the "Network Neighbor" invalid, the procedure is as follows:

1. As you know, the file corresponding to the "Network Neighbor" icon is netcpl under C: \ WINDOWS \ SYSTEM. cpl. Therefore, accessing "Network Neighbor" is actually accessing the file. to invalidate "Network Neighbor", you only need to remove netcpl. cpl or netcpl. change the name of CPL;
2. You only need to set netcpl. cpl moves other folders, or. CPL is stored as another file name. When we access "Network Neighbor", the system cannot find netcpl in C: \ WINDOWS \ SYSTEM. the CPL file cannot open the "Network Neighbor" attribute dialog box.

5. Cancel Network Access Permissions
By carefully analyzing the methods mentioned above, it is not difficult to find that these methods are almost achieved through hidden methods, however, if you find a file corresponding to the "Network Neighbor" or "network" icon, you can also open the "Network attribute" dialog box. to disable the file in the true sense, you should modify the registry, to cancel the user's right to access network properties:

1. Open the Start menu and click Run Command. In the displayed run dialog box, enter regedit, the registry editing command, to open the registry editing window;
2. Click hkey_curren \ Software \ Microsoft \ Windows \ CurrentVersion \ Policies \ Network with the left mouse button;
3. In the right window of the corresponding network key value, check whether there is a DWORD value such as "nonetsetup". If not, create a new one and set the DWORD Value to 1;
4. Click OK to exit the registry editing dialog box and restart the computer. When you access the "Network Neighbor" or "network" icon again, the system will warn you that you are not authorized to access the network, in this way, the user naturally has no chance to modify the network settings.