Announcement

Collapse
No announcement yet.

One domain moved to Google Apps from Exchange 2003. Trouble with internal

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

  • One domain moved to Google Apps from Exchange 2003. Trouble with internal

    Hi,
    Running 2 domains on one Exchange 2003 server. I moved one domain (xxx.com) from Exchange 2003 to Google Apps. Email from users on other domain that is still on Exchange (zzz.com) cannot send e-mail out to users on the Google Apps domain. External email to and from google apps works fine. Any ideas?

  • #2
    Re: One domain moved to Google Apps from Exchange 2003. Trouble with internal

    Check recipient policies, make sure the domain has been removed. You will also need to go through each user manually and remove any addresses on the old domain. Also check DNS and make sure that the MX record for this domain is correctly resolved by your servers.
    BSc, MCSA: Server 2008, MCSE, MCSA: Messaging, MCTS
    sigpic
    Cruachan's Blog

    Comment


    • #3
      Re: One domain moved to Google Apps from Exchange 2003. Trouble with internal

      Thanks for your help. I deleted the domain in the Recipient Policies and deleted the MX record associated with the domain in dns. I removed the old e-mail addresses as well. Still having the issue though.
      I realized that the domain that I moved is not a parent domain, but a child domain. both the active e-mail addresses for the two companies are under one parent domain. Is that the problem? If so, how to fix?

      Comment


      • #4
        Re: One domain moved to Google Apps from Exchange 2003. Trouble with internal

        By child domain you mean that the domain is sub.example.com and the domain still on Exchange is example.com, then that doesn't matter.
        As far as Exchange is concerned, they are two different domains. Exchange requires an exact match.

        Since you removed the domain, have you restarted any services? If not, then I suggest that you restart the Exchange and IIS services. That will ensure that the change is written to the IIS Metabase.

        There is always a chance that the IIS metabase hasn't updated correctly and the domain is being treated as internal. You would need to use IIS Metabase Explorer to verify that.

        Simon.
        --
        Simon Butler
        Exchange MVP

        Blog: http://blog.sembee.co.uk/
        More Exchange Content: http://exchange.sembee.info/
        Exchange Resources List: http://exbpa.com/
        In the UK? Hire me: http://www.sembee.co.uk/

        Sembee is a registered trademark, used here with permission.

        Comment

        Working...
        X