Announcement

Collapse
No announcement yet.

exchange topology advice needed sil vous plait?

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • exchange topology advice needed sil vous plait?

    hey all.

    fresh from my last issue, my 2k7 standard server is working (with mailboxes migrated as well!)

    i however seem to unable to properly route mail through my exchange topology without a legacy server being on and working.

    in the past, our topology was native 2k3 but i have added a 2k7 server.

    site looks like this....

    [B]
    mx record
    V
    smart host (mimesweeper)
    |
    V
    site A | site B
    child domain parent domain
    |
    exchange 2k3 legacy exchange 2k3 (Remote Bridgehead)
    exchange 2k7 standard (hub, mailbox, client access[B]


    with the above topology, mail is routed from site A to site B via a routing group connector that allows Site A to tx / rx via the smart host and domain mx record.

    when i switch off the legacy exchange 2k3 box i find site A is unable to tx/rx to either the new 2k7 server or indeed the outside world.

    in my reading, i have learnt that routing group connectors are no longer used in exchange! how do i replicate the above settings in exchange 2k7 to allow mail flow and also allow me to decommision the legacy server?

    as always, any help is appreciated.

    edited to add info on roles applied to 2k7 server.
    Last edited by kipkiller; 18th September 2008, 11:51.
    Kipkiller

    MCP 2000/server, n+, CCNA, LPIC L1

  • #2
    Re: exchange topology advice needed sil vous plait?

    The routing group connector lets mail flow between the 2003 and 2007. You need send and receive connectors setup on the 2007 box to send and receive.

    If you have mail hitting the smtp connector on your Exchange 2003 that is bound for a 2007 mailbox it will use the RG connector to get there. When a 2007 user sends a mail it determines there is no send connector on the 2007 exchange and uses the RG connector to send it to 2003 which then uses the smtp connector.

    Have a read of this:
    http://msexchangeteam.com/archive/20...17/431555.aspx

    Basically, setup a send and receive connectors, change your firewall so it routes email to the 2007 box and then remove the smtp connector on the 2003 box.
    cheers
    Andy

    Please read this before you post:


    Quis custodiet ipsos custodes?

    Comment


    • #3
      Re: exchange topology advice needed sil vous plait?

      thanks for the advice andy....

      the post didnt quite render how i wanted it!

      i will give that a go and will report any progress back.

      cheers,
      Kipkiller

      MCP 2000/server, n+, CCNA, LPIC L1

      Comment


      • #4
        Re: exchange topology advice needed sil vous plait?

        Does that mean I answered incorrectly? If you want to clarify the question I will give it another go!
        cheers
        Andy

        Please read this before you post:


        Quis custodiet ipsos custodes?

        Comment


        • #5
          Re: exchange topology advice needed sil vous plait?

          no, not at all (you have helped!)

          you've given me a pointer in so far as the understanding that i need recieve connectors as well as send.

          ive now created a recieve connector pointing to my child domain's exchange server, however im still trying to decide on the settings for my 'send' connector.

          im assuming i should use the default * address space?

          furthermore, should i create an 'internal' connection?

          all im trying to do is allow a server in a child domain to send and recieve mail via the 2k8 box of which has access to the WWW and relevant MX records.

          hopefully all the above makes sense.
          Last edited by kipkiller; 18th September 2008, 12:50. Reason: must remember to proof read!
          Kipkiller

          MCP 2000/server, n+, CCNA, LPIC L1

          Comment


          • #6
            Re: exchange topology advice needed sil vous plait?

            ok,

            having set up the send connector to 'internal' with address space of *

            i found i was unable to send externally...


            NDR Below
            ukplydc02.ply.company.co.uk #550 5.7.1 Unable to relay for [email protected] ##

            Original message headers:

            Received: from UKSTCEXC02.company.co.uk by
            UKSTCEXC02.company.co.uk with mapi; Thu, 18
            Sep 2008 12:58:30 +0100
            From: Wayne Glanville <[email protected]>
            To: test user <[email protected]>, test
            <[email protected]>
            Date: Thu, 18 Sep 2008 12:58:29 +0100

            UKPLYDC01 - child domain W2k3 server
            UKSTCEXC02 - parent domain 2k8 server

            it is my understanding that i have just forced all traffic to the UKPLYDC02 server... i believe my send connector is badly configured. ideas on a postcard?
            cheers,
            Last edited by kipkiller; 23rd September 2008, 09:55.
            Kipkiller

            MCP 2000/server, n+, CCNA, LPIC L1

            Comment


            • #7
              Re: exchange topology advice needed sil vous plait?

              How many exchange servers are involved here? Originally you said "The legacy exchange 2003 server" which implies one 2003 box.

              The send connector is for external email in this scenario.

              The RG connector gets mail between the 2003 and 2007 so we are describing here how to get mail flow from the 2003 to the 2007 so eventually removing the 2003 server will not affect the flow.

              Have you read this too?
              http://technet.microsoft.com/en-us/l...EXCHG.80).aspx
              cheers
              Andy

              Please read this before you post:


              Quis custodiet ipsos custodes?

              Comment


              • #8
                Re: exchange topology advice needed sil vous plait?

                How many exchange servers are involved here? Originally you said "The legacy exchange 2003 server" which implies one 2003 box. Yes, the server i am replacing is W2K3 and is the only server within the parent domain. There is however a W2K3 server in the child domain that is not as yet getting updated.

                The send connector is for external email in this scenario. the UKSTEXC02 (W2K8 server) has send connecters relating to the smart host one via source server UKSTCEXC02 and the other is again a send connector that again points to the smart host and is via the source server (UKSTCEXC01 - legacy server

                The RG connector gets mail between the 2003 and 2007 so we are describing here how to get mail flow from the 2003 to the 2007 so eventually removing the 2003 server will not affect the flow. Pretty much exactly what i want but with the parent / child issue

                Have you read this too?
                http://technet.microsoft.com/en-us/l...EXCHG.80).aspxWill do, thanks for the link
                Kipkiller

                MCP 2000/server, n+, CCNA, LPIC L1

                Comment


                • #9
                  Re: exchange topology advice needed sil vous plait?

                  What do you see if you run
                  get-routinggroupconnector | fl
                  ?
                  cheers
                  Andy

                  Please read this before you post:


                  Quis custodiet ipsos custodes?

                  Comment


                  • #10
                    Re: exchange topology advice needed sil vous plait?

                    [PS] C:\Users\administrator.company\Desktop>get-routinggroupconnector | fl


                    TargetRoutingGroup : company
                    Cost : 1
                    TargetTransportServers : {UKSTCEXC01}
                    ExchangeLegacyDN : /o=company Group LTD/ou=Exchange Administrative
                    Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Con
                    nections/cn=UKSTCEXC02-UKSTCEXC01
                    PublicFolderReferralsEnabled : True
                    SourceRoutingGroup : Exchange Routing Group (DWBGZMFD01QNBJR)
                    SourceTransportServers : {UKSTCEXC02}
                    HomeMTA : Microsoft MTA
                    HomeMtaServerId : UKSTCEXC02
                    MaxMessageSize : unlimited
                    AdminDisplayName :
                    ExchangeVersion : 0.1 (8.0.535.0)
                    Name : UKSTCEXC02-UKSTCEXC01
                    DistinguishedName : CN=UKSTCEXC02-UKSTCEXC01,CN=Connections,CN=Excha
                    nge Routing Group (DWBGZMFD01QNBJR),CN=Routing G
                    roups,CN=Exchange Administrative Group (FYDIBOHF
                    23SPDLT),CN=AdministrativeGroups, CN=company microsoft Exchange,CN=Se
                    rvices,CN=Configuration,DC=company,DC=co,DC=uk
                    Identity : UKSTCEXC02-UKSTCEXC01
                    Guid : 9d455431-d528-4d54-9540-6cd17b21e038
                    ObjectCategory : company.co.uk/Configuration/Schema/ms-Exch-Rout
                    ing-Group-Connector
                    ObjectClass : {top, msExchConnector, msExchRoutingGroupConnect
                    or}
                    WhenChanged : 28/08/2008 12:17:30
                    WhenCreated : 28/08/2008 12:17:29
                    OriginatingServer : UKSTCEXC02.company.co.uk
                    IsValid : True

                    TargetRoutingGroup : Exchange Routing Group (DWBGZMFD01QNBJR)
                    Cost : 1
                    TargetTransportServers : {UKSTCEXC02}
                    ExchangeLegacyDN : /O=company LTD/OU=company/cn=Co
                    nfiguration/cn=Connections/cn=UKSTCEXC01-UKSTCEX
                    C02
                    PublicFolderReferralsEnabled : True
                    SourceRoutingGroup : company
                    SourceTransportServers : {UKSTCEXC01}
                    HomeMTA : Microsoft MTA
                    HomeMtaServerId : UKSTCEXC01
                    MaxMessageSize : unlimited
                    AdminDisplayName :
                    ExchangeVersion : 0.1 (8.0.535.0)
                    Name : UKSTCEXC01-UKSTCEXC02
                    DistinguishedName : CN=UKSTCEXC01-UKSTCEXC02,CN=Connections,CN=infot
                    eam,CN=Routing Groups,CN=company,CN=Administrat
                    ive Groups,CN=company ,CN
                    =Microsoft Exchange,CN=Services,CN=Configuration
                    ,DC=company,DC=co,DC=uk
                    Identity : UKSTCEXC01-UKSTCEXC02
                    Guid : 744eb4f8-b2f7-4da5-91c8-a75fea49f7f6
                    ObjectCategory : company.co.uk/Configuration/Schema/ms-Exch-Rout
                    ing-Group-Connector
                    ObjectClass : {top, msExchConnector, msExchRoutingGroupConnect
                    or}
                    WhenChanged : 28/08/2008 12:17:30
                    WhenCreated : 28/08/2008 12:17:29
                    OriginatingServer : UKSTCEXC02.company.co.uk
                    IsValid : True

                    TargetRoutingGroup : Exchange Routing Group (DWBGZMFD01QNBJR)
                    Cost : 1
                    TargetTransportServers : {UKSTCEXC02}
                    ExchangeLegacyDN : /O=company Group LTD/OU=UXBRIDGE_company/cn=Co
                    nfiguration/cn=Connections/cn=PLY-STC1
                    PublicFolderReferralsEnabled : True
                    SourceRoutingGroup : company
                    SourceTransportServers : {UKPLYDC02}
                    HomeMTA : Microsoft MTA
                    HomeMtaServerId : UKPLYDC02
                    MaxMessageSize : unlimited
                    AdminDisplayName :
                    ExchangeVersion : 0.0 (6.5.6500.0)
                    Name : PLY-STC1
                    DistinguishedName : CN=PLY-STC1,CN=Connections,CN=company,CN=Routin
                    g Groups,CN=company,CN=Administrative Groups,CN
                    =company Services,CN=Microsoft Ex
                    change,CN=Services,CN=Configuration,DC=company,
                    DC=co,DC=uk
                    Identity : PLY-STC1
                    Guid : 9658c71f-fbb5-4793-a95c-d583665f0bf2
                    ObjectCategory : company.co.uk/Configuration/Schema/ms-Exch-Rout
                    ing-Group-Connector
                    ObjectClass : {top, msExchConnector, msExchRoutingGroupConnect
                    or}
                    WhenChanged : 22/09/2008 12:23:53
                    WhenCreated : 22/09/2008 12:22:52
                    OriginatingServer : UKSTCEXC02.company.co.uk
                    IsValid : True
                    Kipkiller

                    MCP 2000/server, n+, CCNA, LPIC L1

                    Comment

                    Working...
                    X