Hi
we have an issue where we have Exchange 2010 DAG, 2 members in primary site, and 1 member in the DR site
we have a separate replication network at each site on its own VLAN etc, config is below:
SITE1:
EXCH1 192.168.1.1 - MAPI
EXCH1 10..1.1.1 - DAG
EXCH2 192.168.1.2 - MAPI
EXCH2 10.1.1.2 - DAG
SITE2:
EXCHDR3 - 192.168.3.1 - MAPI
EXCHDR3 - 10.1.3.1 - DAG
there are static routes added for the DAG networks using netsh, these work, pings and traffic work as expected out the correct interfaces.
all hosts can talk to each other, and after allot of work, we have the DAG working as expected, with one Mounted and 2 healthy DB's
now the issue is: all of these hosts are sending packets out of the MAPI interface on port 445 to the DAG IP's of the other mebers, even the two that are in the same site, and have local connections to each others 10.10.x network
i.e., EXCH1 wants to send a packet to EXCH2 10.1.1.2, but it leaves the 192.168.1.1 interface, not the 10.1.1.1 interface, and this is routed via the default GW.
and the same goes for all the others, each member is trying to send 445 packets to 10.10.x.x hosts out the 192.168.x.x interface
note that all the DAG traffic does go out the correct interface, so there is traffic on port 64327 going out the 10.1.x.x interfaces and arriving at the correct interface of the receiver no problem.
so my question is - why? DAG isn't supposed to use 445 anyway, and why on earth would it try to contact an IP that it has a local interface to the subnet for, out a different interface?
and is this a problem? as the DAG seems to be working OK but the logs look horrible
this is a really odd issue and any help would be appreciated