Routing Connector Problems

Posted on 2004-10-21
Medium Priority
Last Modified: 2012-06-21
We have two exchange sites running exchange 5.5 servers, and I have installed Exchange 2003 servers in each site as the first step in our migration.  We have a few mailboxes moved over to each of the EX2003 servers to test, and all sems to be functional. However, when I look in the queues on each of the 2003 servers (in system manager) I see site connectors that are not functional.  Each server has a Site Connector (routing group connector) that says it is unable to bind to server in DNS.  I have tested name resolution for both servers to each other and there are no problems whatsoever.

I recently tried to make the new 2003 servers the bridgeheads in each site (using 5.5 administrator, not sure how to so it with exchange 2003 system manager, it is greyed out).  Once I made the change, mail started queuing up in each of these connectors and delivery was not occurring.  It doesn't seem like I can take our 5.5 servers offline unless I can figure this out.  I have gone over DNS settings repeatedly and cannot find any problems with it currently (although in the past there were).  I recently ran netdiag /v and found no DNS errors.

Also, for some reason there are two identical Site connectors in site 1 pointing to site 2 (showing in the queues), both are not functional.  I am unsure as to how to remove one of them.

Question by:bandoafernandez
  • 5
  • 2

Expert Comment

ID: 12375016
Let me see if I understood your topology correctly

Two Sites ... created in E5.5 and now you have E2k3 in each. You said you have RGC between these two sites, but actually you cannot make changes on these RGC through E5.5 Admin.

You might still be using your old E5.5 "Site Connector or X.400 Connector" ... as you said you cannot make changes though E2k3 System Admin.

But anyways, make sure what connector you are using.

for your DNS, I could say that nslookup by default uses UDP Queries and Exchange queries using TCP. You can force 'nslookup' to use TCP using command ... "set vc". Any further Queries after this settings would be TCP.

Use "winroute.exe" to troubleshoot Connector issues.
281382 How to Use the WinRoute Tool

If you see multiple connectors ... probably your Routing Table is Fried. Winroute will reveal more.

One basic Question, do you see all your recipient from all the servers? ... what if you create new Mailbox on E2k3, is it available on GAL on other E2k3?

Author Comment

ID: 12382393
I can actually ONLY make changes on the site connectors through the 5.5 admin, not through the 2003 System Manager.  It appears that the RGC is merely an emulation of the 5.5 site connector, and only replicates changes that I make through the 5.5 administrator, that's it.  I can't edit anything through the 2003 administrator.

I do see all of our recipients from all servers.  New mailboxes created on Exchange 2k3 do show up on the GAL on all other servers (5.5 and 2k3).

I will check try winroute and see what happens. Thanks.

Author Comment

ID: 12382445
Also - should I be creating a new connector between sites using 2k3?  We are utilizing existing 5.5 site connectors.
Configuration Guide and Best Practices

Read the guide to learn how to orchestrate Data ONTAP, create application-consistent backups and enable fast recovery from NetApp storage snapshots. Version 9.5 also contains performance and scalability enhancements to meet the needs of the largest enterprise environments.


Accepted Solution

Maharajkp earned 750 total points
ID: 12383163
According to your last comment ... you are using E5.5 Site Connectors, that means you can only make changes in E5.5 Admin.

If that's the case, yes creating Routing Group Connector between E2k3 would definitely help and it is infact more efficient

Author Comment

ID: 12383310
Ok I created the RGC using 2k3.  Now I should be able to delete the existing site connector in the 5.5 administrator, correct?  It will not allow me to do this, saying that it is the only connector between the 2 sites.  Does this mean that I have to delete the Directory replication connection between the two sites?  If so, should I create some other kind of directory rep connection using 2003 first?

Author Comment

ID: 12383321
Ah, it let me delete the old site connector... Will monitor now... But what of the Dir rep connector?

Author Comment

ID: 12427982
I figured it out.  Restarted the SMTP service and the duplicate queue disappeared.

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Want to know how to use Exchange Server Eseutil command? Go through this article as it gives you the know-how.
With so many activities to perform, Exchange administrators are always busy in organizations. If everything, including Exchange Servers, Outlook clients, and Office 365 accounts work without any issues, they can sit and relax. But unfortunately, it…
To show how to create a transport rule in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Rules tab.:  To cr…
This video demonstrates how to sync Microsoft Exchange Public Folders with smartphones using CodeTwo Exchange Sync and Exchange ActiveSync. To learn more about CodeTwo Exchange Sync and download the free trial, go to: http://www.codetwo.com/excha…
Suggested Courses
Course of the Month16 days, 20 hours left to enroll

862 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question