"Bill" said:
Ok below is my routing table. When I add a route here is the syntax:
route -p add <ip address> mask 255.255.255.255 <gateway> metric "X" if
0x"X"
When I say "they dont work" I mean, after a reboot, the routing table
still
has the persistent routes listed, however, I cant ping or log into any of
my
nodes on the network, until I delete the route and re-create it.
Let me try to clarify my setup; I have 3 different physical networks that
I
access through this one pc but all 3 networks are using the same IP range.
(but no nodes have conflicting IP addresses) Which is why I use static
routing. To tell the pc which interface to use to get to a particular IP
address.
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 20 ed 21 fa 3c ...... Realtek RTL8139 Family PCI Fast Ethernet
NIC - Packet Scheduler Miniport
0x3 ...00 13 f7 1a 87 32 ...... Realtek RTL8139 Family PCI Fast Ethernet
NIC
#3 - Packet Scheduler Miniport
0x4 ...00 08 a1 89 c0 73 ...... CNet PRO200 PCI Fast Ethernet Adapter -
Packet Scheduler Miniport
[remainder snipped]
Thanks for the details, Bill. Here's a simple solution that
eliminates the need for the static routes:
1. Create a Network Bridge between the three NICs. I've written a web
page with details:
XP ICS - Network Bridge
http://www.practicallynetworked.com/sharing/xp_ics/networkbridge.htm
2. Assign the Network Bridge an IP address and subnet mask that
matches the other three networks. I think that
10.10.10.1/255.255.255.0 will work.
3. You might have to follow the steps in this Microsoft Knowledge Base
article:
Bridge May Not Work With a Non-Promiscuous Mode Network Adapter
http://support.microsoft.com/kb/302348/en-us
If the Network Bridge doesn't work, we'll have to find another
solution. I'm not sure what that would be, because your network does
some things that I've never tried:
1. Two of the NICs are the same make and model.
2. All three NICs have IP addresses in the same subnet.
I think that the number of "route" statements that you use can be
greatly reduced. For example, this statement says that all IP
addresses in the range 10.10.10.128 through 10.10.10.254 are
accessible through the NIC with IP address 10.10.10.1:
route -p add 10.10.10.128 mask 255.255.255.128 10.10.10.1
I don't understand your IP addressing scheme well enough to give
specific routes.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)
Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.
Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com