none
Exchange 2010 Best Practices Analyzer Cannot connect to port 691 of routing group master.

All replies

  • Hello Artur,

    My First question is, is Mail flow is working fine?
    If you don;t have legacy server than you don;t need routing group. 


    Gulab | MCITP: Exchange 2010-2007 | Skype: Gulab.Mallah | Blog: www.ExchangeRanger.Blogspot.com
    Friday, July 08, 2011 6:19 PM
  • Mail flow is working fine. This is the only Exchange server in our organization at the time. Should I remove routing groups?
    Artur
    Friday, July 08, 2011 6:25 PM
  • Hi Artur,

    Yes, you can remove the Routing Group as it's not required by 2010. Exchange 2010 has  Receive and Send Connector.
    You would use Routing Group if you had Exchange 2003 in the environment, but you do not have it, hence you are good to GO and remove it.


    Gulab | MCITP: Exchange 2010-2007 | Skype: Gulab.Mallah | Blog: www.ExchangeRanger.Blogspot.com
    Saturday, July 09, 2011 4:30 AM
  • As Gulab rightly said, you can remove routing group master connector safely using Exchange cmdlets. Since routing group master connector was used in Exchange 2003, but in Exchange 2010 it uses Send/Receiver connector to send & receive mails. As your organization is complete Exchange 2010, you can get rid of it safely, more at below links.

    http://technet.microsoft.com/en-us/library/aa998645.aspx

    http://www.petri.co.il/cleaning-up-exchange-2003-remnants-part-2.htm

     

    Regards  


    MVP-Directory Services 

    Awinish Vishwakarma| CHECK MY BLOG

    Disclaimer: This posting is provided AS-IS with no warranties or guarantees and confers no rights.

     

    Saturday, July 09, 2011 7:18 AM
  • Hi Gays

    At this point I'm a little confused.

    I checked suggested articles and read about connectors, but it seems that our server has no legacy routing connectors

     cmdlet "Get-RoutingGroupconnector |fl" returns no connectors at all.

    ADSI Edit shows under

    CN=Connections,CN=Exchange Routing Group (DWBGZMFD01QNBJR),CN=Routing Groups,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=MYDC,DC=com

    Internet Connector; Class msExchRoutingSMTPConnector

    and

    Text Messaging Delivery Agent Connector; Class: msExchAgentConnector

    I'm not sure if we can remove this routing group with these connectors.

    Thank you for taking your time to help me.


    Artur
    Monday, July 11, 2011 2:05 PM
  • Hello Artur,

    You can delete the connectors which says 2003-2010. Its not going to cause any problem as Exchange 2003 does not exist anymore.


    Gulab | MCITP: Exchange 2010-2007 | Skype: Gulab.Mallah | Blog: www.ExchangeRanger.Blogspot.com
    Monday, July 11, 2011 3:37 PM
  • Hi Gulab

     It seems that we have routing groups without any 3003-2010 connectors. What is the best way to determine which ones can be removed?


    Artur
    Monday, July 11, 2011 3:53 PM
  • Isn't that your send connector for the Exchange 2010 server?

    Is it called "Internet Connector", then don't delete it.. if you do, then your org won't be able to send mail out externally

    Check under Org config -> HUB -> Send connectors

     


    Jonas Andersson | Microsoft Community Contributor Award 2011 | MCITP: EMA 2007/2010 | Blog: http://www.testlabs.se/blog | Follow me on twitter: jonand82
    Wednesday, July 13, 2011 11:32 AM
  •  Hi Jonas

      I'm not going to delete any send or receive connectors. Do you know how to find any remaining 2003-2010 connectors, and routing groups?.


    Artur
    Wednesday, July 13, 2011 12:49 PM
  • Use EMS

    Get-RoutingGroupConnector

    http://technet.microsoft.com/en-us/library/aa996924.aspx

     

    If you have any, check if it's in use, and if not you can use

    Remove-RoutingGroupConnector

    http://technet.microsoft.com/en-us/library/aa998645.aspx


    Jonas Andersson | Microsoft Community Contributor Award 2011 | MCITP: EMA 2007/2010 | Blog: http://www.testlabs.se/blog | Follow me on twitter: jonand82
    Wednesday, July 13, 2011 12:57 PM
  • Jonas

    Get-RoutingGroupConnector returns nothing, and ExBPA still returns "Cannot connect to port 691 of routing group master" error.


    Artur
    Wednesday, July 13, 2011 1:57 PM
  • Is the send connector created from the 2010 server?

     


    Jonas Andersson | Microsoft Community Contributor Award 2011 | MCITP: EMA 2007/2010 | Blog: http://www.testlabs.se/blog | Follow me on twitter: jonand82
    Wednesday, July 13, 2011 2:58 PM
  • Most likely. Transition from Exchange 2003 to 2010 was done by 3rd party company and they never clean up this error.


    Artur
    Wednesday, July 13, 2011 3:05 PM
  • Hi

    I did just check my own environment..

    I have my send connectors and one extra called:

    CN=Text Messaging Delivery Agent Connector

    So most likely you shouldn't touch this object..

     


    Jonas Andersson | Microsoft Community Contributor Award 2011 | MCITP: EMA 2007/2010 | Blog: http://www.testlabs.se/blog | Follow me on twitter: jonand82
    Thursday, July 14, 2011 12:35 PM
  • Hi,
    Please check your setting for the attribute msExchangeRoutingMasterDN. Is the CN specified a server that are still alive?
    Use AdsiEdit and check the setting. You find it under:

    CN=Exchange Routing Group (DWBGZMFD01QNBJR),CN=Routing Groups,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=YOUR_EXCHANGE_ORG,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=DOMAIN,DC=XX

    If you do find an old entry there, clear the value and paste in the DN of the Exchange 2010 Server that should be the MSExchRoutingGroupMaster.
    Even an Exchange Org that never has had an Routing Group Connector has one.

    :Martina

    Thursday, July 14, 2011 1:27 PM
  • Hi Martina

    msExchangeRoutingMasterDN shows the new server.

    Artur


    Artur
    Thursday, July 14, 2011 2:33 PM
  • Did you ever figure out how to get this one to go away?
    Wednesday, August 21, 2013 6:53 AM
  • Did you ever figure out how to get this one to go away?

    No, but it seems  it does not affect the server.

    Artur

    Wednesday, August 21, 2013 12:36 PM
  • I know this is very old, but the solution is to remove the First Routing Group container.

    The error will go away after that.

    PD

    Saturday, March 08, 2014 11:58 PM
  • Thank you. The error did not affect the server so far. It's already almost 3 years, but I will definitely check it. 

    Artur

    Monday, March 10, 2014 2:08 PM