Okay, we got this working. We were able to set up a static route on both sides to get this to work.
On one side: #route add 10.111.101.0 mask 255.255.255.0 10.121.100.254 metric 1 -p On the other: #route add 10.121.101.0 mask 255.255.255.0 10.111.100.254 metric 1 -p Should've occurred to us earlier. -----Original Message----- 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 ~ 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 ~ 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
