A simple description of Windows dual-NIC cross-network

Now generally work with notebooks, which have at least two NICs, wireless and Wired. This example is the use of wireless Sisu network, wired intranet, so that the external network can connect to an example of the intranet.

About this thing in fact very early on the application, just yesterday and used a bit, there have been some problems, failed to solve, but also a summary.

In the WinXP dual NIC use must add static routes, and Win7 generally can be automatically recognized, but there are unexpected circumstances. Other systems do not have a specific practice, but regardless of whether XP or Win7 in the event of an inability to determine the situation will take precedence of the cable network card.

Now let's briefly introduce the environment, I use the notebook wired network address is 1.2.200.170, the gateway is 1.2.200.168, which is used to access the intranet. My wireless network address is 192.168.0.104 gateway address is 192.168.0.1. I need the remote Desktop through QQ to let maintenance staff can remote to my computer, I through my notebook and then through the Windows comes with Remote Desktop Connection to 10.44.10.152 server.

Because it is not my computer, so I was not familiar with this computer, with the Win7 home base version, win+r after the input cmd and then began to configure static routes, but after the configuration prompt permission is not enough, then re-click to start to find the command prompt, Then right-click cmd to run as administrator, and there's a more complicated way to enter runas/user:administrator at the command prompt "cmd/k can also run as Administrator

It is recommended to empty the routing table before adding the routing table to prevent confusion and clear the command to Route-f

I then enter two commands to add a static route

Route add 0.0.0.0 Mask 0.0.0.0 192.168.0.1

Route add 10.0.0.0 Mask 255.0.0.0 1.2.200.168

These two commands entered after the prompt can not find the element, before I use XP computer never out of such a hint, so I began to check, did not find the problem, tossing a 5 minutes after opening the mobile phone Internet search found this command later in fact there are two parameters, I have less one, The specific reasons may be the difference between Win7 and XP, or it may be because the computer also has a Bluetooth network card. I then found the number of the two NICs by the route Print command, which is the first number before each NIC in the interface list, and for another long jump point, I did the test, setting how much seems to have no effect. Then my revised command is as follows

Route-f

Route add 0.0.0.0 Mask 0.0.0.0 192.168.0.1 if 14

Route add 10.0.0.0 Mask 255.0.0.0 1.2.200.168 if 11

After the addition is finished I try to surf the internet, can, ping the server does not pass! So I have to re-check the toss about 10 minutes after the same situation, I accidentally opened the remote connection 10.44.10.152 This server results, this is still ping this 10.44.10.152 still not pass, and I am sure this server can be ping through. Although I do not know why but my purpose is achieved, so the establishment of a connection so that the engineers are connected. However, this link is not very stable, about 40 minutes after the appearance of the 10.44.10.152 with about 1 minutes of disconnection, after automatic reconnection, about 10 minutes after the complete disconnection. At this point repeated the above command, can still surf the internet, but ping different 10.44.10.152 this server phenomenon, but this time even remote Desktop can not. After a brief thought I decided to put the two route configuration upside down as follows:

Route-f

Route add 10.0.0.0 Mask 255.0.0.0 1.2.200.168 if 11

Route add 0.0.0.0 Mask 0.0.0.0 192.168.0.1 if 14

Test the Internet is normal, ping the server through, remote connection through. This is when our engineers can play happily with our servers.

This is a problem to solve, but for the middle of the ping does not work but can be remote Desktop problems I have not been able to understand why this phenomenon occurs. A detailed description of the route command can be found in the command prompt, which is not mentioned here.

A simple description of Windows dual-NIC cross-network