|
|
Question : Routing Group Connector Problem
|
|
Exchange 2003 - I have an Exchange System with two routing groups. Originally this was setup with one routing group connector in each routing group. For whatever reason the routing group connector in Rouging Group A stopped working; however the routing group connector in Routing Group B was still working. To work around this I deleted the routing group connector in Routing Group A and replaced it with a SMTP connector, which has been working fine. When I recreate the routing group connector and look at the queues of the local bridgehead in Exchange System Manager I see the routing group connector is no connected. It is in retry state. If I click on the connector the message under Additional queue information is "Unable to bind to the destination server in DNS". I can ping the remote bridgehead from the local bridgehead, so DNS resolution shouldn't be an issue and the SMTP connector is working fine. I don't see anything unusal in the local bridgeheads Event Viewer. Im running out of ideas; any help is appreciated.
Thanks.
|
Answer : Routing Group Connector Problem
|
|
I have seen this before.
Have you changed the FQDN on the SMTP virtual server? If you have, does that resolve correctly internally? Another fix can be to ensure that all SMTP virtual servers have been changed from "All Unassigned" to the specific IP address of the server. It doesn't affect operation of the servers but it will stop this DNS problem from occurring.
Simon.
|
|
|
|