Hi, I'm using Vista Ultimate 64-bit.I have two network adapters in my pc. They both connect to the same switch/router/firewall. I have disabled all IPv6 on Vista. Vista, on boot, creates a default routing table like THIS:IPv4 Route Table===========================================================================Active Routes:Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 10.169.212.1 10.169.212.10 10 10.169.212.0 255.255.255.224 On-link 10.169.212.10 266 10.169.212.10 255.255.255.255 On-link 10.169.212.10 266 10.169.212.31 255.255.255.255 On-link 10.169.212.10 266 10.169.213.0 255.255.255.224 On-link 10.169.213.10 266 10.169.213.10 255.255.255.255 On-link 10.169.213.10 266 10.169.213.31 255.255.255.255 On-link 10.169.213.10 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 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 10.169.212.10 266 224.0.0.0 240.0.0.0 On-link 10.169.213.10 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 10.169.212.10 266 255.255.255.255 255.255.255.255 On-link 10.169.213.10 266===========================================================================Persistent Routes: NoneOf key interest here is the default route metrics for 10.169.212.0 and 10.169.213.0.The problem is that when my pc (10.169.212.10 and 10.169.213.10, two physically separate network interfaces) tries to talk to 10.169.213.28, you would think that it would take the path that is closest, which would be through the DIRECTLY CONNECTED 10.169.213.10 interface. It does not. It goes THROUGH the 10.169.212.10 interface, up to the switch gateway, then the gateway sends it over to the 10.169.213.28 address. What I WANT is for any communciation sourcing FROM my vista machine TO any 10.169.213.0 address to use the directly attached 10.169.213.10 interface to get to it's destination.I think that the problem is that the automatically generated default metric costs for both networks is identical (276 on the table above).I would LIKE to change the metric value on all the 10.169.213.* routes above to be LOWER than 276 to correct the issue, but I can't figure out how to do that. Because they're directly connected (on-link) and automatically generated I can't get a ROUTE CHANGE command to function on them.THIS HYPERLINK is a graphical example of the PROBLEM.THIS HYPERLINK is a graphical example of the DESIRED BEHAVIOUR.Can anyone help me get my vista default routing changed to produce DESIRED BEHAVIOUR on boot?I can get the desired behaviour if, after I boot vista, I established the undesirable communication and then disable my 10.169.212.10 interface. THEN it starts routing over the proper path, and it stays that way, even if I turn my 10.169.212.10 interface back on.Some additional information:10.169.212.10 is DHCP, a statically reserved address in the dhcp server in my router/switch.10.169.213.10 is statically assigned, no DHCP involved.The reason I want the traffic to go over the path indicated by the DESIRED BEHAVIOUR diagram is simple. 10.169.212.10 is my "main" network interface on my pc - what I use for everything. 10.169.213.10 is a network interface I enabled specifically to carry heavy video traffic from a remote camera, which is connected on the same switch. The VLANS keep the traffic separated, but only if the correct interface was used to set up the communication in the first place. Basically, I don' t want that video traffic on the 10.169.212.10 interface at all.

Can anyone help with this at all?

Hi, How do you know that the network packets are sent through the 10.169.212.10 network adapter but not the 10.169.213.10 network adapter when you access the 10.169.213.28? Could you capture the network packets for further research? I have established a similar environment as you described but I did not encounter this issue. The network packets are sent out from the expected network adapter. In addition, to make the metric of the route 10.169.213.0 lower than the one of 10.169.212.0, you can perform the following steps: 1. Open Network Connections by typing ncpa.cpl in the Start Search box and pressing Enter. 2. Right-click the network connection that the IP address is 10.169.213.10, select Properties, double-click Internet Connection Version 4, and click Advanced. 3. In the IP Settings tab, clear the Automatic metric check box and type the interface metric such as 10. Hope it helps.

I too am looking for a solution to this problem. I've got a couple of Windows 2008 server machines with dual-NICs. The appropriate catch-all and specific network routes are in place, however simply pinging an address on one of the networks triggers the 0.0.0.0 rule and sends the data to the default gateway, NOT DIRECTLY OUT the NIC like it should. I've been screwing around with this for awhile, and cannot figure out for the life of me why by default it would not send direct LAN traffic to the LAN (it seems that the same auto-generated metric for both catch-all and specific NIC subnet is the cause). Regards,