***************************
All of the following examples should provide full TCP/IP connectivity,
<all masks are 255.255.255.0, unless noted
************* One Router *************
segment1 --- NT router --- segment2
NT router:
NIC1: 192.168.100.1 (segment1)
Segment1 machines:
IP: 192.168.100.2 - 192.168.100.254
Segment2 machines:
IP: 192.168.200.2 - 192.168.200.254
************* Two Routers *************
segment1 --- NT router --- segment2 --- cisco --- segment3
NT router:
NIC1: 192.168.100.1 (segment1)
Cisco:
NIC1: 192.168.200.2 (segment2)
Segment1 machines:
IP: 192.168.100.2 - 192.168.100.254
Segment2 machines:
IP: 192.168.200.3 - 192.168.200.254
Segment3 machines:
IP: 192.168.250.2 - 192.168.250.254
************* Three Routers *************
segment1 --- NT router --- segment2 --- Cisco --- segment3
NT router:
NIC1: 192.168.100.1 (segment1)
Cisco:
NIC1: 192.168.200.2 (segment2)
Bay Router:
NIC1: 192.168.100.2 (segment1)
Segment1 machines:
IP: 192.168.100.3 - 192.168.100.254
Segment2 machines:
IP: 192.168.200.3 - 192.168.200.254
Segment3 machines:
IP: 192.168.250.2 - 192.168.250.254
Segment4 machines:
IP: 10.100.0.0 <mask 255.255.0.0
Note: The static route added to the NT in the 3rd example. You can either do this or implement one of the router protocols (e.g. RIP) on at least the NT and the BAY.
Note: In some cases, you have an option on which DG to use on the segment clients (or even the routers). There can be many reasons to favor one over the other, but probably the most common determining factor is traffic patterns (i.e. use the DG that is attached to the most common destination network).
***************************