I'm having a little bit of an issue with routing. I have a server with 4 nics, 2 not connect and 2 connected. The first is configured as follows. IP: 172.19.250.110 NM: 255.255.255.0 GW: 172.19.250.1 The second configured as follows IP: 192.168.250.110 NM: 255.255.255.0 GW: empty The 2nd network card is to be used in an exchange dag and as such from what I've read should not have a gw address. The DAG is across a WAN and as such I entered the following static route. route add 192.168.251.0 mask 255.255.255.0 192.168.250.1 metric 10 if 17 At this point I should explain that the gw on each network is the same physical unit that currently has 2 vlans. VLAN 10 for the 1st NIC (and network), VLAN 30 for the 2nd NIC. Each VLAN is excluded from the other so there is no funn cross routing happening there. If I then ping 192.168.251.1 (which is the gw address on the other network) I get a reply and all seems fine, however I wanted make sure it wasn't pinging via the 1st nic and did a pathping to 192.168.251.1 and found that it was actually pinging through the 1st nic not the 2nd. If I add a gw address on the 2nd NIC and do a pathping to 192.168.251.1 the 2nd nic is used, but I need the 2nd nic to be used to route traffic to the 192.168.251/24 network without a gateway and I thought the route above would of done that. Below is a copy of the current output from route print =========================================================================== Interface List 17...3c 4a 92 6e a6 98 ......HP NC382i DP Multifunction Gigabit Server Adapter #4 15...3c 4a 92 6e a6 96 ......HP NC382i DP Multifunction Gigabit Server Adapter #3 12...3c 4a 92 6e a6 94 ......HP NC382i DP Multifunction Gigabit Server Adapter #2 11...3c 4a 92 6e a6 92 ......HP NC382i DP Multifunction Gigabit Server Adapter 1...........................Software Loopback Interface 1 13...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter 14...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2 16...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #3 18...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #4 19...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface =========================================================================== IPv4 Route Table =========================================================================== Active Routes: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 172.19.250.1 172.19.250.110 266 127.0.0.0 255.0.0.0 On-link 127.0.0.1 306 127.0.0.1 255.255.255.255 On-link 127.0.0.1 306 127.255.255.255 255.255.255.255 On-link 127.0.0.1 306 172.19.250.0 255.255.255.0 On-link 172.19.250.110 266 172.19.250.110 255.255.255.255 On-link 172.19.250.110 266 172.19.250.255 255.255.255.255 On-link 172.19.250.110 266 192.168.251.0 255.255.255.0 192.168.250.1 192.168.250.110 20 224.0.0.0 240.0.0.0 On-link 127.0.0.1 306 224.0.0.0 240.0.0.0 On-link 172.19.250.110 266 224.0.0.0 240.0.0.0 On-link 192.168.250.110 266 255.255.255.255 255.255.255.255 On-link 127.0.0.1 306 255.255.255.255 255.255.255.255 On-link 172.19.250.110 266 255.255.255.255 255.255.255.255 On-link 192.168.250.110 266 =========================================================================== Persistent Routes: Network Address Netmask Gateway Address Metric 0.0.0.0 0.0.0.0 172.19.250.1 Default =========================================================================== IPv6 Route Table =========================================================================== Active Routes: If Metric Network Destination Gateway 1 306 ::1/128 On-link 11 266 fe80::/64 On-link 17 266 fe80::/64 On-link 17 266 fe80::5019:17e5:4200:ebca/128 On-link 11 266 fe80::e93a:fe27:871a:7f4d/128 On-link 1 306 ff00::/8 On-link 11 266 ff00::/8 On-link 17 266 ff00::/8 On-link =========================================================================== Persistent Routes: None Any ideas, I'm guessing I'm missing something simple but just can't see it.

