• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 244
  • Last Modified:

exchange queues

We have mail set up to go from our back end Exchange 2003 server to our front end Exchange 2003. We have two sites in Exchange, a site in AZ and one in DC. Mail from each site should flow from the mailbox server to the OWA server to the internet. As a backup, since we have redundant links between the AZ and DC sites, we have a backup connector to the other site to have mail from DC go out AZ if the internet is down on one site or the other way if either site is experiencing a failure.

The cost we have out to the internet directly (and DNS is working fine it appears) is 3 and the one we have set up as a failover to the other site is set to 30.

Mail is flowing from our DC site to the AZ instead of directly out to the internet. AZ is sending mail correctly. Can any one give me any ideas as to where to look to figure out what could be the problem? I am not sure where else to look as it all seems to be ok or what tools to try and put together the problem.

Thanks in advance,

E
0
vatg
Asked:
vatg
2 Solutions
 
Exchange_GeekCommented:
How many routing groups do you have ? Who are the masters for each ?
How many SMTP connectors have you created ? Naming convention please.
Which is the local bridgehead server and remote for all connectors ?
Which ports are the emails flowing upon.

0
 
MrLonandBCommented:
Configure an SMTP Connector from the DC Server to the Front-end Server. The Address Space would be (*) and a cost of 1. In the properties of the connector, set the Smart Host to the IP Address of the Front-end Server. Example: [192.168.1.1]
0
 
edentoneCommented:
I agree with MrL above. You may have to recreate the connectors and as well, make sure that no automated process, like AV or something to that effect is blocking access to the connector that should be the one going out.

Also, why is there no cost of 1, what is the idea with doing the lowest cost with a 3
0
 
vatgAuthor Commented:
I will check out what MrLonandB and edentone have recommended and will try closing the question today as I think I have it working with some of my own troubleshooting.
0
 
vatgAuthor Commented:
Between the recreation of the connectors and the discovery of the vbscript that seemed to be causing some issues, the problem has been resolved. I am not sure exactly who got it, so I am assigning points equally.
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now