By default, the priority of both the wired and wireless network interfaces is high. If you want to change the priority to the wireless network, enter the connection attribute of the wired network interface, select the TCP/IP attribute, and click "advanced .... ", enter the Advanced TCP/IP
On the properties page, delete the gateway (if any) and change the following "interface hops" to "2" or higher. 2. Enter the TCP/IP settings of the wireless Nic, set the gateway, and change the interface hops to "1 ". 3. If the "use the default gateway on the remote network" option is displayed on the "General" page in "Advanced TCP/IP attributes" of the wireless network adapter
And hook it up. To be tested, the network explanation about the hops is as follows: I understand it. To put it bluntly, it is similar to the metric value of the Distance Vector routing selection Protocol-the number of hops. The number of hops is defined as the number of CIDR blocks that need to be routed to the destination network, that is, the number of routers that need to be routed. (More than 16 are considered inaccessible) if the router has two interfaces that can reach the network you want to access, it will ignore the metric value in the routing table, the data stream is forwarded to an interface with a relatively small metric value, because he thinks this path is the fastest. Similarly, a pc actually has a route table. For example, if you have two NICs that can reach the same destination address at the same time, one bandwidth is 10 M and the other is 100 M. If you set the interface hops of 10 m NICs to 2 and m to 1, the data will be forwarded first from the M Nic because the metric of this Nic is small. (The premise is that you are a win2000 or winxp System) when the network adapter is down, data will be forwarded from the 10 m network adapter. It acts as a floating route. How can we solve a new problem? Forget it. What does floating route mean. If the two NICs have the same number of hops, I guess the load will be balanced.