Like all our friends at work, we have encountered the coexistence of wired and wireless networks. Sometimes, when both of them are on, they cannot access the Internet. The same is true for me, it was finally done in WINXP. It was relatively simple in Linux. Just run a few commands, but few commands were used in windows.
The situation is as follows: My Intranet (wired) is 192.168.100. *, that is, you can only use a LAN and cannot access the Internet. The other is the company's USB wireless network card (which can be used to browse the webpage normally and chat with qq), connected to a router. The Gateway is 192.168.1.1 and connected to a network cable, wireless connection fails.
Some people say that the priority of the network card is a problem, but when I enable the NIC priority option, I found that the priority of the wireless network is higher than that of the wired network, but still cannot access the Internet. Later I saw an articleArticle, Just do it.
The method is as follows:
1. set the wireless network card as the default route Gateway: Wireless Network Connection Properties-Internet Protocol (TCP/IP)-properties-advanced, manually enter the wireless route gateway, here is 192.168.1.1, the number of hops is 1, which is the highest priority. In this step, if both wired and wireless connections exist, all data is processed by the wireless Nic.
At this step, the author can access the Internet normally, but there is another step:
2. Set the exclusion information192.168.100The URL Connection Request of the. X road section is handled by the priority NIC: Enter the following command on the command line
Route-P add192.168.100.0 mask 255.255.255. 0192.168.100.1
Where192.168.100.0Is the local lan cidr block,192.168.100.1It is the default gateway for the subnet segment of the local machine, which must be filled in according to the actual situation.
After the above settings, All accesses to the primary network segment are handled by the wired network adapter, and the access to the Internet can be handled by the wireless network adapter, so there will be no conflict.
It's still being tested. It's okay for visual testing. I will update it if there are any side effects.