Hi, You said "I wanted make sure it wasn't pinging via the 1st nic and did a pathping to 192.168.251.1 and found that it was actually pinging through the 1st nic not the 2nd. Could you share the results of the path ping? Is strong host and weak host enabled on your server? Please review this article to see if this helps your case: http://blogs.technet.com/b/networking/archive/2009/04/25/source-ip-address-selection-on-a-multi-homed-windows-computer.aspxRegards, Amit Saxena (Microsoft). Please remember to use Mark as Answer or "vote as helpful" on the posts that help you. Keep Walking!

Hi Amit, Please find below the pathping and also netsh interface ipv4 show interface for each of the 2 interfaces. Interface 11 is the 1st nic and interface 17 is the 2nd nic. I'll be honest I've never changed or even looked at strong host/weak host information but they appear disabled from the information below. Interestingly I re-enabled (had disabled while not looking directly at the issue) the 2nd nic to do the pathping, and after entering the static route I got the results I would expect (See 2nd pathping) however I didn't know untill I opened the txt file as I'd used "pathping 192.168.251.1 > pathping.txt" once I saw this I re-ran the test thinking I'd get the same result and I didn't instead I got the same result as before (see 1st pathping). Out of the 20-30 or so pathpings I've run that is the first and seems only time I got the result I would expect. I tried re-doing the steps disabling the card, enable enter route to see if I could reproduce the correct result but no. Everytime I get the exact same pathping as the 1st one entered below Tracing route to 192.168.251.1 over a maximum of 30 hops 0 xxxxx.xxxxx.local [172.19.250.110] 1 * 172.19.250.1 2 192.168.251.1 Computing statistics for 50 seconds... Source to Here This Node/Link Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address 0 xxxxx.xxxxx.local [172.19.250.110] 0/ 100 = 0% | 1 0ms 0/ 100 = 0% 0/ 100 = 0% 172.19.250.1 0/ 100 = 0% | 2 39ms 0/ 100 = 0% 0/ 100 = 0% 192.168.251.1 Trace complete. Tracing route to 192.168.251.1 over a maximum of 30 hops 0 xxxxx.xxxxx.local [192.168.250.110] 1 * 192.168.250.1 2 192.168.251.1 Computing statistics for 50 seconds... Source to Here This Node/Link Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address 0 xxxxx.xxxxx.local [192.168.250.110] 0/ 100 = 0% | 1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.250.1 0/ 100 = 0% | 2 39ms 0/ 100 = 0% 0/ 100 = 0% 192.168.251.1 Trace complete. Interface Local Area Connection Parameters ---------------------------------------------- IfLuid : ethernet_5 IfIndex : 11 State : connected Metric : 10 Link MTU : 1500 bytes Reachable Time : 27000 ms Base Reachable Time : 30000 ms Retransmission Interval : 1000 ms DAD Transmits : 3 Site Prefix Length : 64 Site Id : 1 Forwarding : disabled Advertising : disabled Neighbor Discovery : enabled Neighbor Unreachability Detection : enabled Router Discovery : dhcp Managed Address Configuration : enabled Other Stateful Configuration : enabled Weak Host Sends : disabled Weak Host Receives : disabled Use Automatic Metric : enabled Ignore Default Routes : disabled Advertised Router Lifetime : 1800 seconds Advertise Default Route : disabled Current Hop Limit : 0 Force ARPND Wake up patterns : disabled Directed MAC Wake up patterns : disabled Interface DAG Parameters ---------------------------------------------- IfLuid : ethernet_15 IfIndex : 17 State : connected Metric : 10 Link MTU : 1500 bytes Reachable Time : 30500 ms Base Reachable Time : 30000 ms Retransmission Interval : 1000 ms DAD Transmits : 3 Site Prefix Length : 64 Site Id : 1 Forwarding : disabled Advertising : disabled Neighbor Discovery : enabled Neighbor Unreachability Detection : enabled Router Discovery : dhcp Managed Address Configuration : enabled Other Stateful Configuration : enabled Weak Host Sends : disabled Weak Host Receives : disabled Use Automatic Metric : enabled Ignore Default Routes : disabled Advertised Router Lifetime : 1800 seconds Advertise Default Route : disabled Current Hop Limit : 0 Force ARPND Wake up patterns : disabled Directed MAC Wake up patterns : disabled

