Solved

Need two network XP Pro Dual NICs to two seperate Networks

Posted on 2004-10-15
10
222 Views
Last Modified: 2010-04-10
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?
0
Comment
Question by:infutech
  • 3
  • 3
  • 3
  • +1
10 Comments
 
LVL 9

Expert Comment

by:TannerMan
ID: 12323693
This can be accomplished by manipulating your route table. Dangerous, if not familiar with route tables. Open up your XP Control Panel and then the Network Connections applet. In the opening window click the  advanced option on the horizontal menu, then choose Advanced Options. In the connections section move your NIC utilizing 192.168.x.x to the top of the list if not thre.

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.
0
 
LVL 9

Accepted Solution

by:
TannerMan earned 250 total points
ID: 12323980
I know the spacing may be difficult to view if your not familiar with route table edits. The below example has an UNDERSCORE where each space should be in the command.

route_add_0.0.0.0_mask_255.255.0.0_2.1.x.x_metric_2_-p

Hope that helps
0
 

Author Comment

by:infutech
ID: 12324068
Should I remove the 2.1.X.X defaualt gateway? I saw that in another post
0
Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

 
LVL 79

Expert Comment

by:lrmoore
ID: 12324500
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.
0
 
LVL 15

Expert Comment

by:Frabble
ID: 12325443
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.
0
 
LVL 9

Expert Comment

by:TannerMan
ID: 12325736
Frabble is dead on right. I don't knwo what I was thinking with the 16 bit mask on a default entry.....brain freeze.
0
 

Author Comment

by:infutech
ID: 12328217
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?
0
 
LVL 79

Expert Comment

by:lrmoore
ID: 12328300
Yes, you can delete what you entered and add the proper gateway entry with all zeros...
0
 

Author Comment

by:infutech
ID: 12339976
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?
0
 
LVL 79

Assisted Solution

by:lrmoore
lrmoore earned 250 total points
ID: 12340282
That depends. Look at the result of "route print" first.
What is the current metric for your default gateway? XP Defaults mine to '10'
Just make sure that the new route to 2.x.x.x has a higher metric than the existing default '2' might not be high enough.


0

Featured Post

Netscaler Common Configuration How To guides

If you use NetScaler you will want to see these guides. The NetScaler How To Guides show administrators how to get NetScaler up and configured by providing instructions for common scenarios and some not so common ones.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Configuring network clients can be a chore, especially if there are a large number of them or a lot of itinerant users.  DHCP dynamically manages this process, much to the relief of users and administrators alike!
For many of us, the  holiday season kindles the natural urge to give back to our friends, family members and communities. While it's easy for friends to notice the impact of such deeds, understanding the contributions of businesses and enterprises i…
Viewers will learn how to connect to a wireless network using the network security key. They will also learn how to access the IP address and DNS server for connections that must be done manually. After setting up a router, find the network security…
Get a first impression of how PRTG looks and learn how it works.   This video is a short introduction to PRTG, as an initial overview or as a quick start for new PRTG users.

830 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question