I can't say for sure "why" they had you switch from RGC to SMTP connectors without knowing more about your environment, but you can also check "Do not allow public folder referrals" on SMTP connectors too. Either way the RGC and SMTP connectors are the very similar in the way they communicate, it's just that the RGC is the easier to configure of the two, while the SMTP provides you ways of setting up dedicated connectors to other domains, etc. It is weird they would have you make such drastic changes to your Exchange routing, rather than just fixing your DNS. I don't believe this is your problem though.
Right-click on your Public Folders and select "View System Folders". Expand Public Folders -> Offline Address Book. There you should see a /o=OrganizationName/cn=addrlists/cn=oabs/cn=Default Offline Address List. If you do a properties on this, you can add replicas to the other servers. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Larry Wahlers Sent: Wednesday, May 30, 2007 8:33 AM To: Exchange Discussions Subject: RE: Connections to wrong Exchange server Many, many thanks, James. You wrote: > If you look at the Mailbox Store properties on that server > and look at the Offline address list and see what it is set > to, then you can see what OAL Generator the clients in that > store are using. It says "Default Offline Address List." And, I can't find a "Default Offline Address List" public folder anywhere! > If "Do not allow public folder referrals" is enabled on the > RGC Now we're on to something. Around the same time this client said this slowness began, we had a problem in that mail was not being delivered to and from any of the four Exchange sites (routing groups). I got Microsoft support on the phone, and talked to a fellow named Neeraj. He said the Fully-qualified domain name on my Default SMTP virtual server did not resolve to the IP address of the Exchange server upon which it was running, so email was failing. He had me delete all my routing group connectors, and put in SMTP connectors between each site, using the IP address of the remote site's Exchange server. I questioned this, but Neeraj said it would work just fine. Now I am wondering if the lack of RGC's is causing normal Exchange server communications to fail. Am I making sense here? If this is really the problem, all we have to do is change our internal DNS the way Neeraj said to in the first place, put the RGC's back, delete the inter-site SMTP connectors, and all will be well. -- Larry Wahlers Concordia Technologies The Lutheran Church - Missouri Synod MailTo:[EMAIL PROTECTED] Business Phone: (314) 996-1876 _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/read/?forum=exchange To subscribe: http://e-newsletters.internet.com/discussionlists.html/ To unsubscribe send a blank email to [EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with. _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/read/?forum=exchange To subscribe: http://e-newsletters.internet.com/discussionlists.html/ To unsubscribe send a blank email to [EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with.