Hi, Thanks for posting here. May I know the interface binding order on this server ? Please take look the session “Route Determination Process” in the article below first : Chapter 5 – IP Routing http://technet.microsoft.com/en-us/library/bb727001.aspx#EEAA Meanwhile, we may need to have the weak host receive behavior enabled on this server , take look the explanations and the method about how to enable it : Strong and Weak Host Models http://technet.microsoft.com/en-us/magazine/2007.09.cableguy.aspx Thanks. Tiger LiTiger Li TechNet Community Support

Hi, The interface information about says that weak host receive is disabled. In terms of binding order, the 2nd Nic is top of the list followed but the 1st Nic then the 2 disabled NICs

Hi, Any specific reason for keeping the NIC2 (192.168.250.110) disabled? Please correct me if I am wrong: You disable 192.168.250.110, try to ping 192.168.251.1 and the traffic goes out of NIC1 (172.19.250.110). Please correct if I am wrong. If the the above undertanding is correct, I would consider this behaviour normal. Here's why: 192.168.250.110 is disabled hence the only active/connected NIC is 172.19.250.110. When you ping any address (be it of any range) it will go out of this NIC. If the desitnation address of a different subnet, that doesn't have an *active/enabled* route in the netork table, the packet will be given to the DG (172.19.250.1) If the DG has the route to the destination network, it will deliver the packet to the next hop, in order to reach it. Thus, since 172.19.250.1 has the route for 192.168.250.1, it is delivering the packet therefore.Regards, Amit Saxena (Microsoft). Please remember to use Mark as Answer or "vote as helpful" on the posts that help you. Keep Walking!

Hi, Any specific reason for keeping the NIC2 (192.168.250.110) disabled? Please correct me if I am wrong: You disable 192.168.250.110, try to ping 192.168.251.1 and the traffic goes out of NIC1 (172.19.250.110). Please correct if I am wrong. If the the above undertanding is correct, I would consider this behaviour normal. Here's why: 192.168.250.110 is disabled hence the only active/connected NIC is 172.19.250.110. When you ping any address (be it of any range) it will go out of this NIC. If the desitnation address of a different subnet, that doesn't have an *active/enabled* route in the netork table, the packet will be given to the DG (172.19.250.1) If the DG has the route to the destination network, it will deliver the packet to the next hop, in order to reach it. Thus, since 172.19.250.1 has the route for 192.168.250.1, it is delivering the packet therefore. Regards, Amit Saxena (Microsoft). Please remember to use “Mark as Answer” or "vote as helpful" on the posts that help you. Keep Walking! Umm, Sorry maybe somewhere I made it sound like it was disabled but no when I'm pinging 192.168.251.1 the nic is connected and enabled

