On Tue, Sep 20, 2011 at 11:00, Maglinger, Paul <[email protected]> wrote:
> Windows 2003 DC, migrating from Exchange 2003 to 2010. Setting up DAGs
> and wanting to separate out the replication traffic from the rest of the
> stuff. We have 3 mailbox servers, two of which are at our site, the
> other is at another site. We can only have one gateway per server and
> are trying to figure out how to get the replication traffic from A to B.
>
> Site A Mailbox Server A data NIC - 10.111.100.1
> Site A Mailbox Server A replication NIC - 10.111.101.30
> 24 bit SNM, 10.111.100.254 GW
>
> Site A Mailbox Server B data NIC - 10.111.100.2
> Site A Mailbox Server B replication NIC - 10.111.101.31
> 24 bit SNM, 10.111.100.254 GW
>
> Site B Mailbox Server C data NIC - 10.121.100.3
> Site B Mailbox Server C replication NIC - 10.121.101.32
> 24 bit SNM, 10.121.100.254 GW
>
> -Paul
Um, more info please?
Can you describe the data flow you want to see? Can you ping from each
of the machines to the others?
I can't speak to the Exchange portion of this, but you are sort of
correct. While you can have only one Default Gateway on a Windows box,
you can specify routes. So, for instance you might have a router at
10.0.0.1 and another on the same network segment at 10.0.0.2. If on
your Windows machine you set 10.0.0.1 as the DG, you can still specify
that data for some subnet (say, 10.0.10.0/24) goes out the 10.0.0.2
gateway with a route statement, by opening up a cmd.exe or powershell
instance:
route -p add 10.0.10.0 netmask 255.255.255.0 10.0.0.2
The -p parameter enters the route into the registry, which makes it
survive reboots, until you remove the route manually.
OTOH, if you only have one router per network segment, then you'll
need to do your routing in your network equipement. I'll leave that
for you to figure out...
Kurt
~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
---
To manage subscriptions click here:
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to [email protected]
with the body: unsubscribe ntsysadmin
