Flappy Shoot

Monday, January 19, 2009

Unable to bind to the destination server in DNS - Exchange 2003 Server Routing Group

I had a problem with my Exchange Routing Group Connector. We have 12 Routing Groups. Our setup is hub and spoke model.

For some reason mails between three of the spoke and hub stopped flowing. To pin point the issue mail flow from hub is fine, only the mail flow from three of the remote office via their respective Routing Group was having the problem.

Routing Group Connector status was always in “Retry” state. When I force the connection, few mails are flushed. The error message is “unable to bind to the destination server in DNS”.

The following Microsoft KB article didn’t fix the issue.
http://support.microsoft.com/default.aspx/kb/822939

So I have to log a case with Microsoft.

The resolution gave by them is to run a tool called remonitor.exe which fixes and routing table issue. I believe that it recreates the routing table.

This tool was run from command prompt under system privilege. To do so we started the command prompt by running a job.

C:\Program Files\Exchsrvr\bin>at 5:55 /interactive cmd.exe

From command prompt we run the remonitor to repair the link state table.

C:\Program Files\Exchsrvr\bin>remonitor.exe -i servername
Note: This tool is extracted to bin folder.

After running this utility, all we did is restarted SMTP and Routing Engine.

1 comment:

Tariq Samsudeen said...

How to use the Remonitor tool to clear the cache for the routing engine
http://support.microsoft.com/kb/914255