Hi,I just started working for a new company and have found that they are having problems with their SMTP connectors. there are two sites, A & B and they are on the same domain, CDE.com, but we have two different companies on that domain. CDE and HGH. the main mx records point to my site, B and our email address is user@HGH.com. Now when our internet connection goes down our VPN connection to site A stays up. All mail automatically goes to site A's exchange server, but it it wont send it over the VPN connection, it tries the shooting it over the internet instead. my question is should I create a route to the VPN IP address of the exchange server (B) instead of the FQDN of server B?thanks adn sorry if this sounds confusing. i just started here and havent gotten a full grasp of the setup.

OK so let me see if I have this right.. One domain CDE.com 2 exchange servers in seperate physical sites conected by VPN, HGH and CDE 2 name spaces with the mx records pointing to both exchange servers.. HGH has the lower cost You have conectors between CDC and HGH going both ways right? hmm DNS resolution.. on the CDE exchange server doesthe FQDN for HGHresolve to the external IP in the mx record or the VPN address?

looks like it pings the correct address, but I think the route has the wrong FQDN. Looks like maybe there was a mix up of which name they should be using. Will post the outcome after we try. Thanks ScottI take that back. It is pointing to the Public FQDN not the Private. I suggested we change it to the Private but the guys in charge want me to put in a support ticket with Microsoft to be sure.