j_friedrich
asked on
How does XP decide what NIC port to use if you have a multi-homed machine?
Hi guys.
We have setup an XP multi-homed machine. We have 3 NIC's in this box with different IP's/different subnets assigned to them. We want XP to use a specific NIC port as the default for regular traffic. We are trying to force it to use a specific NIC port but are finding that it seems to randomly pick a port and stick with it. For example, 192.168.4.100 is the particular IP it always want to use. We can unplug that NIC port and XP will then pick another NIC port to use. As soon as we plug the 192.168.4.100 NIC port back in, it jumps back to this port. In other words, how do we force XP to use a specific NIC port and stick to it?
Thanks for everyones help.
Jason
We have setup an XP multi-homed machine. We have 3 NIC's in this box with different IP's/different subnets assigned to them. We want XP to use a specific NIC port as the default for regular traffic. We are trying to force it to use a specific NIC port but are finding that it seems to randomly pick a port and stick with it. For example, 192.168.4.100 is the particular IP it always want to use. We can unplug that NIC port and XP will then pick another NIC port to use. As soon as we plug the 192.168.4.100 NIC port back in, it jumps back to this port. In other words, how do we force XP to use a specific NIC port and stick to it?
Thanks for everyones help.
Jason
the pending options in the advanced drop down list of the network connections window will decide wich will used first and if the distination is on on of the two nic's it will choose the matched network id without looking to the pending
Based on the metric of each connection....
How to change the binding order of network adapters in Windows XP and in Windows 2000
http://support.microsoft.com/kb/894564
Specifically, the section on the fixed metric....
What is Windows XP's automatic metric feature?
http://www.windowsitpro.com/Article/ArticleID/27315/27315.html
How to change the binding order of network adapters in Windows XP and in Windows 2000
http://support.microsoft.com/kb/894564
Specifically, the section on the fixed metric....
What is Windows XP's automatic metric feature?
http://www.windowsitpro.com/Article/ArticleID/27315/27315.html
ASKER
Hi guys.
Thanks for the response. What we are finding is that after changing the metric of the NIC cards, the particular program that we want to use on a specific port will after time jump to another NIC port. For example: 192.168.4.100 has a metric of 1. 192.168.13.100 has a metric of 9999. Even though we specifically told the program to use 192.168.4.100, we are finding after a while, the program is now broadcasting on 192.168.13.100 with the metric of 9999? What gives? How do we keep the program stuck to a particular NIC port. BTW, it's just not one program, but many that we bind to individual NIC ports.
Thanks again.
Thanks for the response. What we are finding is that after changing the metric of the NIC cards, the particular program that we want to use on a specific port will after time jump to another NIC port. For example: 192.168.4.100 has a metric of 1. 192.168.13.100 has a metric of 9999. Even though we specifically told the program to use 192.168.4.100, we are finding after a while, the program is now broadcasting on 192.168.13.100 with the metric of 9999? What gives? How do we keep the program stuck to a particular NIC port. BTW, it's just not one program, but many that we bind to individual NIC ports.
Thanks again.
maybe creating static routes using the route add command??
What is the purpose of this server? Does it serve to 3 different subnets at once?
What is the purpose of this server? Does it serve to 3 different subnets at once?
ASKER
Yes, it does serve 3 subnets at once.
Anyways, trying to keep things simple on our end, does server 2003 or vista offer any advantages to doing this? Or will it be the same method of adding static routes? Can you also give us an example of using the route add command so that we don't have NIC port jumping.
thanks again for your time.
Anyways, trying to keep things simple on our end, does server 2003 or vista offer any advantages to doing this? Or will it be the same method of adding static routes? Can you also give us an example of using the route add command so that we don't have NIC port jumping.
thanks again for your time.
ASKER
Hi guys.
Ok. We are ready to throw microsoft in the garbage. We have done all the above. We have setup static routes to do the destinations. XP is still jumping subnets and deciding to broadcast on whatever NIC it wants. There has got to be something that we are missing? Any suggestions?
Thanks for your time.
Ok. We are ready to throw microsoft in the garbage. We have done all the above. We have setup static routes to do the destinations. XP is still jumping subnets and deciding to broadcast on whatever NIC it wants. There has got to be something that we are missing? Any suggestions?
Thanks for your time.
Sorry for not getting back to you sooner on the route add.....
http://www.windowsitpro.com/Articles/ArticleID/27171/27171.html?Ad=1
Can you do a route print on your machine and please post?
http://www.windowsitpro.com/Articles/ArticleID/27171/27171.html?Ad=1
Can you do a route print on your machine and please post?
ASKER
Hi guys.
Here is the route print. We specifically want traffic going out of the 192.168.13.1 gateway. IF 0x4 is the IP of 192.168.13.33. We are finding some traffic popping up on the 192.168.4.1 gateway which is what we don't want.
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\jjf>route print
==========================
Interface List
0x1 ..........................
0x2 ...00 1a a0 9a e3 16 ...... Intel(R) 82562V-2 10/100 Network Connection - Pa
cket Scheduler Miniport
0x3 ...00 15 17 3e 16 87 ...... Intel(R) PRO/1000 PT Dual Port Server Adapter #2
- Packet Scheduler Miniport
0x4 ...00 15 17 3e 16 86 ...... Intel(R) PRO/1000 PT Dual Port Server Adapter -
Packet Scheduler Miniport
==========================
==========================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.2.1 192.168.2.33 9998
0.0.0.0 0.0.0.0 192.168.4.1 192.168.4.33 9999
0.0.0.0 0.0.0.0 192.168.13.1 192.168.13.33 1
66.0.0.0 255.0.0.0 192.168.13.1 192.168.13.33 1
69.0.0.0 255.0.0.0 192.168.13.1 192.168.13.33 1
72.0.0.0 255.0.0.0 192.168.13.1 192.168.13.33 1
74.0.0.0 255.0.0.0 192.168.13.1 192.168.13.33 1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
169.254.0.0 255.255.0.0 192.168.13.33 192.168.13.33 30
192.168.2.0 255.255.255.0 192.168.2.33 192.168.2.33 9998
192.168.2.33 255.255.255.255 127.0.0.1 127.0.0.1 9998
192.168.2.255 255.255.255.255 192.168.2.33 192.168.2.33 9998
192.168.4.0 255.255.255.0 192.168.4.33 192.168.4.33 9999
192.168.4.33 255.255.255.255 127.0.0.1 127.0.0.1 9999
192.168.4.255 255.255.255.255 192.168.4.33 192.168.4.33 9999
192.168.13.0 255.255.255.0 192.168.13.33 192.168.13.33 1
192.168.13.33 255.255.255.255 127.0.0.1 127.0.0.1 1
192.168.13.255 255.255.255.255 192.168.13.33 192.168.13.33 1
192.246.40.244 255.255.255.255 192.168.13.1 192.168.13.33 1
207.0.0.0 255.0.0.0 192.168.13.1 192.168.13.33 1
224.0.0.0 240.0.0.0 192.168.2.33 192.168.2.33 9998
224.0.0.0 240.0.0.0 192.168.4.33 192.168.4.33 9999
224.0.0.0 240.0.0.0 192.168.13.33 192.168.13.33 1
255.255.255.255 255.255.255.255 192.168.2.33 192.168.2.33 1
255.255.255.255 255.255.255.255 192.168.4.33 192.168.4.33 1
255.255.255.255 255.255.255.255 192.168.13.33 192.168.13.33 1
Default Gateway: 192.168.13.1
==========================
Persistent Routes:
Network Address Netmask Gateway Address Metric
74.0.0.0 255.0.0.0 192.168.13.1 1
66.0.0.0 255.0.0.0 192.168.13.1 1
72.0.0.0 255.0.0.0 192.168.13.1 1
69.0.0.0 255.0.0.0 192.168.13.1 1
192.246.40.244 255.255.255.255 192.168.13.1 1
207.0.0.0 255.0.0.0 192.168.13.1 1
C:\Documents and Settings\jjf>
Thanks.
Here is the route print. We specifically want traffic going out of the 192.168.13.1 gateway. IF 0x4 is the IP of 192.168.13.33. We are finding some traffic popping up on the 192.168.4.1 gateway which is what we don't want.
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\jjf>route print
==========================
Interface List
0x1 ..........................
0x2 ...00 1a a0 9a e3 16 ...... Intel(R) 82562V-2 10/100 Network Connection - Pa
cket Scheduler Miniport
0x3 ...00 15 17 3e 16 87 ...... Intel(R) PRO/1000 PT Dual Port Server Adapter #2
- Packet Scheduler Miniport
0x4 ...00 15 17 3e 16 86 ...... Intel(R) PRO/1000 PT Dual Port Server Adapter -
Packet Scheduler Miniport
==========================
==========================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.2.1 192.168.2.33 9998
0.0.0.0 0.0.0.0 192.168.4.1 192.168.4.33 9999
0.0.0.0 0.0.0.0 192.168.13.1 192.168.13.33 1
66.0.0.0 255.0.0.0 192.168.13.1 192.168.13.33 1
69.0.0.0 255.0.0.0 192.168.13.1 192.168.13.33 1
72.0.0.0 255.0.0.0 192.168.13.1 192.168.13.33 1
74.0.0.0 255.0.0.0 192.168.13.1 192.168.13.33 1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
169.254.0.0 255.255.0.0 192.168.13.33 192.168.13.33 30
192.168.2.0 255.255.255.0 192.168.2.33 192.168.2.33 9998
192.168.2.33 255.255.255.255 127.0.0.1 127.0.0.1 9998
192.168.2.255 255.255.255.255 192.168.2.33 192.168.2.33 9998
192.168.4.0 255.255.255.0 192.168.4.33 192.168.4.33 9999
192.168.4.33 255.255.255.255 127.0.0.1 127.0.0.1 9999
192.168.4.255 255.255.255.255 192.168.4.33 192.168.4.33 9999
192.168.13.0 255.255.255.0 192.168.13.33 192.168.13.33 1
192.168.13.33 255.255.255.255 127.0.0.1 127.0.0.1 1
192.168.13.255 255.255.255.255 192.168.13.33 192.168.13.33 1
192.246.40.244 255.255.255.255 192.168.13.1 192.168.13.33 1
207.0.0.0 255.0.0.0 192.168.13.1 192.168.13.33 1
224.0.0.0 240.0.0.0 192.168.2.33 192.168.2.33 9998
224.0.0.0 240.0.0.0 192.168.4.33 192.168.4.33 9999
224.0.0.0 240.0.0.0 192.168.13.33 192.168.13.33 1
255.255.255.255 255.255.255.255 192.168.2.33 192.168.2.33 1
255.255.255.255 255.255.255.255 192.168.4.33 192.168.4.33 1
255.255.255.255 255.255.255.255 192.168.13.33 192.168.13.33 1
Default Gateway: 192.168.13.1
==========================
Persistent Routes:
Network Address Netmask Gateway Address Metric
74.0.0.0 255.0.0.0 192.168.13.1 1
66.0.0.0 255.0.0.0 192.168.13.1 1
72.0.0.0 255.0.0.0 192.168.13.1 1
69.0.0.0 255.0.0.0 192.168.13.1 1
192.246.40.244 255.255.255.255 192.168.13.1 1
207.0.0.0 255.0.0.0 192.168.13.1 1
C:\Documents and Settings\jjf>
Thanks.
This is why it is going to the .13 sunbet....
"0.0.0.0 0.0.0.0 192.168.13.1 192.168.13.33 1"
by replacing it with the following....
route -p add 0.0.0.0 mask 0.0.0.0 192.168.4.33 metric 1 if 0x4
That *should* direct outbound traffic to this NIC. But are you still wanting to send out the the LAN on different NICs, based on a "per app" setting?
The rest of the routes look good, in terms that the subnets are getting the right traffic, and general broadcasts are going out on all interfaces.....
"0.0.0.0 0.0.0.0 192.168.13.1 192.168.13.33 1"
by replacing it with the following....
route -p add 0.0.0.0 mask 0.0.0.0 192.168.4.33 metric 1 if 0x4
That *should* direct outbound traffic to this NIC. But are you still wanting to send out the the LAN on different NICs, based on a "per app" setting?
The rest of the routes look good, in terms that the subnets are getting the right traffic, and general broadcasts are going out on all interfaces.....
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.