Whether it's on the Internet or a LAN, we need to get the appropriate configuration of the network parameters from the "local connection". However, in the actual network process, we sometimes find that “local connections” may cause various inexplicable failures, which often cause us to be unable to set the network parameters in a targeted manner, thus affecting our Internet efficiency. Here are some of the more common failure phenomena that occur in the “local connection” and different countermeasures for each failure phenomenon. I believe that it will bring you benefits!
Try 1, Check the Internet settings
Considering that every computer in the LAN is set to automatically obtain an IP address, is it possible that the faulty computer does not correctly apply for a valid IP address or other Internet access parameters from the LAN DHCP server? In order to verify my guess, the author first consulted the Internet access parameters of the local working subnet and found that the working subnet address of the faulty computer is 10.176.1.x. If the faulty computer is currently using the IP address, it is located at 10.176.1.x. In the subnet, it means that the network connection between the computer and the target DHCP server is normal;
So, the author immediately opens the "Start" menu of the faulty computer, and clicks from it. Run the ” command, in the pop-up system run text box, enter the string command “cmd”, click the Enter key, the system will work Switch to the DOS command line working state, enter the string command "ldconfig; ipconfig /all" in this state, click the Enter key, the author sees the IP address used by the faulty computer as the result interface ;169.254.18.173”, and the IP address starting with "169.254" is actually assigned to the faulty computer by the Windows system. This means that the faulty computer does not apply for a valid Internet access parameter from the DHCP server at all, in other words, the local area network. The network connection between the DHCP server and the failed computer is not available.
Try 2, check the DHCP status
The network connection between the LAN DHCP server and the faulty computer is unreachable, will it be due to the abnormal state of the DHCP server itself, or its faulty computer? The Internet has been restricted? I think of this, I immediately tried to access the Internet from other ordinary computer systems in the LAN. After testing, I found that other computers can apply for valid Internet access parameters from the LAN DHCP server. Several ordinary computers were tested on the Internet, and the test results were normal. This ruled out the abnormality of the DHCP server itself.
In order to check whether the DHCP server has restricted the Internet access of the faulty computer, the author rushed to the server site, enters the corresponding host system as the system administrator, opens the DHCP console window, and enters the property setting interface of the DHCP server. From which the various setting options were checked in turn, and the result of the check did not find any suspicious places, which means that "local connection" is a limited failure, and there is no problem with the status of the DHCP server.
Try 3, reinstall the NIC driver
Since the DHCP server is in a normal state and the failed computer was able to access the Internet, there is no problem with the network connection between them. The problem may only be Out of the faulty computer itself, will it be that the driver of the network card device is not compatible with the Windows Vista system, or the driver of the network card device has been damaged? I think this point, I intend to first drive the old network card driver from Windows. The Vista system was completely uninstalled, and then the system was rescanned to install the driver for the NIC. The idea has been fixed, the author immediately right-click on the "Computer" icon on the system desktop, click the "Properties" command in the right-click menu, click the "Device Manager" option in the system properties window , find the target NIC device, and right-click the device option, and execute the “Uninstall” command from the pop-up shortcut menu, so that the Windows Vista system will automatically uninstall the old NIC driver from the computer. It's clean.
Next, the author right-clicks the name of the target host in the Device Manager window, and clicks the "Scan for hardware changes" command from the pop-up shortcut menu. It doesn't take long, Windows The Vista system found the NIC device and automatically installed the new driver. After the NIC driver was installed, the author immediately conducted an online access test, but the test results once again gave the author a head start. Previous12Next page Total 2 pages
The computer has been in use for a long time, and the number of files will be more
Due to its many advantages, WinXP system, even if it is stopped by Microsoft, there
WordPress is a blog platform developed using PHP language, users can set up their own website on the
In the process of using the computer, I often encounter the situation that the inpu
How to solve broadband 678 error under WinXP system
What is the process of Spoolsv.exe in WinXP system?
How to retrieve the encrypted partition file under Windows XP?
How does WinXP run the Desktop Cleanup Wizard? Method of executing the desktop cleanup wizard
The rookie defense software crash has a trick
How to solve the Windows XP taskbar becomes a double-layer problem
Introduction to WinXP Security Mechanism
Share the experience of Tencent's micro cloud space to 10T
Remove the magic tricks that affect the appearance of Windows desktop icons
The solution to the fake crash after entering the XP system
Seven hidden devices for Windows running commands
Adobe CS6 series failed to solve the WIN7 WIN8 installation
Win7 system sets some methods to run on the specified CPU
Win7 open the computer management method
IE11 browser official official version installation tutorial
Win7 system using compatibility mode to run the program tutorial
Win10 annual upgrade release! Multiple content updates
How to solve the problem of installing the system failed to read the file?