connecting two different networks
From: Dan (anonymous_at_discussions.microsoft.com)
Date: 05/12/04
- Next message: Jerold Schulman: "Re: Windows 2000 server utilization reporting"
- Previous message: Andrew S.: "Windows 2000 server utilization reporting"
- In reply to: Altria: "connecting two different networks"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 12 May 2004 11:18:24 -0700
Phillips Answer is one to do it - Using a Router between
the different nets.
But that requires hardware you may nothave or need. The
other approach in my mind is easier and cheaper.
First I'm assuming all three nets are present on the same
wire directly (not via a router route).
Go into the TCP/IP props in the advanced section add in a
static IP address for the other networks (all addresses
must be assigned you can't use DHCP in this config.) Once
you add each address you will also need to add the needed
masks.
OK, next step
Open up a DOS window then run 'ROUTE' This will give you
the Route tsble info. For help add '/?' with a space
between this will help you in setting up the Route service
which you may need to configure. As you know the default
Route (also called default gateway) sets which network and
upstream Router one needs to go to to get to the next
net. Assuming the primary IP address you have assigned to
the NIC network address space is the only pathway to gain
access to the next upstream network (via a Router or
firewall/Proxy system) you don't need to do anything
within the Route services as all of the other networks are
listed dynamically. If on the other hand one or more of
the other address networks you now have setup need to be
crossed to a router to still another network you will need
to either add the needed route entry every time you
restart your system or set a persistant entry.
Now using multiple networks on the same wire is not overly
smart. Ther are a few places it is needed but you appear
to be going to far here (DMZ). I would recommend not
having more than two nets on a given wire and have only
one network which needs to be routed across any router or
firewall. With server systems you may have multiple NICs
each used to isolate either given traffic types or
connection pathways. This is were I mostly use this trick
when two systems have muiltiple pathways between them and
I need to bias a given pathway and/or allow a given
process access to a different direction.
Sometimes the config is more complex were a static route
entry won't do. This is were adding a routing protocol
service onto the system might make better sense. Adding
RIP2 or OSPF or other routing protocol is the answer.
This allows the system to be a member of the routers route
updates yet not be a router (no interconnection between
the different NIC's or there nets).
>-----Original Message-----
>Hello All,
>This may be a silly question but how do I connect
multiple networks that do
>not have a common network IDs. Is this done thru the
subnet mask? For
>example, how would i share resources in networks such as;
>
>A)111.222.0.0
>B)222.0.0.0
>C)333.1.20.0
>
>I am sure that a router is involved but do I simply have
to give them the
>same subnet mask?
>TIA
>Altria
>
>
>.
>
- Next message: Jerold Schulman: "Re: Windows 2000 server utilization reporting"
- Previous message: Andrew S.: "Windows 2000 server utilization reporting"
- In reply to: Altria: "connecting two different networks"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|