What do I do if my network neighbor can't find the local connection option?

Symptom symptoms: In the WinXP, click Start, Control Panel, network Connections, or "My net place, properties", we will see the "Local Connection" icon, in general the computer has several network cards will appear several local connections. Of course, some readers may have used a similar virtual network card program, then each add a virtual network card program will be more than a local connection. With local connection we can set the network parameters of the corresponding NIC. Of course, there is one or more of the following failures in the actual work "Local Area Connection".

Failure performance:

1, the "Local Area 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, and the other connection options are grayed out.

5, click the Advanced menu for the network connection, and then click Advanced Settings to display only the remote access connections item in connections. 6, after you select a network connection and click Properties, the Network and Dial-up Connections resource manager stops responding or shuts down immediately.

Despite these problems, the network can function properly, and the ipconfig command also displays all connections and all adapter information. However, it can be very inconvenient to create new connections and network settings later.

Solutions

1, verify that the network DLL file is correctly registered, in WindowsXP, the network-related dynamic link library files are mainly Netshell.dll, Netcfgx.dll,netman.dll. In practice, it is possible that the registration of DLL files is invalidated due to some accidents. So all we need to do is re-register these DLL files with the regsvr32 command: Click Start-To-run, enter regsvr32 netshell.dllregsvr32 netcfgx.dllregsvr32 Netman.dll completes the registration of the DLL file. Restart the computer after registering. As shown in figure:

2. Verify the network adapter settings by expanding the network adapter (that is, the NIC) and verifying that the correct network card is listed through the Device Manager, hardware, My Computer, properties. Verify that the NIC model is correct and the device is not in front of it. Double-click the network adapter to verify that the "This device is currently working" message appears in the device status in the General tab.

3, verify that the necessary services have been started, through the "Control Panel, management tools and services" to see whether the following services have been started: Remote Procedure call (RPC) network Connectionsplug and playcom+ Event Systemremote Access Connection Manager telephony a total of six services. It is important to note that when the remote Access Connection Manager service is not started, a prompt will appear when establishing a network connection.

4. Verify the Network Service settings, add/Remove Windows components, add or Remove Programs from Control Panel, select Network services, details, and verify that simple TCP/IP services is turned on.

5. Make sure that all Windows protected files in the system folder are not affected, and start the Windows File Checker to fix the protected files by typing Sfc/purgecache and sfc/scannow at the command prompt.

6, repair the key values in the registry, start Registry Editor (Start-and-run, input regedit), locate and click the registry subkey hkey_classes_rootinterface{ 0000010C-0000-0000-C000-000000000046} verifies that its subkeys nummethods and PROXYSTUBCLSID32 exist, and that their values are correct (Nummethods is 4, PROXYSTUBCLSID32 is {00000320-0000-0000-c000-000000000046}. If there are no registry subkeys, create them.

Tip: Be sure to back up the registry before you modify it, otherwise it will cause changes that don't even enter the operating system.

7. Make sure that there is no non-existent, unreal or hidden network adapter in the computer, if it exists please delete all. and remove all third-party network adapter management software.

8. In Device Manager, remove the network adapter and re-manually or let the operating system automatically install the NIC driver. This step detects and corrects corrupted registry entries on the network adapter bindings. If all other steps do not resolve the actual problem, follow this procedure.

Note: You can use the eight steps described above to solve the problem when you encounter local or dial-up connections in practice. As long as you follow the steps in sequence, basically you can solve the network connection related failures.