infutech
asked on
Need two network XP Pro Dual NICs to two seperate Networks
I have an XP Pro system with Dual NICs connected to separate networks each with different IP schemes. One is a 192.168.X.X and the other is 2.1.X.X I need computers from both networks to talk to the system however I need all outbound traffic to route to the 192.168.X.X network first before trying to go out the 2.1.X.X network. Is there a way to make this happen?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Should I remove the 2.1.X.X defaualt gateway? I saw that in another post
TannerMan has the right idea, but you may have to adjust the metric, especially if you let XP set automatic metrics.
Using "route print" look at the metrics that you already have assigned with the two defaults. Using the syntax from TannerMan, put the "higher cost" route entry in with a higher metric than the one you want as a primary default.
Using "route print" look at the metrics that you already have assigned with the two defaults. Using the syntax from TannerMan, put the "higher cost" route entry in with a higher metric than the one you want as a primary default.
If you're going to change the default route, you also need a zero mask, i.e.
route add 0.0.0.0 mask 0.0.0.0 <next hop>
If the 2.1.X.X gateway provides a route to other networks, then leave it in.
You should be able to modify the metric values without having to enter static routes. In advanced TCP/IP properties of the LAN connection, just untick Automatic metric and enter the value in the box provided.
route add 0.0.0.0 mask 0.0.0.0 <next hop>
If the 2.1.X.X gateway provides a route to other networks, then leave it in.
You should be able to modify the metric values without having to enter static routes. In advanced TCP/IP properties of the LAN connection, just untick Automatic metric and enter the value in the box provided.
Frabble is dead on right. I don't knwo what I was thinking with the 16 bit mask on a default entry.....brain freeze.
ASKER
Please forgive me, however I am a litte confused. I should now delete what tannerman has suggested and add the additional 0.0.0.0 route?
Yes, you can delete what you entered and add the proper gateway entry with all zeros...
ASKER
One more time for clarification...
I need to: route add 0.0.0.0 mask 0.0.0.0 2.1.X.X metric 2 -p
Is that correct? This way the traffic would attempt the 192.168.0.X route first?
I need to: route add 0.0.0.0 mask 0.0.0.0 2.1.X.X metric 2 -p
Is that correct? This way the traffic would attempt the 192.168.0.X route first?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
From an command line type "route print" and see your table. You should see that the defaullt 0.0.0.0 route is set to use 192.168.x.x STOP right now and make a screen shot of your route table in case you have to revert back and don't remember any static routes already there.
Then type the following command and excute. Make sure my examples are changed to valid IP's and Network MAsk. If not familiar with the syntax, make sure you type with spaces just like listed below.
route add 0.0.0.0 mask 255.255.0.0 2.1.x.x metric 2 -p
What has been accomplished is the first path data will travel, if a specific path is not known, is the 192.168.x.x NIC. Then, if that destination can not be found there, it will then send the data to the secondary default path of 2.1.x.x. Just to explain, the "0.0.0.0" represents any address that is no known by this system, the "metirc -2" makes it the secondar path of choice and the "-p" makes it persistent so the route will stay after you reboot.
I hope this helps.