Two NIC's, metrics question

I've two NIC's in my machine, both public IP's.

Traffic is received on both fine, but outbound traffic doesn't go out via the NIC it came in on, it goes out via 114 regardless. Is there a way to change this via metrics or some other method?


Current route table:

IPv4 Route Table
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 30 48 72 be 9c ...... Intel(R) PRO/100 S Server Adapter - Packet Sched
uler Miniport
0x10004 ...00 30 48 72 be 9d ...... Intel(R) PRO/1000 MT Network Connection - Pa
cket Scheduler Miniport
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
      5      1      5     10      5     10      5     10      5     10      1      1
Default Gateway:
Persistent Routes:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

In my opinion you have two options,

(1) You can alter the metrics to match for each host based route because as it stands your route for (.114) appears to be more attractive than your route for (.124) in the routing table above.      5      5


(2) You can use a router with two ethernet interfaces (or if it supports subinterfaces) and seperate the two IP's into a seperate network using VLSM

rossdagleyAuthor Commented:
All this can only be done with software on Windows 2003 - I cant stick any more hardware in.

I've adjusted the metrics so their the same, but (for example) if I FTP to, when I get my download, it still comes out over, not 124. :(

Any ideas?

Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

rossdagleyAuthor Commented:
Not entirely sure I understand that doc from MS.

Is there really no simple solution for this?

> Is there really no simple solution for this?

No.  The mechanism that selects an outbound interface to use looks only at the destination address.  It doesn't care about the source address, and has absolutely no concept that this packet is "in response to" some other packet that may have once passed this way.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
rossdagleyAuthor Commented:
Thanks for the replies, and I'm sorry for the delay. I didn't ever solve this problem (due to what you said - IP doesn't care where it came from) so I gave up. :(

But thanks for the help.

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.