About the "Windows cannot automatically bind IP stack to a network adapter" problem causes a solution that cannot be connected to the Internet

The problem arises: The direct appearance of this problem is not to show the user this problem, but the wireless network driver may be a problem or Ethernet driver may be a problem, but as long as the user to view the "details", will get the title of the problem, and the nature of this problem is not the driving problem, I thought it was a driver problem, and I downloaded a new driver, but I didn't have any eggs. In fact, there should be a protocol conflict caused the NIC to not work properly, and then show that the driver has a problem.

Workaround: I'm talking about a protocol conflict, it should be some of your own downloaded software in the use of the network to provide a variety of driver protocols, and your computer's own network protocol conflict, resulting in the computer has no way to automatically select the Network IP protocol. The way to resolve the conflict is that you right-click on the computer status bar of the small computer or wireless icon, click on the Network and Sharing Center , find the change adapter settings , if the wireless connection is not on, right click on the WLAN, click Properties ,

My previous is the TX WiFi NAT driver Conflict, the front of the hook to remove it to solve. You may not be sure what your problem is, here's how to fix it, there are six options in the project that were selected at the outset :Microsoft two , link Layer Topology Discovery the first two ,Tcp/ipv6,Tcp/ipv4. you leave all this behind, and the rest will be removed, and the problem will be solved. Of course, if you want to determine exactly which conflict, you can try one, and if there is a problem again, then the answer is out.

If a local connection or Ethernet connection is not connected, right-click Ethernet or Local Area Connection, Click Properties,

This time, just keep the six options mentioned above, others can not, the problem should be solved.

(OK, hope can help you ~)

About the "Windows cannot automatically bind IP stack to a network adapter" problem causes a solution that cannot be connected to the Internet