Hi, Thanks for update. I’ve tested this scenario in lab however can’t reproduce it . Traffics will correctly go out form the interface that we bound in that routing entry (route add 192.168.251.0 mask 255.255.255.0 192.168.250.1 metric 10 if 17) . We can see that system will first reach the interface 192.168.250.110 form pathping result. Please first make sure the interface 17(HP NC382i DP Multifunction Gigabit Server Adapter #4) is the interface we set address 192.168.250.110 to. Could you show us the ipconfig /all result here also ? Meanwhile, perhaps we can also disable all no connected interfaces and restart the host to see if the route table will take effect. The another method we can try is that resetting TCP/IP on this server and reconfigure the whole settings and see how is going. How to reset Internet Protocol (TCP/IP) http://support.microsoft.com/kb/299357 Thanks. Tiger LiTiger Li TechNet Community Support

Hi, This was is what is so annoying, this isn't a complicated thing to do but it just doesn't seem to work. Below I've put the following route print information. 1st is with only the 172.19.250.110 card enabled. 2nd is with the 192.168.250.110 card enabled aswell. 3rd is with the card enabled and route added. I've also added the ipconfig /all information below that. =========================================================================== Interface List 11...3c 4a 92 6e a6 92 ......HP NC382i DP Multifunction Gigabit Server Adapter 1...........................Software Loopback Interface 1 13...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter 19...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface =========================================================================== IPv4 Route Table =========================================================================== Active Routes: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 172.19.250.1 172.19.250.110 266 127.0.0.0 255.0.0.0 On-link 127.0.0.1 306 127.0.0.1 255.255.255.255 On-link 127.0.0.1 306 127.255.255.255 255.255.255.255 On-link 127.0.0.1 306 172.19.250.0 255.255.255.0 On-link 172.19.250.110 266 172.19.250.110 255.255.255.255 On-link 172.19.250.110 266 172.19.250.255 255.255.255.255 On-link 172.19.250.110 266 224.0.0.0 240.0.0.0 On-link 127.0.0.1 306 224.0.0.0 240.0.0.0 On-link 172.19.250.110 266 255.255.255.255 255.255.255.255 On-link 127.0.0.1 306 255.255.255.255 255.255.255.255 On-link 172.19.250.110 266 =========================================================================== Persistent Routes: Network Address Netmask Gateway Address Metric 0.0.0.0 0.0.0.0 172.19.250.1 Default =========================================================================== IPv6 Route Table =========================================================================== Active Routes: If Metric Network Destination Gateway 1 306 ::1/128 On-link 11 266 fe80::/64 On-link 11 266 fe80::e93a:fe27:871a:7f4d/128 On-link 1 306 ff00::/8 On-link 11 266 ff00::/8 On-link =========================================================================== Persistent Routes: None =========================================================================== Interface List 17...3c 4a 92 6e a6 98 ......HP NC382i DP Multifunction Gigabit Server Adapter #4 11...3c 4a 92 6e a6 92 ......HP NC382i DP Multifunction Gigabit Server Adapter 1...........................Software Loopback Interface 1 13...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter 14...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2 19...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface =========================================================================== IPv4 Route Table =========================================================================== Active Routes: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 172.19.250.1 172.19.250.110 266 127.0.0.0 255.0.0.0 On-link 127.0.0.1 306 127.0.0.1 255.255.255.255 On-link 127.0.0.1 306 127.255.255.255 255.255.255.255 On-link 127.0.0.1 306 172.19.250.0 255.255.255.0 On-link 172.19.250.110 266 172.19.250.110 255.255.255.255 On-link 172.19.250.110 266 172.19.250.255 255.255.255.255 On-link 172.19.250.110 266 192.168.250.0 255.255.255.0 On-link 192.168.250.110 266 192.168.250.110 255.255.255.255 On-link 192.168.250.110 266 192.168.250.255 255.255.255.255 On-link 192.168.250.110 266 224.0.0.0 240.0.0.0 On-link 127.0.0.1 306 224.0.0.0 240.0.0.0 On-link 172.19.250.110 266 224.0.0.0 240.0.0.0 On-link 192.168.250.110 266 255.255.255.255 255.255.255.255 On-link 127.0.0.1 306 255.255.255.255 255.255.255.255 On-link 172.19.250.110 266 255.255.255.255 255.255.255.255 On-link 192.168.250.110 266 =========================================================================== Persistent Routes: Network Address Netmask Gateway Address Metric 0.0.0.0 0.0.0.0 172.19.250.1 Default =========================================================================== IPv6 Route Table =========================================================================== Active Routes: If Metric Network Destination Gateway 1 306 ::1/128 On-link 11 266 fe80::/64 On-link 17 266 fe80::/64 On-link 17 266 fe80::5019:17e5:4200:ebca/128 On-link 11 266 fe80::e93a:fe27:871a:7f4d/128 On-link 1 306 ff00::/8 On-link 11 266 ff00::/8 On-link 17 266 ff00::/8 On-link =========================================================================== Persistent Routes: None =========================================================================== Interface List 17...3c 4a 92 6e a6 98 ......HP NC382i DP Multifunction Gigabit Server Adapter #4 11...3c 4a 92 6e a6 92 ......HP NC382i DP Multifunction Gigabit Server Adapter 1...........................Software Loopback Interface 1 13...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter 14...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2 19...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface =========================================================================== IPv4 Route Table =========================================================================== Active Routes: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 172.19.250.1 172.19.250.110 266 127.0.0.0 255.0.0.0 On-link 127.0.0.1 306 127.0.0.1 255.255.255.255 On-link 127.0.0.1 306 127.255.255.255 255.255.255.255 On-link 127.0.0.1 306 172.19.250.0 255.255.255.0 On-link 172.19.250.110 266 172.19.250.110 255.255.255.255 On-link 172.19.250.110 266 172.19.250.255 255.255.255.255 On-link 172.19.250.110 266 192.168.250.0 255.255.255.0 On-link 192.168.250.110 266 192.168.250.110 255.255.255.255 On-link 192.168.250.110 266 192.168.250.255 255.255.255.255 On-link 192.168.250.110 266 192.168.251.0 255.255.255.0 192.168.250.1 192.168.250.110 20 224.0.0.0 240.0.0.0 On-link 127.0.0.1 306 224.0.0.0 240.0.0.0 On-link 172.19.250.110 266 224.0.0.0 240.0.0.0 On-link 192.168.250.110 266 255.255.255.255 255.255.255.255 On-link 127.0.0.1 306 255.255.255.255 255.255.255.255 On-link 172.19.250.110 266 255.255.255.255 255.255.255.255 On-link 192.168.250.110 266 =========================================================================== Persistent Routes: Network Address Netmask Gateway Address Metric 0.0.0.0 0.0.0.0 172.19.250.1 Default =========================================================================== IPv6 Route Table =========================================================================== Active Routes: If Metric Network Destination Gateway 1 306 ::1/128 On-link 11 266 fe80::/64 On-link 17 266 fe80::/64 On-link 17 266 fe80::5019:17e5:4200:ebca/128 On-link 11 266 fe80::e93a:fe27:871a:7f4d/128 On-link 1 306 ff00::/8 On-link 11 266 ff00::/8 On-link 17 266 ff00::/8 On-link =========================================================================== Persistent Routes: None Windows IP Configuration Host Name . . . . . . . . . . . . : xxxxx Primary Dns Suffix . . . . . . . : xxxx.local Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : xxxx.local Ethernet adapter DAG: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : HP NC382i DP Multifunction Gigabit Server Adapter #4 Physical Address. . . . . . . . . : 3C-4A-92-6E-A6-98 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::5019:17e5:4200:ebca%17(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.250.110(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : DHCPv6 IAID . . . . . . . . . . . : 440158866 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-15-38-B4-F6-3C-4A-92-6E-A6-92 DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1 fec0:0:0:ffff::2%1 fec0:0:0:ffff::3%1 NetBIOS over Tcpip. . . . . . . . : Enabled Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : HP NC382i DP Multifunction Gigabit Server Adapter Physical Address. . . . . . . . . : 3C-4A-92-6E-A6-92 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::e93a:fe27:871a:7f4d%11(Preferred) IPv4 Address. . . . . . . . . . . : 172.19.250.110(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 172.19.250.1 DHCPv6 IAID . . . . . . . . . . . : 238832274 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-15-38-B4-F6-3C-4A-92-6E-A6-92 DNS Servers . . . . . . . . . . . : 172.19.250.104 NetBIOS over Tcpip. . . . . . . . : Enabled Tunnel adapter isatap.{307E0907-C98D-472E-82C2-31FD67942374}: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft ISATAP Adapter Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Tunnel adapter Teredo Tunneling Pseudo-Interface: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes

I would second Tiger's recommendation. Reset the TCP/IP please. Also, let's make sure we have the latest NIC drivers and firmware. How to reset TCP/IP http://support.microsoft.com/kb/299357Regards, Amit Saxena (Microsoft). Please remember to use Mark as Answer or "vote as helpful" on the posts that help you. Keep Walking!