Troubleshoot Windows ' inability to automatically bind IP protocol stacks to network adapters

Symptoms are:

Win8 or Win7 cannot obtain an IP address, regardless of whether Ethernet or wireless networks are restricted.
Diagnostic results: Windows cannot automatically bind the IP protocol stack to the network adapter.

Solution:

WINDOWS7/8 system

The solution currently has a narrow range of solutions for both Niang and Google, most of which are WiFi-type issues that cannot be addressed to local connectivity problems.

Applicable to: 360, such as Kabbah anti-virus software uninstall is not clean, WiFi virtual AP can not uninstall the normal, legitimate virus control software uninstall is not clean, enterprise anti-virus software left the controlling end of the network situation.

Systems involved: Windows Vista above.

Problem performance:

1, with an exclamation point network connection.




2, LAN also cannot connect, can not ping any address, all return: "General failure" error.




3, unable to fill out the default gateway, but your local connection seems to be normal.







4, IPV4, V6 connection, the details are all empty.




5. Windows Diagnostics cannot be repaired, but the problem is explained.




6, the network card by a driver or service binding hijacked, this article's hijacking component is TPACKETV miniport.




7, Rogue components in the normal situation has not been damaged is not shown, but the display of hidden devices can be seen:







Solution Idea:

[post] The first thought is to put the dog Search Network Diagnostics fault description, but can be found in the solution is the number of words to solve the WiFi side of the situation, MS TechNet can not do. So the idea of tackling the diagnosis squarely was abandoned.

The second starting point is the driver is not the correct prompt, so the right key to uninstall, found that can not uninstall ... It is obvious that some components of the system are bound to an incorrect file, causing the general operation to fail, even if the file is deleted.

So put the dog search similar uninstall Miniport,uninstall bad Miniport,miniport is not work keyword, finally found a solution is effective, that is, replace the wrong component driver, and then uninstall, the system is normal.

Replace the drive direct selection system can be:


for the XP system

Ensure that the local wireless network switch open on the premise of 360 in the boot Start-service settings, or the wireless set to boot up on the good

Thanks to the original source: Http://www.suchso.com/ITLife/Windows cannot automatically bind the IP protocol stack to a network adapter solution. html